[Kernel-packages] [Bug 2063322] Re: ite-cir driver failed to load due to a regression in linux kernel 6.5+ serial driver change

[James Joseph]

** Tags added: noble

** Tags added: mantic

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

Title:
  ite-cir driver failed to load due to a regression in linux kernel 6.5+
  serial driver change

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

  From Kernel 6.5 and above, the serial driver now claims multiple UART
  ports by default, when the previous behaviour was it would only claim
  1.  Due to this the ite-cir driver can no longer load because the port
  it would assign itself is now being used in memory by the 16550/8250
  driver.  We have found a workaround by disabling the serial driver
  from consuming more than 1 port.  Below is the steps we went to
  troubleshoot, investigate and the solution we’ve found.  This is a
  regression from 6.4 behaviour.

  When installing 24.04 I noticed that the /dev/lirc0 device was not
  loaded on the system which is what is created when the driver is
  loaded.  After reviewing the driver we use on 20.04 I then searched
  the kernel logs and found that the ite-cir driver failed to load due
  to error -16.

  ```
  2024-04-19T13:44:51.873060+00:00 host kernel: rc rc0: ITE8708 CIR transceiver 
as /devices/pnp0/00:03/rc/rc0
  2024-04-19T13:44:51.873062+00:00 host kernel: rc rc0: lirc_dev: driver 
ite-cir registered at minor = 0, raw IR receiver, raw IR transmitter
  2024-04-19T13:44:51.873070+00:00 host kernel: input: ITE8708 CIR transceiver 
as /devices/pnp0/00:03/rc/rc0/input6
  2024-04-19T13:44:51.873072+00:00 host kernel: i2c i2c-2: 2/2 memory slots 
populated (from DMI)
  2024-04-19T13:44:51.873076+00:00 host kernel: i2c i2c-2: Successfully 
instantiated SPD at 0x50
  2024-04-19T13:44:51.873078+00:00 host kernel: ite-cir: probe of 00:03 failed 
with error -16
  ```

  I reviewed kernel error message and this error is due to the
  device/resource is busy or in use.  My colleague and I reviewed the
  ite-cir driver source code and noticed the driver initialisation
  succeeds up until L1404
  https://github.com/torvalds/linux/blob/master/drivers/media/rc/ite-
  cir.c#L1404 where it attempts to request_region, if it fails to do
  this it will unregister the device.

  The request region allocates a place in memory for the device to use,
  we believe it’s using the ioport.h’s request region function
  https://github.com/torvalds/linux/blob/master/include/linux/ioport.h#L278

  When we added some debug lines to ite-cir we noticed that the memory
  reference it is trying to allocate is 02f8-02ff. We checked the
  ioports on 24.04 and noticed that the serial driver was taking up this
  reference in memory when in 20.04 (The OS we currently use) and 23.04
  it would not.

  Ubuntu 24.04 ioports

  ```
  user@host:~$ sudo cat /proc/ioports
  -0cf7 : PCI Bus :00
    02f8-02ff : serial
    03f8-03ff : serial
  ```

  Ubuntu 20.04 ioports memory allocation

  ```
  user@host:~$ sudo cat /proc/ioports
  -0cf7 : PCI Bus :00
    02f8-02ff : ite-cir
    03f8-03ff : serial
  ```

  When we investigated any changes that might cause this, we came with
  two potential commits that were released in 6.5 that might have caused
  this issue:

  * 
https://github.com/torvalds/linux/commit/9d86719f8769244dc99b8cb6091c41eae3fd684f
  * 
https://github.com/torvalds/linux/commit/84a9582fd203063cd4d301204971ff2cd8327f1a

  The serial changes allow 16550/8250 driver to consume as many serial
  ports as they require initializing the driver, originally they only
  used 1.  Due to this we noticed that when we checked the serial ports
  in use by the device that 8250 was consuming the place in memory that
  ite-cir should.

  Ubuntu 24.04

  ```
  user@host:~$ sudo setserial -g /dev/ttyS*
  /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
  /dev/ttyS1, UART: 8250, Port: 0x02f8, IRQ: 3
  ```

  Ubuntu 20.04

  ```
  user@host:~$ sudo setserial -g /dev/ttyS*
  /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
  /dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3
  ```
  [Regression]
  We believe that the regression started from 6.5 kernel onwards based on the 
commit changes that were done to the serial driver that shipped to those 
kernels.  23.04 that uses 6.2 works as expected and shows no issues with using 
the serial port for IR while 23.10 that uses 6.5 and 24.04 that uses 6.8 does 
not load the ite-cir driver.

  [Reproducible steps]

  * Use Ubuntu 23.10 + or use Kernel 6.5+
  * Use IR hardware that requires the ite-cir driver to be loaded
  * Attempt to load ite-cir driver on boot of OS
  * Check /var/log/kern.log for ite-cir driver failure

  [Fix]

  The requested solution would be to either:

  * Set the serial driver to no longer consume more than 1 serial port
  * Have the serial driver check what memory reference ite-cir driver needs to 
load, ignore that reference and then consume another point in memory instead.

  We have found a 

[Kernel-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu

[James Cameron]

I'm upstream.  I saw the removal first in the release notes.  Yet I'm
not surprised by removal.  The contributions to pptp and pptpd have
declined, so the release cadence has slowed as well (1.4.0 in 2013, but
a few commits in git since).  Number of people asking for help has also
declined.  Some countries or corporations still require it, presumably
because it is so easily monitored.

Using pptpd on Ubuntu will be more difficult because of removal from
Ubuntu, but that's just a security by obscurity; very easily bypassed by
installing the software yourself.  Thanks for holding on so long.

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

Title:
  RM: Remove dangerously insecure MPPE PPTP from Ubuntu

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in pptp-linux package in Ubuntu:
  New
Status in pptpd package in Ubuntu:
  Fix Released

Bug description:
  Remove dangerously insecure MPPE PPTP from Ubuntu

  https://pptpclient.sourceforge.net/protocol-security.phtml

  It has been dead for over 20 years now.

  Current Windows versions natively support IPSec and L2TP as much
  better alternatives.

  https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec-
  configuration#how-to-use-wfp-to-configure-ipsec-policies

  https://learn.microsoft.com/en-US/troubleshoot/windows-
  server/networking/configure-l2tp-ipsec-server-behind-nat-t-device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2041751/+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 2063512] [NEW] on reboot with linux-image-6.5.0-34 system hangs at loading initial ramdisk

[James Hill]

Public bug reported:

loading initial ramdisk hangs only with linux-image-6.5.0-34

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-550 550.67-0ubuntu1.22.04.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: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 16:36:07 2024
InstallationDate: Installed on 2021-01-20 (1191 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: nvidia-graphics-drivers-550
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-550 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  on reboot with linux-image-6.5.0-34 system hangs at loading initial
  ramdisk

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

Bug description:
  loading initial ramdisk hangs only with linux-image-6.5.0-34

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nvidia-driver-550 550.67-0ubuntu1.22.04.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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 16:36:07 2024
  InstallationDate: Installed on 2021-01-20 (1191 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: nvidia-graphics-drivers-550
  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-550/+bug/2063512/+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 2063322] [NEW] ite-cir driver failed to load due to a regression in linux kernel 6.5+ serial driver change

[James Joseph]

Public bug reported:

[Impact]

From Kernel 6.5 and above, the serial driver now claims multiple UART
ports by default, when the previous behaviour was it would only claim 1.
Due to this the ite-cir driver can no longer load because the port it
would assign itself is now being used in memory by the 16550/8250
driver.  We have found a workaround by disabling the serial driver from
consuming more than 1 port.  Below is the steps we went to troubleshoot,
investigate and the solution we’ve found.  This is a regression from 6.4
behaviour.

When installing 24.04 I noticed that the /dev/lirc0 device was not
loaded on the system which is what is created when the driver is loaded.
After reviewing the driver we use on 20.04 I then searched the kernel
logs and found that the ite-cir driver failed to load due to error -16.

```
2024-04-19T13:44:51.873060+00:00 host kernel: rc rc0: ITE8708 CIR transceiver 
as /devices/pnp0/00:03/rc/rc0
2024-04-19T13:44:51.873062+00:00 host kernel: rc rc0: lirc_dev: driver ite-cir 
registered at minor = 0, raw IR receiver, raw IR transmitter
2024-04-19T13:44:51.873070+00:00 host kernel: input: ITE8708 CIR transceiver as 
/devices/pnp0/00:03/rc/rc0/input6
2024-04-19T13:44:51.873072+00:00 host kernel: i2c i2c-2: 2/2 memory slots 
populated (from DMI)
2024-04-19T13:44:51.873076+00:00 host kernel: i2c i2c-2: Successfully 
instantiated SPD at 0x50
2024-04-19T13:44:51.873078+00:00 host kernel: ite-cir: probe of 00:03 failed 
with error -16
```

I reviewed kernel error message and this error is due to the
device/resource is busy or in use.  My colleague and I reviewed the ite-
cir driver source code and noticed the driver initialisation succeeds up
until L1404
https://github.com/torvalds/linux/blob/master/drivers/media/rc/ite-
cir.c#L1404 where it attempts to request_region, if it fails to do this
it will unregister the device.

The request region allocates a place in memory for the device to use, we
believe it’s using the ioport.h’s request region function
https://github.com/torvalds/linux/blob/master/include/linux/ioport.h#L278

When we added some debug lines to ite-cir we noticed that the memory
reference it is trying to allocate is 02f8-02ff. We checked the ioports
on 24.04 and noticed that the serial driver was taking up this reference
in memory when in 20.04 (The OS we currently use) and 23.04 it would
not.

Ubuntu 24.04 ioports

```
user@host:~$ sudo cat /proc/ioports
-0cf7 : PCI Bus :00
  02f8-02ff : serial
  03f8-03ff : serial
```

Ubuntu 20.04 ioports memory allocation

```
user@host:~$ sudo cat /proc/ioports
-0cf7 : PCI Bus :00
  02f8-02ff : ite-cir
  03f8-03ff : serial
```

When we investigated any changes that might cause this, we came with two
potential commits that were released in 6.5 that might have caused this
issue:

* 
https://github.com/torvalds/linux/commit/9d86719f8769244dc99b8cb6091c41eae3fd684f
* 
https://github.com/torvalds/linux/commit/84a9582fd203063cd4d301204971ff2cd8327f1a

The serial changes allow 16550/8250 driver to consume as many serial
ports as they require initializing the driver, originally they only used
1.  Due to this we noticed that when we checked the serial ports in use
by the device that 8250 was consuming the place in memory that ite-cir
should.

Ubuntu 24.04

```
user@host:~$ sudo setserial -g /dev/ttyS*
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: 8250, Port: 0x02f8, IRQ: 3
```

Ubuntu 20.04

```
user@host:~$ sudo setserial -g /dev/ttyS*
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3
```
[Regression]
We believe that the regression started from 6.5 kernel onwards based on the 
commit changes that were done to the serial driver that shipped to those 
kernels.  23.04 that uses 6.2 works as expected and shows no issues with using 
the serial port for IR while 23.10 that uses 6.5 and 24.04 that uses 6.8 does 
not load the ite-cir driver.

[Reproducible steps]

* Use Ubuntu 23.10 + or use Kernel 6.5+
* Use IR hardware that requires the ite-cir driver to be loaded
* Attempt to load ite-cir driver on boot of OS
* Check /var/log/kern.log for ite-cir driver failure

[Fix]

The requested solution would be to either:

* Set the serial driver to no longer consume more than 1 serial port
* Have the serial driver check what memory reference ite-cir driver needs to 
load, ignore that reference and then consume another point in memory instead.

We have found a workaround where we set the /etc/default/grub config to
make the 8250 use only 1 UART port, this allows ite-cir to consume the
port in memory like it use to, enabling us to use the driver again

/etc/default/grub

```
GRUB_CMDLINE_LINUX_DEFAULT="8250.nr_uarts=1"
```
The alternative fix is to have a startup script that will remove 8250 from 
using /dev/ttyS1 and then remove and re-add the ite-cir driver

```
#!/bin/bash

setserial /dev/ttyS1 uart none
modprobe -r ite-cir

```

[Diagnostic information]

version

```
Linux 

[Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update

[James Fox]

The fix hasn't been released yet.

"Fix Committed" status means the source has been updated but hasn't been
released in a package.

"Fix Released" status means the new package has the fix.

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

Title:
  The keyboard does not work after latest kernel update

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  SRU Justification:
  ==
  [Impact]
  Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
  versions.

  [Fix]
  Regression commit is found commit:
  936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")

  Fixes:
  9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
  skipping ATKBD_CMD_GETID
  683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
  ATKBD_CMD_GETID

  [Test]
  Tested on hardware, keyboard works fine after bootup.

  The regression commit is only in 6.5 stable, so SRU for 6.5 only.

  [Where problems could occur]
  It may break keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2060727] Re: The keyboard does not work after latest kernel update

[James Fox]

I have a Dell XPS 13 running Kubuntu 22.04. Keyboard works fine on fresh
boot but the keyboard doesnt work at all after resuming from suspend.

linux-image-6.5.0-27-generic is the kernel I started having the problem
with.

Booting an older 6.5 kernel and keyboard works again after resume.

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

Title:
  The keyboard does not work after latest kernel update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2058750] Re: i915 GPU HANG: ecode 12:1:db96edba

[James Chancellor]

Another crash (viewing satellite images on windy.com) with a different
ecode:

Apr 13 20:32:58 james-xps kernel: [1286582.354762] i915 :00:02.0: [drm] 
*ERROR* GT0: GUC: Engine reset failed on 0:0 (rcs0) because 0x
Apr 13 20:32:58 james-xps kernel: [1286582.404294] i915 :00:02.0: [drm] GPU 
HANG: ecode 12:1:84db, in CanvasRenderer [366470]
Apr 13 20:32:58 james-xps kernel: [1286582.404465] i915 :00:02.0: [drm] 
Resetting chip for GuC failed to reset engine mask=0x1
Apr 13 20:32:58 james-xps kernel: [1286582.507012] i915 :00:02.0: [drm] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Apr 13 20:32:58 james-xps kernel: [1286582.507733] i915 :00:02.0: [drm] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Apr 13 20:32:58 james-xps kernel: [1286582.507886] i915 :00:02.0: [drm] 
CanvasRenderer[366470] context reset due to GPU hang
Apr 13 20:32:58 james-xps kernel: [1286582.507988] i915 :00:02.0: [drm] 
GT0: GuC firmware i915/adlp_guc_70.bin version 70.5.1
Apr 13 20:32:58 james-xps kernel: [1286582.507997] i915 :00:02.0: [drm] 
GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
Apr 13 20:32:58 james-xps kernel: [1286582.524574] i915 :00:02.0: [drm] 
GT0: HuC: authenticated for all workloads
Apr 13 20:32:58 james-xps kernel: [1286582.525447] i915 :00:02.0: [drm] 
GT0: GUC: submission enabled
Apr 13 20:32:58 james-xps kernel: [1286582.525448] i915 :00:02.0: [drm] 
GT0: GUC: SLPC enabled

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

Title:
  i915 GPU HANG: ecode 12:1:db96edba

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

Bug description:
  This has happened several times over a period of months when visiting
  the site https://www.windy.com and viewing satellite images. The
  computer completely freezes and must be hard restarted. I don't think
  I have triggered this freeze by visiting any other site.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 14:14:41 2024
  InstallationDate: Installed on 2023-04-12 (344 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2058750/+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 2058750] Re: i915 GPU HANG: ecode 12:1:db96edba

[James Chancellor]

Sorry, I'm not sure what information was automatically attached to this
report generated with the command `ubuntu-bug linux` but here is a
snippet from the `syslog`:

```
Mar 22 14:01:45 james-xps kernel: [271888.137758] i915 :00:02.0: [drm] 
*ERROR* GT0: GUC: Engine reset failed on 0:0 (rcs0) because 0x
Mar 22 14:01:45 james-xps kernel: [271888.191936] i915 :00:02.0: [drm] GPU 
HANG: ecode 12:1:db96edba, in CanvasRenderer [2738]
Mar 22 14:01:45 james-xps kernel: [271888.192116] i915 :00:02.0: [drm] 
Resetting chip for GuC failed to reset engine mask=0x1
Mar 22 14:01:45 james-xps kernel: [271888.297138] i915 :00:02.0: [drm] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Mar 22 14:01:45 james-xps kernel: [271888.297885] i915 :00:02.0: [drm] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Mar 22 14:01:45 james-xps kernel: [271888.298023] i915 :00:02.0: [drm] 
CanvasRenderer[2738] context reset due to GPU hang
Mar 22 14:01:45 james-xps kernel: [271888.298126] i915 :00:02.0: [drm] GT0: 
GuC firmware i915/adlp_guc_70.bin version 70.5.1
Mar 22 14:01:45 james-xps kernel: [271888.298139] i915 :00:02.0: [drm] GT0: 
HuC firmware i915/tgl_huc.bin version 7.9.3
Mar 22 14:01:45 james-xps kernel: [271888.321405] i915 :00:02.0: [drm] GT0: 
HuC: authenticated for all workloads
Mar 22 14:01:45 james-xps kernel: [271888.326098] i915 :00:02.0: [drm] GT0: 
GUC: submission enabled
Mar 22 14:01:45 james-xps kernel: [271888.326099] i915 :00:02.0: [drm] GT0: 
GUC: SLPC enabled
```

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

Title:
  i915 GPU HANG: ecode 12:1:db96edba

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

Bug description:
  This has happened several times over a period of months when visiting
  the site https://www.windy.com and viewing satellite images. The
  computer completely freezes and must be hard restarted. I don't think
  I have triggered this freeze by visiting any other site.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 14:14:41 2024
  InstallationDate: Installed on 2023-04-12 (344 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2058750/+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 2058750] [NEW] i915 GPU HANG: ecode 12:1:db96edba

[James Chancellor]

Public bug reported:

This has happened several times over a period of months when visiting
the site https://www.windy.com and viewing satellite images. The
computer completely freezes and must be hard restarted. I don't think I
have triggered this freeze by visiting any other site.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 22 14:14:41 2024
InstallationDate: Installed on 2023-04-12 (344 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  i915 GPU HANG: ecode 12:1:db96edba

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

Bug description:
  This has happened several times over a period of months when visiting
  the site https://www.windy.com and viewing satellite images. The
  computer completely freezes and must be hard restarted. I don't think
  I have triggered this freeze by visiting any other site.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 14:14:41 2024
  InstallationDate: Installed on 2023-04-12 (344 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2058750/+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 2048768] Re: Autopkgtest failures on amd64

[James Paton-Smith]

This issue might also affect 22.04 with the HWE kernel

Going from kernel 6.5.0-21 to 6.5.0-25, we're seeing the same change in
kernel parameters

On a system with kernel 6.5.0-21 I have these kernel parameters set:
vm.mmap_rnd_bits = 28
vm.mmap_rnd_compat_bits = 8

On a system with the new kernel 6.5.0-25:
vm.mmap_rnd_bits = 32
vm.mmap_rnd_compat_bits = 16

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

Title:
  Autopkgtest failures on amd64

Status in linux package in Ubuntu:
  Confirmed
Status in llvm-toolchain-14 package in Ubuntu:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in llvm-toolchain-14 source package in Noble:
  Confirmed

Bug description:
  Some tests related to the address sanitizer are occasionally failing
  on amd64 (also for llvm-toolchain-15 and 16):

  --
  FAIL: LLVM regression suite :: test_leaksan.c (38 of 45)
  746s  TEST 'LLVM regression suite :: test_leaksan.c' 
FAILED 
  746s Script:
  746s --
  746s : 'RUN: at line 4';   /usr/bin/clang-14 -o 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
-fsanitize=address -g 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c
  746s : 'RUN: at line 5';   env ASAN_OPTIONS="log_path=stdout:exitcode=0"  
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
2>&1 > 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  746s : 'RUN: at line 6';   grep -q "detected memory leaks" 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  746s --
  746s Exit Code: 139
  746s
  746s Command Output (stderr):
  746s --
  746s 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script:
 line 3:  3335 Segmentation fault  (core dumped) env 
ASAN_OPTIONS="log_path=stdout:exitcode=0" 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
2>&1 > 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  --

  If you run the test manually you'll notice that it works but
  eventually crashes:

  
  
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ 
./test_leaksan.c.tmp

  =
  ==8631==ERROR: LeakSanitizer: detected memory leaks

  Direct leak of 7 byte(s) in 1 object(s) allocated from:
  #0 0x5e9c3441ed12 in __interceptor_malloc 
(/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12)
 (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193)
  #1 0x5e9c3445acb8 in main 
/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7
  #2 0x7e84e1e280cf  (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: 
f0b834daa3d05a80967e9ec2f990a1ea71c958fa)

  SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s).
  
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ 
./test_leaksan.c.tmp

  =
  ==8634==ERROR: LeakSanitizer: detected memory leaks

  Direct leak of 7 byte(s) in 1 object(s) allocated from:
  #0 0x5f19be5f6d12 in __interceptor_malloc 
(/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12)
 (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193)
  #1 0x5f19be632cb8 in main 
/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7
  #2 0x77c7d3c280cf  (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: 
f0b834daa3d05a80967e9ec2f990a1ea71c958fa)

  SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s).

  
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ 
./test_leaksan.c.tmp
  Segmentation fault (core dumped)
  

  After some investigation I found that it will not fail with ASLR
  disabled:

  sudo sysctl kernel.randomize_va_space=0

  while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0"
  ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ;
  fi done

  If you enable ASLR it will start to crash:

  $ sudo sysctl kernel.randomize_va_space=2

  $ while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" 
./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done
  Segmentation fault (core dumped)
  crashed
  Segmentation fault (core dumped)
  crashed
  Segmentation fault (core dumped)
  crashed
  Segmentation fault (core dumped)
  crashed
  Segmentation fault (core dumped)
  crashed

  If you enable ASLR again and run it with "setarch -R" (to disable ASLR
  for this binary), it will also not crash.

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


-- 
Mailing list: 

[Kernel-packages] [Bug 2056800] Re: Bluetooth adapter not working ATS2851

[James Alford-Allan]

Here is another post, it's a unresolved issue
https://bbs.archlinux.org/viewtopic.php?id=280693=2

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

Title:
  Bluetooth adapter not working ATS2851

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hi, I purchased this adapter: https://www.amazon.co.uk/Maxuni-
  Bluetooth-Computer-Receiver-Keyboard/dp/B0BQ3964FP

  It doesn't currently work on Linux due to a firmware bug.

  The fixes are documented on the web:

  https://www.linuxcompatible.org/story/xanmod-linux-kernel-618-released/
  "Bluetooth: Fix issue with Actions Semi ATS2851 based devices"

  
https://github.com/xanmod/linux/commit/00f4b7c036814009e54ae2841c188fe064717ddf


  This is what it shows up as: 
  Bus 001 Device 012: ID 10d7:b012 Actions general adapter

  My kernel version is 6.5.0-25-generic

  Anyone know how this is fixed? Im running Ubuntu 23.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2056800/+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 2056800] [NEW] Bluetooth adapter not working ATS2851

[James Alford-Allan]

Public bug reported:

Hi, I purchased this adapter: https://www.amazon.co.uk/Maxuni-Bluetooth-
Computer-Receiver-Keyboard/dp/B0BQ3964FP

It doesn't currently work on Linux due to a firmware bug.

The fixes are documented on the web:

https://www.linuxcompatible.org/story/xanmod-linux-kernel-618-released/
"Bluetooth: Fix issue with Actions Semi ATS2851 based devices"

https://github.com/xanmod/linux/commit/00f4b7c036814009e54ae2841c188fe064717ddf


This is what it shows up as: 
Bus 001 Device 012: ID 10d7:b012 Actions general adapter

My kernel version is 6.5.0-25-generic

Anyone know how this is fixed? Im running Ubuntu 23.10

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


** Tags: bluetooth

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

Title:
  Bluetooth adapter not working ATS2851

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hi, I purchased this adapter: https://www.amazon.co.uk/Maxuni-
  Bluetooth-Computer-Receiver-Keyboard/dp/B0BQ3964FP

  It doesn't currently work on Linux due to a firmware bug.

  The fixes are documented on the web:

  https://www.linuxcompatible.org/story/xanmod-linux-kernel-618-released/
  "Bluetooth: Fix issue with Actions Semi ATS2851 based devices"

  
https://github.com/xanmod/linux/commit/00f4b7c036814009e54ae2841c188fe064717ddf


  This is what it shows up as: 
  Bus 001 Device 012: ID 10d7:b012 Actions general adapter

  My kernel version is 6.5.0-25-generic

  Anyone know how this is fixed? Im running Ubuntu 23.10

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


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

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

[james anderson]

one of the best information be like the  https://rugnroll.com.au

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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

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

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

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

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


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

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

[james anderson]

thanks for sharing you can visit to the https://advancewithai.net/ai-
image-generators/leonardo-ai.html

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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

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

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

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

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


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

[Kernel-packages] [Bug 2049976] Re: Analog VGA goes black on resume

[James Cobban]

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

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

Title:
  Analog VGA goes black on resume

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Starting a few weeks ago after applying regular maintenance to 22.04.3
  LTS one of my two displays, an LG 22MP47HQ-P connected to my tower by
  a D-Sub cable, blinked multiple times immediately on resume from
  suspend.  My second display which is connected using HDMI works
  normally. This, of course, was merely a mild annoyance because after a
  few seconds it stopped. However in the past week that same display
  flashes on, and then goes black. I power the display off and back on
  and again it flashes on for a fraction of a second and then goes
  black. After several power cycles of the display it stays on, so again
  this is only a mild annoyance. Is this a known issue with a recent
  update?

  Specifically this is after a deep suspend, one where on unlock you
  need to press a key to get the login prompt.

  I tried updating to 23.10 but the problem is there as well.

  This bug tool does not permit reporting a problem against Wayland.

  lshw -C video
  *-display
  description: VGA compatible controller
  product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
  vendor: Intel Corporation
  physical id: 2
  bus info: pci@:00:02.0
  logical name: /dev/fb0
  version: 06
  width: 64 bits
  clock: 33MHz
  capabilities: msi pm vga_controller bus_master cap_list rom fb
  configuration: depth=32 driver=i915 latency=0 resolution=1920,1080
  resources: irq:31 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64) memory:c-d

  /var/log/apt/history.log taken immediately after encountering the
  issue on 22.04

  Start-Date: 2024-01-02 16:01:30
  Commandline: aptdaemon role='role-commit-packages' sender=':1.7295'
  Upgrade: thunderbird:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en:amd64 
(1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), 
thunderbird-locale-en-gb:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 
(1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), 
thunderbird-gnome-support:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1)
  End-Date: 2024-01-02 16:01:33

  Start-Date: 2024-01-03 16:57:04
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsqlite3-dev:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), 
libsqlite3-0:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), sqlite3:amd64 
(3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3)
  End-Date: 2024-01-03 16:57:05

  Start-Date: 2024-01-03 16:57:08
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: openssh-client:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), 
openssh-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), 
openssh-sftp-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6)
  End-Date: 2024-01-03 16:57:10

  Start-Date: 2024-01-03 16:57:13
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libnode72:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), 
nodejs:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), 
libnode-dev:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3)
  End-Date: 2024-01-03 16:57:14

  Start-Date: 2024-01-03 16:57:16
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: nodejs-doc:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3)
  End-Date: 2024-01-03 16:57:17

  Start-Date: 2024-01-09 20:43:19
  Commandline: aptdaemon role='role-commit-packages' sender=':1.9514'
  Install: php8.3-xml:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-mbstring:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-common:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-intl:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic)
  Upgrade: php-common:amd64 (2:93+ubuntu22.04.1+deb.sury.org+3, 
2:94+ubuntu22.04.1+deb.sury.org+1), software-properties-common:amd64 
(0.99.22.8, 0.99.22.9), python3-software-properties:amd64 (0.99.22.8, 
0.99.22.9), php-intl:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 
2:8.3+94+ubuntu22.04.1+deb.sury.org+1), php-mbstring:amd64 
(2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), 
software-properties-gtk:amd64 (0.99.22.8, 0.99.22.9), python3-distro-info:amd64 
(1.1ubuntu0.1, 1.1ubuntu0.2), distro-info-data:amd64 (0.52ubuntu0.5, 
0.52ubuntu0.6), linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.23, 
20220329.git681281e4-0ubuntu3.24), php-xml:amd64 
(2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), 
distro-info:amd64 (1.1ubuntu0.1, 1.1ubuntu0.2)
  End-Date: 2024-01-09 20:45:50

  Start-Date: 2024-01-10 21:58:10
  Commandline: 

[Kernel-packages] [Bug 2049976] Re: Analog VGA goes black on resume

[James Cobban]

After replacing the VGA cable with a Display Port to HDMI cable the
problem persists.  Presumably the backlight on the LCD display is
failing.  It is over five years old, so this is forgivable.  I will
order a new display.

Thank for your patience and consideration.

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

Title:
  Analog VGA goes black on resume

Status in linux package in Ubuntu:
  New

Bug description:
  Starting a few weeks ago after applying regular maintenance to 22.04.3
  LTS one of my two displays, an LG 22MP47HQ-P connected to my tower by
  a D-Sub cable, blinked multiple times immediately on resume from
  suspend.  My second display which is connected using HDMI works
  normally. This, of course, was merely a mild annoyance because after a
  few seconds it stopped. However in the past week that same display
  flashes on, and then goes black. I power the display off and back on
  and again it flashes on for a fraction of a second and then goes
  black. After several power cycles of the display it stays on, so again
  this is only a mild annoyance. Is this a known issue with a recent
  update?

  Specifically this is after a deep suspend, one where on unlock you
  need to press a key to get the login prompt.

  I tried updating to 23.10 but the problem is there as well.

  This bug tool does not permit reporting a problem against Wayland.

  lshw -C video
  *-display
  description: VGA compatible controller
  product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
  vendor: Intel Corporation
  physical id: 2
  bus info: pci@:00:02.0
  logical name: /dev/fb0
  version: 06
  width: 64 bits
  clock: 33MHz
  capabilities: msi pm vga_controller bus_master cap_list rom fb
  configuration: depth=32 driver=i915 latency=0 resolution=1920,1080
  resources: irq:31 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64) memory:c-d

  /var/log/apt/history.log taken immediately after encountering the
  issue on 22.04

  Start-Date: 2024-01-02 16:01:30
  Commandline: aptdaemon role='role-commit-packages' sender=':1.7295'
  Upgrade: thunderbird:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en:amd64 
(1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), 
thunderbird-locale-en-gb:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 
(1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), 
thunderbird-gnome-support:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1)
  End-Date: 2024-01-02 16:01:33

  Start-Date: 2024-01-03 16:57:04
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsqlite3-dev:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), 
libsqlite3-0:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), sqlite3:amd64 
(3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3)
  End-Date: 2024-01-03 16:57:05

  Start-Date: 2024-01-03 16:57:08
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: openssh-client:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), 
openssh-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), 
openssh-sftp-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6)
  End-Date: 2024-01-03 16:57:10

  Start-Date: 2024-01-03 16:57:13
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libnode72:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), 
nodejs:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), 
libnode-dev:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3)
  End-Date: 2024-01-03 16:57:14

  Start-Date: 2024-01-03 16:57:16
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: nodejs-doc:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3)
  End-Date: 2024-01-03 16:57:17

  Start-Date: 2024-01-09 20:43:19
  Commandline: aptdaemon role='role-commit-packages' sender=':1.9514'
  Install: php8.3-xml:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-mbstring:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-common:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-intl:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic)
  Upgrade: php-common:amd64 (2:93+ubuntu22.04.1+deb.sury.org+3, 
2:94+ubuntu22.04.1+deb.sury.org+1), software-properties-common:amd64 
(0.99.22.8, 0.99.22.9), python3-software-properties:amd64 (0.99.22.8, 
0.99.22.9), php-intl:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 
2:8.3+94+ubuntu22.04.1+deb.sury.org+1), php-mbstring:amd64 
(2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), 
software-properties-gtk:amd64 (0.99.22.8, 0.99.22.9), python3-distro-info:amd64 
(1.1ubuntu0.1, 1.1ubuntu0.2), distro-info-data:amd64 (0.52ubuntu0.5, 
0.52ubuntu0.6), linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.23, 
20220329.git681281e4-0ubuntu3.24), php-xml:amd64 

[Kernel-packages] [Bug 2049976] Re: Analog VGA goes black on resume

[James Cobban]

Thank you for responding.  Please bear in mind that I have been using
this same computer and this same monitor configuration for over five
years, and only in the past three weeks since I originally reported this
problem have I had this issue.  I did not change the hardware before the
problem arose.  However since my computer has two DisplayPort 1.2
outputs I will try connecting the failing display using a DisplayPort to
HDMI cable, the same way the working display is connected.

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

Title:
  Analog VGA goes black on resume

Status in linux package in Ubuntu:
  New

Bug description:
  Starting a few weeks ago after applying regular maintenance to 22.04.3
  LTS one of my two displays, an LG 22MP47HQ-P connected to my tower by
  a D-Sub cable, blinked multiple times immediately on resume from
  suspend.  My second display which is connected using HDMI works
  normally. This, of course, was merely a mild annoyance because after a
  few seconds it stopped. However in the past week that same display
  flashes on, and then goes black. I power the display off and back on
  and again it flashes on for a fraction of a second and then goes
  black. After several power cycles of the display it stays on, so again
  this is only a mild annoyance. Is this a known issue with a recent
  update?

  Specifically this is after a deep suspend, one where on unlock you
  need to press a key to get the login prompt.

  I tried updating to 23.10 but the problem is there as well.

  This bug tool does not permit reporting a problem against Wayland.

  lshw -C video
  *-display
  description: VGA compatible controller
  product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
  vendor: Intel Corporation
  physical id: 2
  bus info: pci@:00:02.0
  logical name: /dev/fb0
  version: 06
  width: 64 bits
  clock: 33MHz
  capabilities: msi pm vga_controller bus_master cap_list rom fb
  configuration: depth=32 driver=i915 latency=0 resolution=1920,1080
  resources: irq:31 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64) memory:c-d

  /var/log/apt/history.log taken immediately after encountering the
  issue on 22.04

  Start-Date: 2024-01-02 16:01:30
  Commandline: aptdaemon role='role-commit-packages' sender=':1.7295'
  Upgrade: thunderbird:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en:amd64 
(1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), 
thunderbird-locale-en-gb:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 
(1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), 
thunderbird-gnome-support:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1)
  End-Date: 2024-01-02 16:01:33

  Start-Date: 2024-01-03 16:57:04
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsqlite3-dev:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), 
libsqlite3-0:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), sqlite3:amd64 
(3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3)
  End-Date: 2024-01-03 16:57:05

  Start-Date: 2024-01-03 16:57:08
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: openssh-client:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), 
openssh-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), 
openssh-sftp-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6)
  End-Date: 2024-01-03 16:57:10

  Start-Date: 2024-01-03 16:57:13
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libnode72:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), 
nodejs:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), 
libnode-dev:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3)
  End-Date: 2024-01-03 16:57:14

  Start-Date: 2024-01-03 16:57:16
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: nodejs-doc:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3)
  End-Date: 2024-01-03 16:57:17

  Start-Date: 2024-01-09 20:43:19
  Commandline: aptdaemon role='role-commit-packages' sender=':1.9514'
  Install: php8.3-xml:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-mbstring:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-common:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-intl:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic)
  Upgrade: php-common:amd64 (2:93+ubuntu22.04.1+deb.sury.org+3, 
2:94+ubuntu22.04.1+deb.sury.org+1), software-properties-common:amd64 
(0.99.22.8, 0.99.22.9), python3-software-properties:amd64 (0.99.22.8, 
0.99.22.9), php-intl:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 
2:8.3+94+ubuntu22.04.1+deb.sury.org+1), php-mbstring:amd64 
(2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), 
software-properties-gtk:amd64 (0.99.22.8, 0.99.22.9), 

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

[james kaelso]

In the Ubuntu ecosystem, the "-proposed" repository is used for testing
updates before they are officially released. If you are referring to the
Linux kernel version 4.4.0-41.61 proposed update in the Ubuntu
environment visit to the https://startfleet.io/

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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

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

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

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

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


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

[Kernel-packages] [Bug 2048526] Re: linux 5.15.0: repeated warnings from fs/inode.c:265 __destroy_inode+0x143/0x180

[James Dingwall]

Prior to running 5.15.0-85 we were using 5.15.0-79 where the problem was
not observed.  Between these two releases it looks like
https://github.com/torvalds/linux/commit/36ce9d76b0a93bae799e27e4f5ac35478c676592
was added to the Ubuntu tree.  As that relates to tmpfs superblock
operations and the warning seems to be coming from that area is there an
issue with that backport?

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

Title:
  linux 5.15.0: repeated warnings from fs/inode.c:265
  __destroy_inode+0x143/0x180

Status in linux-meta package in Ubuntu:
  New

Bug description:
  The kernel is a rebuild of the Ubuntu source tree with a small number
  of xen related patches.  On a small percentage of boots we encounter a
  repeated kernel warning which comes from fs/inode.c:

  if (!inode->i_nlink) {
  WARN_ON(atomic_long_read(>i_sb->s_remove_count) == 0);
  atomic_long_dec(>i_sb->s_remove_count);
  }

  Using strace to attach to the pid logged in the warning the filesystem
  is a tmpfs (either separate, e.g. /run or as the writeable layer of an
  aufs overlay for /).  This can be raised for different filesystem
  operations, in this example do_unlinkat, others do_renameat2.  The
  problem does not seem to be hardware specific as we have encountered
  on five different systems.

  [Wed Nov 29 10:51:47 2023] [ cut here ]
  [Wed Nov 29 10:51:47 2023] WARNING: CPU: 2 PID: 3295469 at fs/inode.c:265 
__destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023] Modules linked in: tcp_diag udp_diag inet_diag 
cls_cgroup sch_htb drbd_transport_tcp(OE) handshake(OE) drbd(OE) lru_cache 
bridge stp llc xt_owner xt_multiport xt_hl xt_tcpudp xt_state xt_conntrack 
xt_NFLOG ip6
  table_raw iptable_raw ip6table_mangle iptable_mangle ip6table_nat iptable_nat 
nf_nat ip6table_filter ip6_tables iptable_filter bpfilter dell_rbu 
nfnetlink_log nfnetlink i40e dcdbas igb ipmi_ssif joydev input_leds mei_me mei 
ioatdma inte
  l_pch_thermal dca acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler 
acpi_power_meter mac_hid sch_fq_codel xen_pciback xen_netback xen_blkback 
xen_gntalloc xen_gntdev xen_evtchn ramoops reed_solomon pstore_blk pstore_zone 
xenfs ip_tables x_
  tables autofs4 raid10 raid0 multipath linear xen_privcmd zstd zstd_compress 
zram zfs(POE) zunicode(POE) zzstd(O) zlua(OE) zavl(POE) icp(POE) zcommon(POE) 
znvpair(POE) spl(OE) nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 aufs raid1 
dm_raid
   raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
  [Wed Nov 29 10:51:47 2023]  hid_generic usbhid hid raid6_pq libcrc32c ast 
i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core ahci i2c_i801 xhci_pci efi_pstore 
drm i2c
  _smbus libahci xhci_pci_renesas wmi
  [Wed Nov 29 10:51:47 2023] CPU: 2 PID: 3295469 Comm: nano Tainted: PW 
 OE 5.15.0-91-generic #101~20.04.1zynstra1
  [Wed Nov 29 10:51:47 2023] Hardware name: Supermicro 
SYS-5019D-FN8TP-5-NC041/X11SDV-4C-TP8F, BIOS 1.2 11/14/2019
  [Wed Nov 29 10:51:47 2023] RIP: e030:__destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023] Code: 83 c7 08 e8 5f 3f da ff eb 93 be 08 00 00 00 
48 83 c7 08 e8 4f 3f da ff eb 92 0f 0b 0f 0b e9 25 ff ff ff 0f 0b e9 f0 fe ff 
ff <0f> 0b e9 55 ff ff ff 48 8b 90 60 02 00 00 f0 48 83 2a 01 0f 85 00
  [Wed Nov 29 10:51:47 2023] RSP: e02b:c9004c4a3d80 EFLAGS: 00010246
  [Wed Nov 29 10:51:47 2023] RAX: 88812d892000 RBX: 88816be64b18 RCX: 
4e01
  [Wed Nov 29 10:51:47 2023] RDX:  RSI: 0001 RDI: 
88816be64b18
  [Wed Nov 29 10:51:47 2023] RBP: c9004c4a3d88 R08: 0001 R09: 
0064
  [Wed Nov 29 10:51:47 2023] R10: 8261d3de R11: 0003 R12: 
c031a340
  [Wed Nov 29 10:51:47 2023] R13: 88816be64ba0 R14: 88816be64b18 R15: 
8881727c8180
  [Wed Nov 29 10:51:47 2023] FS:  7fdee76d0040() 
GS:889046c8() knlGS:
  [Wed Nov 29 10:51:47 2023] CS:  e030 DS:  ES:  CR0: 80050033
  [Wed Nov 29 10:51:47 2023] CR2: 7fbce67eeff0 CR3: 000fc6a84000 CR4: 
00050660
  [Wed Nov 29 10:51:47 2023] Call Trace:
  [Wed Nov 29 10:51:47 2023]  
  [Wed Nov 29 10:51:47 2023]  ? show_trace_log_lvl+0x1d6/0x2ea
  [Wed Nov 29 10:51:47 2023]  ? show_trace_log_lvl+0x1d6/0x2ea
  [Wed Nov 29 10:51:47 2023]  ? destroy_inode+0x2f/0x80
  [Wed Nov 29 10:51:47 2023]  ? show_regs.part.0+0x23/0x29
  [Wed Nov 29 10:51:47 2023]  ? show_regs.cold+0x8/0xd
  [Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023]  ? __warn+0x8c/0x100
  [Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023]  ? report_bug+0xa4/0xd0
  [Wed Nov 29 10:51:47 2023]  ? handle_bug+0x39/0x90
  [Wed Nov 29 

[Kernel-packages] [Bug 2048526] Re: linux 5.15.0: repeated warnings from fs/inode.c:265 __destroy_inode+0x143/0x180

[James Dingwall]

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2048526/+attachment/5737421/+files/uname-a.log

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

Title:
  linux 5.15.0: repeated warnings from fs/inode.c:265
  __destroy_inode+0x143/0x180

Status in linux-meta package in Ubuntu:
  New

Bug description:
  The kernel is a rebuild of the Ubuntu source tree with a small number
  of xen related patches.  On a small percentage of boots we encounter a
  repeated kernel warning which comes from fs/inode.c:

  if (!inode->i_nlink) {
  WARN_ON(atomic_long_read(>i_sb->s_remove_count) == 0);
  atomic_long_dec(>i_sb->s_remove_count);
  }

  Using strace to attach to the pid logged in the warning the filesystem
  is a tmpfs (either separate, e.g. /run or as the writeable layer of an
  aufs overlay for /).  This can be raised for different filesystem
  operations, in this example do_unlinkat, others do_renameat2.  The
  problem does not seem to be hardware specific as we have encountered
  on five different systems.

  [Wed Nov 29 10:51:47 2023] [ cut here ]
  [Wed Nov 29 10:51:47 2023] WARNING: CPU: 2 PID: 3295469 at fs/inode.c:265 
__destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023] Modules linked in: tcp_diag udp_diag inet_diag 
cls_cgroup sch_htb drbd_transport_tcp(OE) handshake(OE) drbd(OE) lru_cache 
bridge stp llc xt_owner xt_multiport xt_hl xt_tcpudp xt_state xt_conntrack 
xt_NFLOG ip6
  table_raw iptable_raw ip6table_mangle iptable_mangle ip6table_nat iptable_nat 
nf_nat ip6table_filter ip6_tables iptable_filter bpfilter dell_rbu 
nfnetlink_log nfnetlink i40e dcdbas igb ipmi_ssif joydev input_leds mei_me mei 
ioatdma inte
  l_pch_thermal dca acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler 
acpi_power_meter mac_hid sch_fq_codel xen_pciback xen_netback xen_blkback 
xen_gntalloc xen_gntdev xen_evtchn ramoops reed_solomon pstore_blk pstore_zone 
xenfs ip_tables x_
  tables autofs4 raid10 raid0 multipath linear xen_privcmd zstd zstd_compress 
zram zfs(POE) zunicode(POE) zzstd(O) zlua(OE) zavl(POE) icp(POE) zcommon(POE) 
znvpair(POE) spl(OE) nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 aufs raid1 
dm_raid
   raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
  [Wed Nov 29 10:51:47 2023]  hid_generic usbhid hid raid6_pq libcrc32c ast 
i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core ahci i2c_i801 xhci_pci efi_pstore 
drm i2c
  _smbus libahci xhci_pci_renesas wmi
  [Wed Nov 29 10:51:47 2023] CPU: 2 PID: 3295469 Comm: nano Tainted: PW 
 OE 5.15.0-91-generic #101~20.04.1zynstra1
  [Wed Nov 29 10:51:47 2023] Hardware name: Supermicro 
SYS-5019D-FN8TP-5-NC041/X11SDV-4C-TP8F, BIOS 1.2 11/14/2019
  [Wed Nov 29 10:51:47 2023] RIP: e030:__destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023] Code: 83 c7 08 e8 5f 3f da ff eb 93 be 08 00 00 00 
48 83 c7 08 e8 4f 3f da ff eb 92 0f 0b 0f 0b e9 25 ff ff ff 0f 0b e9 f0 fe ff 
ff <0f> 0b e9 55 ff ff ff 48 8b 90 60 02 00 00 f0 48 83 2a 01 0f 85 00
  [Wed Nov 29 10:51:47 2023] RSP: e02b:c9004c4a3d80 EFLAGS: 00010246
  [Wed Nov 29 10:51:47 2023] RAX: 88812d892000 RBX: 88816be64b18 RCX: 
4e01
  [Wed Nov 29 10:51:47 2023] RDX:  RSI: 0001 RDI: 
88816be64b18
  [Wed Nov 29 10:51:47 2023] RBP: c9004c4a3d88 R08: 0001 R09: 
0064
  [Wed Nov 29 10:51:47 2023] R10: 8261d3de R11: 0003 R12: 
c031a340
  [Wed Nov 29 10:51:47 2023] R13: 88816be64ba0 R14: 88816be64b18 R15: 
8881727c8180
  [Wed Nov 29 10:51:47 2023] FS:  7fdee76d0040() 
GS:889046c8() knlGS:
  [Wed Nov 29 10:51:47 2023] CS:  e030 DS:  ES:  CR0: 80050033
  [Wed Nov 29 10:51:47 2023] CR2: 7fbce67eeff0 CR3: 000fc6a84000 CR4: 
00050660
  [Wed Nov 29 10:51:47 2023] Call Trace:
  [Wed Nov 29 10:51:47 2023]  
  [Wed Nov 29 10:51:47 2023]  ? show_trace_log_lvl+0x1d6/0x2ea
  [Wed Nov 29 10:51:47 2023]  ? show_trace_log_lvl+0x1d6/0x2ea
  [Wed Nov 29 10:51:47 2023]  ? destroy_inode+0x2f/0x80
  [Wed Nov 29 10:51:47 2023]  ? show_regs.part.0+0x23/0x29
  [Wed Nov 29 10:51:47 2023]  ? show_regs.cold+0x8/0xd
  [Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023]  ? __warn+0x8c/0x100
  [Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023]  ? report_bug+0xa4/0xd0
  [Wed Nov 29 10:51:47 2023]  ? handle_bug+0x39/0x90
  [Wed Nov 29 10:51:47 2023]  ? exc_invalid_op+0x19/0x70
  [Wed Nov 29 10:51:47 2023]  ? asm_exc_invalid_op+0x1b/0x20
  [Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023]  destroy_inode+0x2f/0x80
  [Wed Nov 29 

[Kernel-packages] [Bug 2048526] Re: linux 5.15.0: repeated warnings from fs/inode.c:265 __destroy_inode+0x143/0x180

[James Dingwall]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2048526/+attachment/5737420/+files/lspci-vnvn.log

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

Title:
  linux 5.15.0: repeated warnings from fs/inode.c:265
  __destroy_inode+0x143/0x180

Status in linux-meta package in Ubuntu:
  New

Bug description:
  The kernel is a rebuild of the Ubuntu source tree with a small number
  of xen related patches.  On a small percentage of boots we encounter a
  repeated kernel warning which comes from fs/inode.c:

  if (!inode->i_nlink) {
  WARN_ON(atomic_long_read(>i_sb->s_remove_count) == 0);
  atomic_long_dec(>i_sb->s_remove_count);
  }

  Using strace to attach to the pid logged in the warning the filesystem
  is a tmpfs (either separate, e.g. /run or as the writeable layer of an
  aufs overlay for /).  This can be raised for different filesystem
  operations, in this example do_unlinkat, others do_renameat2.  The
  problem does not seem to be hardware specific as we have encountered
  on five different systems.

  [Wed Nov 29 10:51:47 2023] [ cut here ]
  [Wed Nov 29 10:51:47 2023] WARNING: CPU: 2 PID: 3295469 at fs/inode.c:265 
__destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023] Modules linked in: tcp_diag udp_diag inet_diag 
cls_cgroup sch_htb drbd_transport_tcp(OE) handshake(OE) drbd(OE) lru_cache 
bridge stp llc xt_owner xt_multiport xt_hl xt_tcpudp xt_state xt_conntrack 
xt_NFLOG ip6
  table_raw iptable_raw ip6table_mangle iptable_mangle ip6table_nat iptable_nat 
nf_nat ip6table_filter ip6_tables iptable_filter bpfilter dell_rbu 
nfnetlink_log nfnetlink i40e dcdbas igb ipmi_ssif joydev input_leds mei_me mei 
ioatdma inte
  l_pch_thermal dca acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler 
acpi_power_meter mac_hid sch_fq_codel xen_pciback xen_netback xen_blkback 
xen_gntalloc xen_gntdev xen_evtchn ramoops reed_solomon pstore_blk pstore_zone 
xenfs ip_tables x_
  tables autofs4 raid10 raid0 multipath linear xen_privcmd zstd zstd_compress 
zram zfs(POE) zunicode(POE) zzstd(O) zlua(OE) zavl(POE) icp(POE) zcommon(POE) 
znvpair(POE) spl(OE) nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 aufs raid1 
dm_raid
   raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
  [Wed Nov 29 10:51:47 2023]  hid_generic usbhid hid raid6_pq libcrc32c ast 
i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core ahci i2c_i801 xhci_pci efi_pstore 
drm i2c
  _smbus libahci xhci_pci_renesas wmi
  [Wed Nov 29 10:51:47 2023] CPU: 2 PID: 3295469 Comm: nano Tainted: PW 
 OE 5.15.0-91-generic #101~20.04.1zynstra1
  [Wed Nov 29 10:51:47 2023] Hardware name: Supermicro 
SYS-5019D-FN8TP-5-NC041/X11SDV-4C-TP8F, BIOS 1.2 11/14/2019
  [Wed Nov 29 10:51:47 2023] RIP: e030:__destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023] Code: 83 c7 08 e8 5f 3f da ff eb 93 be 08 00 00 00 
48 83 c7 08 e8 4f 3f da ff eb 92 0f 0b 0f 0b e9 25 ff ff ff 0f 0b e9 f0 fe ff 
ff <0f> 0b e9 55 ff ff ff 48 8b 90 60 02 00 00 f0 48 83 2a 01 0f 85 00
  [Wed Nov 29 10:51:47 2023] RSP: e02b:c9004c4a3d80 EFLAGS: 00010246
  [Wed Nov 29 10:51:47 2023] RAX: 88812d892000 RBX: 88816be64b18 RCX: 
4e01
  [Wed Nov 29 10:51:47 2023] RDX:  RSI: 0001 RDI: 
88816be64b18
  [Wed Nov 29 10:51:47 2023] RBP: c9004c4a3d88 R08: 0001 R09: 
0064
  [Wed Nov 29 10:51:47 2023] R10: 8261d3de R11: 0003 R12: 
c031a340
  [Wed Nov 29 10:51:47 2023] R13: 88816be64ba0 R14: 88816be64b18 R15: 
8881727c8180
  [Wed Nov 29 10:51:47 2023] FS:  7fdee76d0040() 
GS:889046c8() knlGS:
  [Wed Nov 29 10:51:47 2023] CS:  e030 DS:  ES:  CR0: 80050033
  [Wed Nov 29 10:51:47 2023] CR2: 7fbce67eeff0 CR3: 000fc6a84000 CR4: 
00050660
  [Wed Nov 29 10:51:47 2023] Call Trace:
  [Wed Nov 29 10:51:47 2023]  
  [Wed Nov 29 10:51:47 2023]  ? show_trace_log_lvl+0x1d6/0x2ea
  [Wed Nov 29 10:51:47 2023]  ? show_trace_log_lvl+0x1d6/0x2ea
  [Wed Nov 29 10:51:47 2023]  ? destroy_inode+0x2f/0x80
  [Wed Nov 29 10:51:47 2023]  ? show_regs.part.0+0x23/0x29
  [Wed Nov 29 10:51:47 2023]  ? show_regs.cold+0x8/0xd
  [Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023]  ? __warn+0x8c/0x100
  [Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023]  ? report_bug+0xa4/0xd0
  [Wed Nov 29 10:51:47 2023]  ? handle_bug+0x39/0x90
  [Wed Nov 29 10:51:47 2023]  ? exc_invalid_op+0x19/0x70
  [Wed Nov 29 10:51:47 2023]  ? asm_exc_invalid_op+0x1b/0x20
  [Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023]  destroy_inode+0x2f/0x80
  [Wed Nov 29 

[Kernel-packages] [Bug 2048526] Re: linux 5.15.0: repeated warnings from fs/inode.c:265 __destroy_inode+0x143/0x180

[James Dingwall]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2048526/+attachment/5737422/+files/version.log

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

Title:
  linux 5.15.0: repeated warnings from fs/inode.c:265
  __destroy_inode+0x143/0x180

Status in linux-meta package in Ubuntu:
  New

Bug description:
  The kernel is a rebuild of the Ubuntu source tree with a small number
  of xen related patches.  On a small percentage of boots we encounter a
  repeated kernel warning which comes from fs/inode.c:

  if (!inode->i_nlink) {
  WARN_ON(atomic_long_read(>i_sb->s_remove_count) == 0);
  atomic_long_dec(>i_sb->s_remove_count);
  }

  Using strace to attach to the pid logged in the warning the filesystem
  is a tmpfs (either separate, e.g. /run or as the writeable layer of an
  aufs overlay for /).  This can be raised for different filesystem
  operations, in this example do_unlinkat, others do_renameat2.  The
  problem does not seem to be hardware specific as we have encountered
  on five different systems.

  [Wed Nov 29 10:51:47 2023] [ cut here ]
  [Wed Nov 29 10:51:47 2023] WARNING: CPU: 2 PID: 3295469 at fs/inode.c:265 
__destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023] Modules linked in: tcp_diag udp_diag inet_diag 
cls_cgroup sch_htb drbd_transport_tcp(OE) handshake(OE) drbd(OE) lru_cache 
bridge stp llc xt_owner xt_multiport xt_hl xt_tcpudp xt_state xt_conntrack 
xt_NFLOG ip6
  table_raw iptable_raw ip6table_mangle iptable_mangle ip6table_nat iptable_nat 
nf_nat ip6table_filter ip6_tables iptable_filter bpfilter dell_rbu 
nfnetlink_log nfnetlink i40e dcdbas igb ipmi_ssif joydev input_leds mei_me mei 
ioatdma inte
  l_pch_thermal dca acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler 
acpi_power_meter mac_hid sch_fq_codel xen_pciback xen_netback xen_blkback 
xen_gntalloc xen_gntdev xen_evtchn ramoops reed_solomon pstore_blk pstore_zone 
xenfs ip_tables x_
  tables autofs4 raid10 raid0 multipath linear xen_privcmd zstd zstd_compress 
zram zfs(POE) zunicode(POE) zzstd(O) zlua(OE) zavl(POE) icp(POE) zcommon(POE) 
znvpair(POE) spl(OE) nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 aufs raid1 
dm_raid
   raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
  [Wed Nov 29 10:51:47 2023]  hid_generic usbhid hid raid6_pq libcrc32c ast 
i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core ahci i2c_i801 xhci_pci efi_pstore 
drm i2c
  _smbus libahci xhci_pci_renesas wmi
  [Wed Nov 29 10:51:47 2023] CPU: 2 PID: 3295469 Comm: nano Tainted: PW 
 OE 5.15.0-91-generic #101~20.04.1zynstra1
  [Wed Nov 29 10:51:47 2023] Hardware name: Supermicro 
SYS-5019D-FN8TP-5-NC041/X11SDV-4C-TP8F, BIOS 1.2 11/14/2019
  [Wed Nov 29 10:51:47 2023] RIP: e030:__destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023] Code: 83 c7 08 e8 5f 3f da ff eb 93 be 08 00 00 00 
48 83 c7 08 e8 4f 3f da ff eb 92 0f 0b 0f 0b e9 25 ff ff ff 0f 0b e9 f0 fe ff 
ff <0f> 0b e9 55 ff ff ff 48 8b 90 60 02 00 00 f0 48 83 2a 01 0f 85 00
  [Wed Nov 29 10:51:47 2023] RSP: e02b:c9004c4a3d80 EFLAGS: 00010246
  [Wed Nov 29 10:51:47 2023] RAX: 88812d892000 RBX: 88816be64b18 RCX: 
4e01
  [Wed Nov 29 10:51:47 2023] RDX:  RSI: 0001 RDI: 
88816be64b18
  [Wed Nov 29 10:51:47 2023] RBP: c9004c4a3d88 R08: 0001 R09: 
0064
  [Wed Nov 29 10:51:47 2023] R10: 8261d3de R11: 0003 R12: 
c031a340
  [Wed Nov 29 10:51:47 2023] R13: 88816be64ba0 R14: 88816be64b18 R15: 
8881727c8180
  [Wed Nov 29 10:51:47 2023] FS:  7fdee76d0040() 
GS:889046c8() knlGS:
  [Wed Nov 29 10:51:47 2023] CS:  e030 DS:  ES:  CR0: 80050033
  [Wed Nov 29 10:51:47 2023] CR2: 7fbce67eeff0 CR3: 000fc6a84000 CR4: 
00050660
  [Wed Nov 29 10:51:47 2023] Call Trace:
  [Wed Nov 29 10:51:47 2023]  
  [Wed Nov 29 10:51:47 2023]  ? show_trace_log_lvl+0x1d6/0x2ea
  [Wed Nov 29 10:51:47 2023]  ? show_trace_log_lvl+0x1d6/0x2ea
  [Wed Nov 29 10:51:47 2023]  ? destroy_inode+0x2f/0x80
  [Wed Nov 29 10:51:47 2023]  ? show_regs.part.0+0x23/0x29
  [Wed Nov 29 10:51:47 2023]  ? show_regs.cold+0x8/0xd
  [Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023]  ? __warn+0x8c/0x100
  [Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023]  ? report_bug+0xa4/0xd0
  [Wed Nov 29 10:51:47 2023]  ? handle_bug+0x39/0x90
  [Wed Nov 29 10:51:47 2023]  ? exc_invalid_op+0x19/0x70
  [Wed Nov 29 10:51:47 2023]  ? asm_exc_invalid_op+0x1b/0x20
  [Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
  [Wed Nov 29 10:51:47 2023]  destroy_inode+0x2f/0x80
  [Wed Nov 29 

[Kernel-packages] [Bug 2048526] [NEW] linux 5.15.0: repeated warnings from fs/inode.c:265 __destroy_inode+0x143/0x180

[James Dingwall]

Public bug reported:

The kernel is a rebuild of the Ubuntu source tree with a small number of
xen related patches.  On a small percentage of boots we encounter a
repeated kernel warning which comes from fs/inode.c:

if (!inode->i_nlink) {
WARN_ON(atomic_long_read(>i_sb->s_remove_count) == 0);
atomic_long_dec(>i_sb->s_remove_count);
}

Using strace to attach to the pid logged in the warning the filesystem
is a tmpfs (either separate, e.g. /run or as the writeable layer of an
aufs overlay for /).  This can be raised for different filesystem
operations, in this example do_unlinkat, others do_renameat2.  The
problem does not seem to be hardware specific as we have encountered on
five different systems.

[Wed Nov 29 10:51:47 2023] [ cut here ]
[Wed Nov 29 10:51:47 2023] WARNING: CPU: 2 PID: 3295469 at fs/inode.c:265 
__destroy_inode+0x143/0x180
[Wed Nov 29 10:51:47 2023] Modules linked in: tcp_diag udp_diag inet_diag 
cls_cgroup sch_htb drbd_transport_tcp(OE) handshake(OE) drbd(OE) lru_cache 
bridge stp llc xt_owner xt_multiport xt_hl xt_tcpudp xt_state xt_conntrack 
xt_NFLOG ip6
table_raw iptable_raw ip6table_mangle iptable_mangle ip6table_nat iptable_nat 
nf_nat ip6table_filter ip6_tables iptable_filter bpfilter dell_rbu 
nfnetlink_log nfnetlink i40e dcdbas igb ipmi_ssif joydev input_leds mei_me mei 
ioatdma inte
l_pch_thermal dca acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler 
acpi_power_meter mac_hid sch_fq_codel xen_pciback xen_netback xen_blkback 
xen_gntalloc xen_gntdev xen_evtchn ramoops reed_solomon pstore_blk pstore_zone 
xenfs ip_tables x_
tables autofs4 raid10 raid0 multipath linear xen_privcmd zstd zstd_compress 
zram zfs(POE) zunicode(POE) zzstd(O) zlua(OE) zavl(POE) icp(POE) zcommon(POE) 
znvpair(POE) spl(OE) nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 aufs raid1 
dm_raid
 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
[Wed Nov 29 10:51:47 2023]  hid_generic usbhid hid raid6_pq libcrc32c ast 
i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core ahci i2c_i801 xhci_pci efi_pstore 
drm i2c
_smbus libahci xhci_pci_renesas wmi
[Wed Nov 29 10:51:47 2023] CPU: 2 PID: 3295469 Comm: nano Tainted: PW  
OE 5.15.0-91-generic #101~20.04.1zynstra1
[Wed Nov 29 10:51:47 2023] Hardware name: Supermicro 
SYS-5019D-FN8TP-5-NC041/X11SDV-4C-TP8F, BIOS 1.2 11/14/2019
[Wed Nov 29 10:51:47 2023] RIP: e030:__destroy_inode+0x143/0x180
[Wed Nov 29 10:51:47 2023] Code: 83 c7 08 e8 5f 3f da ff eb 93 be 08 00 00 00 
48 83 c7 08 e8 4f 3f da ff eb 92 0f 0b 0f 0b e9 25 ff ff ff 0f 0b e9 f0 fe ff 
ff <0f> 0b e9 55 ff ff ff 48 8b 90 60 02 00 00 f0 48 83 2a 01 0f 85 00
[Wed Nov 29 10:51:47 2023] RSP: e02b:c9004c4a3d80 EFLAGS: 00010246
[Wed Nov 29 10:51:47 2023] RAX: 88812d892000 RBX: 88816be64b18 RCX: 
4e01
[Wed Nov 29 10:51:47 2023] RDX:  RSI: 0001 RDI: 
88816be64b18
[Wed Nov 29 10:51:47 2023] RBP: c9004c4a3d88 R08: 0001 R09: 
0064
[Wed Nov 29 10:51:47 2023] R10: 8261d3de R11: 0003 R12: 
c031a340
[Wed Nov 29 10:51:47 2023] R13: 88816be64ba0 R14: 88816be64b18 R15: 
8881727c8180
[Wed Nov 29 10:51:47 2023] FS:  7fdee76d0040() 
GS:889046c8() knlGS:
[Wed Nov 29 10:51:47 2023] CS:  e030 DS:  ES:  CR0: 80050033
[Wed Nov 29 10:51:47 2023] CR2: 7fbce67eeff0 CR3: 000fc6a84000 CR4: 
00050660
[Wed Nov 29 10:51:47 2023] Call Trace:
[Wed Nov 29 10:51:47 2023]  
[Wed Nov 29 10:51:47 2023]  ? show_trace_log_lvl+0x1d6/0x2ea
[Wed Nov 29 10:51:47 2023]  ? show_trace_log_lvl+0x1d6/0x2ea
[Wed Nov 29 10:51:47 2023]  ? destroy_inode+0x2f/0x80
[Wed Nov 29 10:51:47 2023]  ? show_regs.part.0+0x23/0x29
[Wed Nov 29 10:51:47 2023]  ? show_regs.cold+0x8/0xd
[Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
[Wed Nov 29 10:51:47 2023]  ? __warn+0x8c/0x100
[Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
[Wed Nov 29 10:51:47 2023]  ? report_bug+0xa4/0xd0
[Wed Nov 29 10:51:47 2023]  ? handle_bug+0x39/0x90
[Wed Nov 29 10:51:47 2023]  ? exc_invalid_op+0x19/0x70
[Wed Nov 29 10:51:47 2023]  ? asm_exc_invalid_op+0x1b/0x20
[Wed Nov 29 10:51:47 2023]  ? __destroy_inode+0x143/0x180
[Wed Nov 29 10:51:47 2023]  destroy_inode+0x2f/0x80
[Wed Nov 29 10:51:47 2023]  evict+0x142/0x190
[Wed Nov 29 10:51:47 2023]  iput_final+0xa5/0x150
[Wed Nov 29 10:51:47 2023]  iput.part.0+0xa0/0xb0
[Wed Nov 29 10:51:47 2023]  iput+0x1c/0x30
[Wed Nov 29 10:51:47 2023]  do_unlinkat+0x1c7/0x2c0
[Wed Nov 29 10:51:47 2023]  __x64_sys_unlink+0x42/0x70
[Wed Nov 29 10:51:47 2023]  do_syscall_64+0x59/0xc0
[Wed Nov 29 10:51:47 2023]  ? ptrace_notify+0x68/0x80
[Wed Nov 29 10:51:47 2023]  ? exit_to_user_mode_prepare+0x96/0xb0
[Wed Nov 29 10:51:47 2023]  ? syscall_exit_to_user_mode+0x35/0x50
[Wed Nov 29 10:51:47 2023]  ? 

[Kernel-packages] [Bug 2045248] Re: focal: 5.15.0-91 crashes on boot as Xen PV guest

[James Dingwall]

Based on a response to xen-devel post I've cherry-picked these commits
to our 5.15 kernel build and since then we have not encountered this
problem.

6cf3e4c0d29102c74aca1ce0c1710be9d02e440e # x86/entry: Cleanup PARAVIRT
1462eb381b4c27576a3e818bc9f918765d327fdf # x86/xen: Rework the 
xen_{cpu,irq,mmu}_opsarrays
8b87d8cec1b31ea710568ae49ba5f5146318da0d # x86/entry,xen: Early rewrite of 
restore_regs_and_return_to_kernel()
bbf92368b0b1fe472d489e62d3340d7897e9c697 # x86/text-patching: Make 
text_gen_insn() play nice with ANNOTATE_NOENDBR
ba27d1a80871eb8dbeddf34ec7d396c149cbb8d7 # x86/ibt,paravirt: Use 
text_gen_insn() for paravirt_patch()

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

Title:
  focal: 5.15.0-91 crashes on boot as Xen PV guest

Status in linux-meta package in Ubuntu:
  New

Bug description:
  We have a custom build of the kernel based on the Ubuntu-
  hwe-5.15-5.15.0-91.101_20.04.1 tag.  It includes a small number of
  patches but nothing in the area of the early boot code.  Xen is based
  on the upstream 4.15.5 stable branch with all patches up to and
  including XSA-444.  In approximately 1% of pv guest boots we get the
  following crash which looks like it involves the entry_64.S code.  We
  have seen this on different hardware models but only with an Intel
  processor although we don't have any AMD based systems.  The problem
  was also observed with the 5.15.0-85 tag.

  I have had a look on the main line kernel branch for arch/x86/entry
  changes but I can't obviously connect this problem to anything there
  based on the commit messages.  I don't have the knowledge to
  understand the code though and whether there is actually something
  relevant.

  
  ```
  [0.303715] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user 
pointer sanitization
  [0.303727] Spectre V2 : Mitigation: Enhanced IBRS
  [0.303733] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB 
on context switch
  [0.303740] Spectre V2 : Spectre v2 / PBRSB-eIBRS: Retire a single CALL on 
VMEXIT
  [0.303746] RETBleed: Mitigation: Enhanced IBRS
  [0.303752] Spectre V2 : mitigation: Enabling conditional Indirect Branch 
Prediction Barrier
  [0.303760] Speculative Store Bypass: Mitigation: Speculative Store Bypass 
disabled via prctl and seccomp
  [0.303771] MMIO Stale Data: Mitigation: Clear CPU buffers
  [0.303777] GDS: Unknown: Dependent on hypervisor status
  [0.303827] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
  [0.303835] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
  [0.303840] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
  [0.303846] x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
  [0.303851] x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
  [0.303857] x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256'
  [0.303865] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
  [0.303871] x86/fpu: xstate_offset[5]: 1088, xstate_sizes[5]:   64
  [0.303877] x86/fpu: xstate_offset[6]: 1152, xstate_sizes[6]:  512
  [0.303882] x86/fpu: xstate_offset[7]: 1664, xstate_sizes[7]: 1024
  [0.303888] x86/fpu: Enabled xstate features 0xe7, context size is 2688 
bytes, using 'standard' format.
  [0.327588] segment-related general protection fault: e030 [#1] SMP NOPTI
  [0.327604] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-91-generic 
#101~20.04.1custom1
  [0.327614] RIP: e030:native_irq_return_iret+0x0/0x2
  [0.327627] Code: 5b 41 5b 41 5a 41 59 41 58 58 59 5a 5e 5f 48 83 c4 08 eb 
0f 0f 1f 00 90 66 66 2e 0f 1f 84 00 00 00 00 00 f6 44 24 20 04 75 02 <48> cf 57 
0f 01 f8 eb 12 0f 20 df 90 90 90 90 90 48 81 e7 ff e7 ff
  [0.327640] RSP: e02b:82e03bc8 EFLAGS: 00010046
  [0.327647] RAX:  RBX: 82e03c30 RCX: 
81e01101
  [0.327653] RDX:  RSI:  RDI: 
001f
  [0.327660] RBP: 82e03bf8 R08: 81e011ef R09: 
0005
  [0.327666] R10: 0006 R11: e8ae0feb75ccff49 R12: 
81e011ef
  [0.327672] R13: 0006 R14: 81e011f1 R15: 
0002
  [0.327684] FS:  () GS:888015a0() 
knlGS:
  [0.327691] CS:  1e030 DS:  ES:  CR0: 80050033
  [0.327696] CR2:  CR3: 02e1 CR4: 
00050660
  [0.327705] Call Trace:
  [0.327709]  
  [0.327713]  ? show_trace_log_lvl+0x1d6/0x2ea
  [0.327723]  ? show_trace_log_lvl+0x1d6/0x2ea
  [0.327729]  ? insn_decode+0xec/0x100
  [0.327738]  ? show_regs.part.0+0x23/0x29
  [0.327743]  ? __die_body.cold+0x8/0xd
  [0.327748]  ? die_addr+0x3e/0x60
  [0.327756]  ? exc_general_protection+0x1c1/0x350
  [

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

[james michaels]

proposed tracker"? Are you referring to a project tracker like
https://www.nationalgolfcartcovers.com/

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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

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

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

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

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


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

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

[james michaels]

one of the best inforamtion like the
https://www.nationalgolfcartcovers.com/

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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

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

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

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

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


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

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

[james anderson]

best information like the http://cryptopostage.info/

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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

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

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

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

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


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

[Kernel-packages] [Bug 2045248] [NEW] focal: 5.15.0-91 crashes on boot as Xen PV guest

[James Dingwall]

Public bug reported:

We have a custom build of the kernel based on the Ubuntu-
hwe-5.15-5.15.0-91.101_20.04.1 tag.  It includes a small number of
patches but nothing in the area of the early boot code.  Xen is based on
the upstream 4.15.5 stable branch with all patches up to and including
XSA-444.  In approximately 1% of pv guest boots we get the following
crash which looks like it involves the entry_64.S code.  We have seen
this on different hardware models but only with an Intel processor
although we don't have any AMD based systems.  The problem was also
observed with the 5.15.0-85 tag.

I have had a look on the main line kernel branch for arch/x86/entry
changes but I can't obviously connect this problem to anything there
based on the commit messages.  I don't have the knowledge to understand
the code though and whether there is actually something relevant.


```
[0.303715] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user 
pointer sanitization
[0.303727] Spectre V2 : Mitigation: Enhanced IBRS
[0.303733] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on 
context switch
[0.303740] Spectre V2 : Spectre v2 / PBRSB-eIBRS: Retire a single CALL on 
VMEXIT
[0.303746] RETBleed: Mitigation: Enhanced IBRS
[0.303752] Spectre V2 : mitigation: Enabling conditional Indirect Branch 
Prediction Barrier
[0.303760] Speculative Store Bypass: Mitigation: Speculative Store Bypass 
disabled via prctl and seccomp
[0.303771] MMIO Stale Data: Mitigation: Clear CPU buffers
[0.303777] GDS: Unknown: Dependent on hypervisor status
[0.303827] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.303835] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.303840] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.303846] x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
[0.303851] x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
[0.303857] x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256'
[0.303865] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.303871] x86/fpu: xstate_offset[5]: 1088, xstate_sizes[5]:   64
[0.303877] x86/fpu: xstate_offset[6]: 1152, xstate_sizes[6]:  512
[0.303882] x86/fpu: xstate_offset[7]: 1664, xstate_sizes[7]: 1024
[0.303888] x86/fpu: Enabled xstate features 0xe7, context size is 2688 
bytes, using 'standard' format.
[0.327588] segment-related general protection fault: e030 [#1] SMP NOPTI
[0.327604] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-91-generic 
#101~20.04.1custom1
[0.327614] RIP: e030:native_irq_return_iret+0x0/0x2
[0.327627] Code: 5b 41 5b 41 5a 41 59 41 58 58 59 5a 5e 5f 48 83 c4 08 eb 
0f 0f 1f 00 90 66 66 2e 0f 1f 84 00 00 00 00 00 f6 44 24 20 04 75 02 <48> cf 57 
0f 01 f8 eb 12 0f 20 df 90 90 90 90 90 48 81 e7 ff e7 ff
[0.327640] RSP: e02b:82e03bc8 EFLAGS: 00010046
[0.327647] RAX:  RBX: 82e03c30 RCX: 81e01101
[0.327653] RDX:  RSI:  RDI: 001f
[0.327660] RBP: 82e03bf8 R08: 81e011ef R09: 0005
[0.327666] R10: 0006 R11: e8ae0feb75ccff49 R12: 81e011ef
[0.327672] R13: 0006 R14: 81e011f1 R15: 0002
[0.327684] FS:  () GS:888015a0() 
knlGS:
[0.327691] CS:  1e030 DS:  ES:  CR0: 80050033
[0.327696] CR2:  CR3: 02e1 CR4: 00050660
[0.327705] Call Trace:
[0.327709]  
[0.327713]  ? show_trace_log_lvl+0x1d6/0x2ea
[0.327723]  ? show_trace_log_lvl+0x1d6/0x2ea
[0.327729]  ? insn_decode+0xec/0x100
[0.327738]  ? show_regs.part.0+0x23/0x29
[0.327743]  ? __die_body.cold+0x8/0xd
[0.327748]  ? die_addr+0x3e/0x60
[0.327756]  ? exc_general_protection+0x1c1/0x350
[0.327766]  ? asm_exc_general_protection+0x27/0x30
[0.327772]  ? restore_regs_and_return_to_kernel+0x1d/0x2c
[0.327778]  ? restore_regs_and_return_to_kernel+0x1b/0x2c
[0.327784]  ? restore_regs_and_return_to_kernel+0x1b/0x2c
[0.327789]  ? asm_sysvec_xen_hvm_callback+0x11/0x20
[0.327796]  ? native_iret+0x7/0x7
[0.327801]  ? insn_get_displacement+0x4d/0x110
[0.327807]  insn_decode+0xec/0x100
[0.327813]  optimize_nops+0x68/0x150
[0.327819]  ? restore_regs_and_return_to_kernel+0x1d/0x2c
[0.327825]  ? restore_regs_and_return_to_kernel+0x2c/0x2c
[0.327830]  ? restore_regs_and_return_to_kernel+0x20/0x2c
[0.327837]  apply_alternatives+0x181/0x3a0
[0.327843]  ? restore_regs_and_return_to_kernel+0x1b/0x2c
[0.327848]  ? fb_is_primary_device+0x25/0x73
[0.327855]  ? restore_regs_and_return_to_kernel+0x1b/0x2c
[0.327861]  ? apply_alternatives+0x8/0x3a0
[0.327867]  ? fb_is_primary_device+0x6e/0x73
[0.327872]  ? apply_returns+0xfc/0x180
[0.327878]  ? 

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

[james michael]

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

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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

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

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

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

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


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

[Kernel-packages] [Bug 2041853] Re: screen goes blank, audio cuts out with kernel 6.2 (but 5.15 works)

[James Atack]

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

Think this is actually a duplicate of 2009952.

I haven't tested 6.x with the kernel parameter suggested, but everything
else described matches. So nothing to do with gnome-shell.

https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2009952

** This bug has been marked a duplicate of bug 2009952
   [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

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

Title:
  screen goes blank, audio cuts out with kernel 6.2 (but 5.15 works)

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

Bug description:
  I'm tracking down the multiple causes of screen flashes and audio 
interruption on my ubuntu 22.04 laptop. 
  Issue open with Lenovo : 
https://forums.lenovo.com/t5/Ubuntu/ThinkPad-T14s-Gen-3-AMD-Ryzen-Screen-flickers-randomly-and-becomes-black-for-4-5-seconds/m-p/525298

  
  This bug is one of the causes (log reversed : journalctl -r)

  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: 
_st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation 
(actor)' failed
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac8bfbc10] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acd416dc0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac996b860] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878ac50] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acb009cc0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878a610] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac9f6a480] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acd404df0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac878a2f0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acb16d9a0] is on because it 
needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca446320] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558acdf86f70] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac996a4e0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558aca9a6fd0] is on because it needs an allocation.
  oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor 
[:0x558ac9e94de0] 

[Kernel-packages] [Bug 2033327] Re: Desktop cannot resume after suspend: screen not detected

[James Phillips]

Kern.log with similar suspend messages. I was looking at the logs
because my game of Euro Truck simulator 2 appeared to crash: but in
hindsight it was probably just the video driver that crashed. Steam was
still running right up until reboot. The game log was truncated by 4
minutes: despite logging into a terminal and typing 'sync' before
"sysctl reboot -i". The video crash happens at

When the video driver crashes I was unable to use the desktop
environment: but the display manager seems to work.

$ uname -a
Linux cathy 5.15.0-87-generic #97-Ubuntu SMP Mon Oct 2 21:09:21 UTC 2023 x86_64 
x86_64 x86_64 GNU/Linux

I am using the AMD Rocm 5.6 video drivers. (The last ones supporting my
Vega 56 card, apparently).

The actual video crash happens in this part of the log:
Oct 20 10:47:59 cathy kernel: [67779.641047] amdgpu :06:00.0: amdgpu: IH 
ring buffer overflow (0x00080C60, 0x02C0, 0x0C80)
Oct 20 10:47:59 cathy kernel: [67779.753369] [drm] ring 0 timeout to preempt ib
Oct 20 10:48:09 cathy kernel: [67789.894431] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* ring gfx_high timeout, signaled seq=1282275, emitted seq
=1282276
Oct 20 10:48:09 cathy kernel: [67789.895531] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* Process information: process gnome-shell pid 1994 thread
 gnome-shel:cs0 pid 2002


** Attachment added: "Oct_20_crash.kern.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+attachment/5711902/+files/Oct_20_crash.kern.log.gz

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

Title:
  Desktop cannot resume after suspend: screen not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware:

  - Desktop PC (Intel i5 4th gen)
  - GPU: AMD RX580
  - Ubuntu 22.04 with kernel HWE 6.2

  Steps to reproduce:

  1. Start the device
  2. Suspend
  3. Resume by pressing a key on the keyboard

  Expected results:

  The screen lights up, showing the screen to put my password to resume
  the session.

  Actual result:

  The screen OSD displays a "No Signal" message before turning off.
  Nothing seems to happen when I press keyboard keys or move the mouse.

  Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see
  the logs (that's how I filed this bug).

  Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows
  the cursor and nothing else (black screen).

  Switching to login screen (Ctrl+Alt+F1) works: I can see the list of
  users, select on and enter my password... but then I'm back to the
  same black screen with the mouse cursor.

  This is not a regression, as the same problem happened already with
  the previous point release (I believe it was Linux kernel 5.15).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Aug 29 09:15:49 2023
  InstallationDate: Installed on 2022-12-28 (243 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  pieq   2262 F pulseaudio
   /dev/snd/controlC1:  pieq   2262 F pulseaudio
   /dev/snd/controlC0:  pieq   2262 F pulseaudio
   /dev/snd/controlC2:  pieq   2262 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-28 (245 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-26-generic N/A
   linux-backports-modules-6.2.0-26-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.17
  RfKill:
   
  StagingDrivers: r8188eu
  Tags:  jammy staging
  Uname: Linux 6.2.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/26/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American 

[Kernel-packages] [Bug 2033327] Re: Desktop cannot resume after suspend: screen not detected

[James Phillips]

Message #26

[code]Aug 29 09:12:32 coltrane kernel: sd 2:0:0:0: [sdb] Stopping disk
Aug 29 09:12:32 coltrane kernel: sd 4:0:0:0: [sdd] Stopping disk
Aug 29 09:12:32 coltrane kernel: sd 3:0:0:0: [sdc] Stopping disk
(...)
Aug 29 09:12:32 coltrane kernel: kworker/u8:24: page allocation failure: 
order:5, mode:0x40d00(GFP_NOIO|__GFP_COMP|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
[/code]

Confirms that it is probably upstream bug #2362
https://gitlab.freedesktop.org/drm/amd/-/issues/2362

The issue is that the GPU driver tries to dump the contents of VRAM to
system RAM upon suspend. However, this is not able to happen because the
disks (with swap) are suspended first. It appears that the solution is
likely to dump the VRAM contents during the "pre-suspend" hook.
Incidentally the bug appear to date back to at least 2010: but VRAM was
a lot smaller compared to system RAM back then.

I got the same errors: but was able to resume from suspend for some
reason. I *suspect* it is because I am using the Rocm GPU drivers.

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2362
   https://gitlab.freedesktop.org/drm/amd/-/issues/2362

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

Title:
  Desktop cannot resume after suspend: screen not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware:

  - Desktop PC (Intel i5 4th gen)
  - GPU: AMD RX580
  - Ubuntu 22.04 with kernel HWE 6.2

  Steps to reproduce:

  1. Start the device
  2. Suspend
  3. Resume by pressing a key on the keyboard

  Expected results:

  The screen lights up, showing the screen to put my password to resume
  the session.

  Actual result:

  The screen OSD displays a "No Signal" message before turning off.
  Nothing seems to happen when I press keyboard keys or move the mouse.

  Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see
  the logs (that's how I filed this bug).

  Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows
  the cursor and nothing else (black screen).

  Switching to login screen (Ctrl+Alt+F1) works: I can see the list of
  users, select on and enter my password... but then I'm back to the
  same black screen with the mouse cursor.

  This is not a regression, as the same problem happened already with
  the previous point release (I believe it was Linux kernel 5.15).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Aug 29 09:15:49 2023
  InstallationDate: Installed on 2022-12-28 (243 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  pieq   2262 F pulseaudio
   /dev/snd/controlC1:  pieq   2262 F pulseaudio
   /dev/snd/controlC0:  pieq   2262 F pulseaudio
   /dev/snd/controlC2:  pieq   2262 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-28 (245 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-26-generic N/A
   linux-backports-modules-6.2.0-26-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.17
  RfKill:
   
  StagingDrivers: r8188eu
  Tags:  jammy staging
  Uname: Linux 6.2.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/26/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  

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

[james michael]

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

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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

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

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

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

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


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

[Kernel-packages] [Bug 2033316] Re: UBUNTU: [Config] optee: Adjust CONFIG_OPTEE_SHM_NUM_PRIV_PAGES to 4

[James Hurley]

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

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

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

Title:
  UBUNTU: [Config] optee: Adjust CONFIG_OPTEE_SHM_NUM_PRIV_PAGES to 4

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

Bug description:
  SRU Justification:

  [Impact]
  This change is needed to OPTEE as the FTPM driver requires 2 contiguous SHMEM 
pages to boot. Without this change the ftpm_tee_probe function will fail.

  [Fix]
  Change the CONFIG_OPTEE_SHM_NUM_PRIV_PAGES from 1 to 4. Note that other SHMEM 
structures are allocated out of this OPTEE pool as well.

  [Test Case]
  Verified the Microsoft TPM 2.0 FTPM is fully functional with this change, 
running the tpm2-tss Test Suite (mandatory & optional) tests  as well as many 
of the TPM2 Command tools.

  [Regression Potential]
  This only has an effect if OPTEE is configured/enabled in the kernel.

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


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

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

[james michal]

one of the best information i have resolved the issue like
https://haktutscoinmaster.com/

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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

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

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

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

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


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

[Kernel-packages] [Bug 2037012] [NEW] package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1

[James Bonilla]

Public bug reported:

no se está ejecutando el sevico Bluez

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3.6
ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116
Uname: Linux 5.15.0-84-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.26
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Sep 21 13:30:47 2023
ErrorMessage: el subproceso instalado paquete bluez script post-installation 
devolvió el código de salida de error 1
InstallationDate: Installed on 2023-09-18 (2 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
InterestingModules: bluetooth
MachineType: Hewlett-Packard HP Pavilion dv4 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic 
root=UUID=e02ac370-977e-4bed-840d-5a24e2e5b288 ro quiet splash vt.handoff=7
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: bluez
Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso 
instalado paquete bluez script post-installation devolvió el código de salida 
de error 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.22
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 30F7
dmi.board.vendor: Compal
dmi.board.version: 99.80
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.22:bd10/17/2008:svnHewlett-Packard:pnHPPaviliondv4NotebookPC:pvrF.22:rvnCompal:rn30F7:rvr99.80:cvnCompal:ct10:cvrN/A:skuFR922UA#ABA:
dmi.product.family: 103C_5335KV
dmi.product.name: HP Pavilion dv4 Notebook PC
dmi.product.sku: FR922UA#ABA
dmi.product.version: F.22
dmi.sys.vendor: Hewlett-Packard
hciconfig:

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


** Tags: amd64 apport-package focal

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

Title:
  package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso
  instalado paquete bluez script post-installation devolvió el código de
  salida de error 1

Status in bluez package in Ubuntu:
  New

Bug description:
  no se está ejecutando el sevico Bluez

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116
  Uname: Linux 5.15.0-84-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Sep 21 13:30:47 2023
  ErrorMessage: el subproceso instalado paquete bluez script post-installation 
devolvió el código de salida de error 1
  InstallationDate: Installed on 2023-09-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  InterestingModules: bluetooth
  MachineType: Hewlett-Packard HP Pavilion dv4 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic 
root=UUID=e02ac370-977e-4bed-840d-5a24e2e5b288 ro quiet splash vt.handoff=7
  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: bluez
  Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso 
instalado paquete bluez script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F7
  dmi.board.vendor: Compal
  dmi.board.version: 99.80
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.22:bd10/17/2008:svnHewlett-Packard:pnHPPaviliondv4NotebookPC:pvrF.22:rvnCompal:rn30F7:rvr99.80:cvnCompal:ct10:cvrN/A:skuFR922UA#ABA:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv4 Notebook PC
  dmi.product.sku: FR922UA#ABA
  dmi.product.version: F.22
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:

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


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

Re: [Kernel-packages] [Bug 2033148] Re: New 6.2.0 kernel error

[James Pollack]

Yes I can confirm the error has been fixed. Thank you.

Sent from Yahoo Mail on Android 
 
  On Sat, 16 Sept 2023 at 4:12, Daniel Jarai<2033...@bugs.launchpad.net> wrote: 
  This seems to be fixed in 6.2.0-32 on Ubuntu 22.04: 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/log/lib?h=Ubuntu-hwe-6.2-6.2.0-32.32_22.04.1
Can you confirm?

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

Title:
  New 6.2.0 kernel error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  You may already be aware of this error but if not I have been trying
  to build lineage-20 recently and it kept failing. After trying a
  number of potential solutions from the web the one that worked advised
  the in ubuntu 22.04.3 kernel version 6.x.x somehow is incompatible for
  the build causing a mmap error while building ART.

  I followed their advice and reverted to a previous kernel. I selected
  5.19.0-46 kernel and the build worked fine.

  See the last post in the following web site for the solution I followed.
  
https://stackoverflow.com/questions/60275623/android-dex2oat-builderror-dex2oat-failed-to-compile-a-boot-image

  Regards, James.

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

Title:
  New 6.2.0 kernel error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  You may already be aware of this error but if not I have been trying
  to build lineage-20 recently and it kept failing. After trying a
  number of potential solutions from the web the one that worked advised
  the in ubuntu 22.04.3 kernel version 6.x.x somehow is incompatible for
  the build causing a mmap error while building ART.

  I followed their advice and reverted to a previous kernel. I selected
  5.19.0-46 kernel and the build worked fine.

  See the last post in the following web site for the solution I followed.
  
https://stackoverflow.com/questions/60275623/android-dex2oat-builderror-dex2oat-failed-to-compile-a-boot-image

  Regards, James.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033148/+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 2033316] Re: UBUNTU: [Config] optee: Adjust CONFIG_OPTEE_SHM_NUM_PRIV_PAGES to 4

[James Hurley]

** Summary changed:

- Kernel cfg: OPTEE driver increase SHMEM pages
+ UBUNTU: [Config] optee: Adjust CONFIG_OPTEE_SHM_NUM_PRIV_PAGES to 4

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

Title:
  UBUNTU: [Config] optee: Adjust CONFIG_OPTEE_SHM_NUM_PRIV_PAGES to 4

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]
  This change is needed to OPTEE as the FTPM driver requires 2 contiguous SHMEM 
pages to boot. Without this change the ftpm_tee_probe function will fail.

  [Fix]
  Change the CONFIG_OPTEE_SHM_NUM_PRIV_PAGES from 1 to 4. Note that other SHMEM 
structures are allocated out of this OPTEE pool as well.

  [Test Case]
  Verified the Microsoft TPM 2.0 FTPM is fully functional with this change, 
running the tpm2-tss Test Suite (mandatory & optional) tests  as well as many 
of the TPM2 Command tools.

  [Regression Potential]
  This only has an effect if OPTEE is configured/enabled in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033316/+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 2033316] Re: Kernel cfg: OPTEE driver increase SHMEM pages

[James Hurley]

** Description changed:

  SRU Justification:
  
  [Impact]
  This change is needed to OPTEE as the FTPM driver requires 2 contiguous SHMEM 
pages to boot. Without this change the ftpm_tee_probe function will fail.
  
- [Fix] 
+ [Fix]
  Change the CONFIG_OPTEE_SHM_NUM_PRIV_PAGES from 1 to 4. Note that other SHMEM 
structures are allocated out of this OPTEE pool as well.
  
  [Test Case]
- Verified the Microsoft TPM 2.0 FTPM is fully functional with this change, 
running the tpm2-tss Test Suite (mandatory & optional)b tests  as well as many 
of the TPM2 Command tools.
+ Verified the Microsoft TPM 2.0 FTPM is fully functional with this change, 
running the tpm2-tss Test Suite (mandatory & optional) tests  as well as many 
of the TPM2 Command tools.
  
  [Regression Potential]
  This only has an effect if OPTEE is configured/enabled in the kernel.

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

Title:
  Kernel cfg: OPTEE driver increase SHMEM pages

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]
  This change is needed to OPTEE as the FTPM driver requires 2 contiguous SHMEM 
pages to boot. Without this change the ftpm_tee_probe function will fail.

  [Fix]
  Change the CONFIG_OPTEE_SHM_NUM_PRIV_PAGES from 1 to 4. Note that other SHMEM 
structures are allocated out of this OPTEE pool as well.

  [Test Case]
  Verified the Microsoft TPM 2.0 FTPM is fully functional with this change, 
running the tpm2-tss Test Suite (mandatory & optional) tests  as well as many 
of the TPM2 Command tools.

  [Regression Potential]
  This only has an effect if OPTEE is configured/enabled in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033316/+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 2033316] [NEW] Kernel cfg: OPTEE driver increase SHMEM pages

[James Hurley]

Public bug reported:

SRU Justification:

[Impact]
This change is needed to OPTEE as the FTPM driver requires 2 contiguous SHMEM 
pages to boot. Without this change the ftpm_tee_probe function will fail.

[Fix] 
Change the CONFIG_OPTEE_SHM_NUM_PRIV_PAGES from 1 to 4. Note that other SHMEM 
structures are allocated out of this OPTEE pool as well.

[Test Case]
Verified the Microsoft TPM 2.0 FTPM is fully functional with this change, 
running the tpm2-tss Test Suite (mandatory & optional)b tests  as well as many 
of the TPM2 Command tools.

[Regression Potential]
This only has an effect if OPTEE is configured/enabled in the kernel.

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

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

Title:
  Kernel cfg: OPTEE driver increase SHMEM pages

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]
  This change is needed to OPTEE as the FTPM driver requires 2 contiguous SHMEM 
pages to boot. Without this change the ftpm_tee_probe function will fail.

  [Fix] 
  Change the CONFIG_OPTEE_SHM_NUM_PRIV_PAGES from 1 to 4. Note that other SHMEM 
structures are allocated out of this OPTEE pool as well.

  [Test Case]
  Verified the Microsoft TPM 2.0 FTPM is fully functional with this change, 
running the tpm2-tss Test Suite (mandatory & optional)b tests  as well as many 
of the TPM2 Command tools.

  [Regression Potential]
  This only has an effect if OPTEE is configured/enabled in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033316/+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 2028274] [NEW] watchdog: BUG: soft lockup - CPU#10 stuck for 134s! [DyingLightGame_:4256]

[James Fox]

Public bug reported:

Playing Dying Light 2 through steam/proton on Ubuntu 22.04 with nvidia
535.

Game is perfect until I press quit in Dying Light 2's menu. The computer
totally locks up and I have to hold the power button down. It happens
every time.

Downgrading to 525 with 'sudo apt install nvidia-driver-525 nvidia-
dkms-525' fixed the issue.

 journalctl 
Jul 20 10:56:28 desktop kernel: watchdog: BUG: soft lockup - CPU#10 stuck for 
134s! [DyingLightGame_:4256]
Jul 20 10:56:28 desktop kernel: Modules linked in: vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) binfmt_misc nls_iso8859_1 snd_sof_pci_intel_tgl 
snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi 
soundwire_bus snd_soc_core snd_usb_audio snd_hda_codec_realtek intel_rapl_msr 
snd_compress intel_rapl_common snd_hda_codec_generic ac97_bus ledtrig_audio 
snd_pcm_dmaengine snd_hda_codec_hdmi snd_usbmidi_lib x86_pkg_temp_thermal 
intel_powerclamp snd_rawmidi snd_seq_device coretemp mc snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi kvm_intel snd_hda_codec snd_hda_core xpad 
mei_hdcp snd_hwdep snd_pcm ff_memless joydev snd_timer kvm snd mei_me soundcore 
mei ee1004 intel_cstate intel_wmi_thunderbolt gigabyte_wmi wmi_bmof 
nvidia_uvm(POE) mac_hid acpi_pad acpi_tad sch_fq_codel msr pstore_blk ramoops 
pstore_zone reed_solomon efi_pstore ip
 _tables x_tables
Jul 20 10:56:28 desktop kernel:  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 nvidia_drm(POE) 
nvidia_modeset(POE) hid_generic usbhid hid nvidia(POE) crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel drm_kms_helper syscopyarea sysfillrect 
sysimgblt fb_sys_fops cec aesni_intel rc_core crypto_simd cryptd drm r8169 ahci 
i2c_i801 xhci_pci i2c_smbus realtek libahci xhci_pci_renesas wmi video 
pinctrl_tigerlake
Jul 20 10:56:28 desktop kernel: CPU: 10 PID: 4256 Comm: DyingLightGame_ 
Tainted: P   OEL5.15.0-76-generic #83-Ubuntu
Jul 20 10:56:28 desktop kernel: Hardware name: Gigabyte Technology Co., Ltd. 
H510M S2H/H510M S2H, BIOS F9 08/23/2021
Jul 20 10:56:28 desktop kernel: RIP: 0010:_nv039537rm+0x3b/0x80 [nvidia]
Jul 20 10:56:28 desktop kernel: Code: d3 89 de 48 8d 55 0f c6 45 0f 00 e8 3f 4c 
60 ff 80 7d 0f 00 41 89 c4 75 11 41 39 5d 10 76 20 49 8b 45 00 c1 eb 02 44 8b 
24 98 <5b> 44 89 e0 41 5c 41 5d 48 83 c5 10 c3 0f 1f 84 00 00 00 00 00 be
Jul 20 10:56:28 desktop kernel: RSP: 0018:bd0d839bf8f0 EFLAGS: 0202
Jul 20 10:56:28 desktop kernel: RAX: bd0d8200 RBX: 2440 
RCX: 9100
Jul 20 10:56:28 desktop kernel: RDX: 952e995e596f RSI: 9100 
RDI: 952de38c0008
Jul 20 10:56:28 desktop kernel: RBP: 952e995e5960 R08: 0020 
R09: 
Jul 20 10:56:28 desktop kernel: R10: 9100 R11: 952e995e59c8 
R12: 0001
Jul 20 10:56:28 desktop kernel: R13: 952de38c0bc8 R14:  
R15: 
Jul 20 10:56:28 desktop kernel: FS:  7fe4617b4040() 
GS:95355fc8() knlGS:7fee
Jul 20 10:56:28 desktop kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Jul 20 10:56:28 desktop kernel: CR2: 7f130400c000 CR3: 0001fca94005 
CR4: 00770ee0
Jul 20 10:56:28 desktop kernel: PKRU: 5554
Jul 20 10:56:28 desktop kernel: Call Trace:
Jul 20 10:56:28 desktop kernel:  
Jul 20 10:56:28 desktop kernel:  ? _nv013076rm+0x10f/0x170 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv047477rm+0x20/0x30 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv030454rm+0x5a/0x110 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv030546rm+0x13f/0x340 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv030547rm+0x50/0x60 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv013174rm+0x86/0xc0 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv013170rm+0x3a4/0x400 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv044237rm+0xd1/0x1b0 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv041109rm+0x1e7/0x370 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv048377rm+0x40/0x95 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv035020rm+0x14d/0x2e0 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv048374rm+0xc5/0x460 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv002711rm+0xd/0x20 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv004074rm+0x19/0xb0 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv016053rm+0x51c/0x620 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv043216rm+0xab/0xe0 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv044933rm+0xac/0x130 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv044932rm+0x3e5/0x690 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv043119rm+0xd5/0x160 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv043120rm+0x41/0x70 [nvidia]
Jul 20 10:56:28 desktop kernel:  ? _nv000566rm+0x4d/0x60 [nvidia]

[Kernel-packages] [Bug 2020757] Re: Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04)

[James Byrne]

Same issue for me using VMWare Player 17 with 5.19.0-42 and 5.19.0-43.
Have rolled back to 5.19.0-41.

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

Title:
  Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic
  (HWE kernel on 22.04)

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

Bug description:
  I use Ubuntu 22.04 in VMWare Player 17.0.2 (Windows host, due to
  corporate IT...). I installed the HWE kernel since I have an Intel CPU
  with P/E-cores. 3D acceleration is enabled in VMWare.

  With linux-image-5.19.0-41-generic it is rock solid. With linux-
  image-5.19.0-42-generic it invariably crashes after anything between a
  minute and an hour.

  In the journalctl after rebooting it showed that X.Org had crashed
  followed by a Kernel BUG/Oops due to NULL pointer dereference in
  drm_gem_object_release_handle. A journalctl log from the Xorg crash up
  until the kernel OOPS has been attached to this case.

  This issue happened twice with this kernel. In addition, after trying
  to reproduce it with kdump tools installed, I got a different issue:
  refcount_t: saturated; leaking memory. in the log, leading to the OOM
  killing everything on the system, including (based on what was printed
  on the terminal), systemd-udevd and journald. That OOM killing never
  made it into the journal however, as can be expected. I have attached
  what I could get from the journal for this case as well.

  One thing that helped trigger this bug (but not every time) was
  launching Firefox, but once it didn't crash from that and only crashed
  much much later.

  Unfortunately I could not get ubuntu-bug to work for this case. I
  tried "ubuntu-bug --package linux-image-5.19.0-42-generic" but it did
  absolutely nothing. I'm happy to provide any additional information
  you require however.

  $ lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
  $ apt-cache policy linux-generic-hwe-22.04   
  linux-generic-hwe-22.04:
Installed: 5.19.0.42.43~22.04.15
Candidate: 5.19.0.42.43~22.04.15
Version table:
   *** 5.19.0.42.43~22.04.15 500
  500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  $ apt-cache policy linux-image-5.19.0-42-generic
  linux-image-5.19.0-42-generic:
    Installed: 5.19.0-42.43~22.04.1
    Candidate: 5.19.0-42.43~22.04.1
    Version table:
   *** 5.19.0-42.43~22.04.1 500
  500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  What I expected to happen: No crash.
  What happened instead: The crash in the attached log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2020757/+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 2001567] Re: Add support for newer I219-LM NICs to the 5.4.0 kernel

[James Kenis]

I have this issue as well when using the FIPS 5.4.0 kernel with 3 Dell
models. Precision 7770, Precision 7670, and Precision 3571 all with the
I219-LM NIC. I was able to get the source from Intel's website and
figured out how to make the e1000e driver, but it does not work well on
all the models. The Precision 3571 has a download speed that bounces
from 800kb/s to 10 b/s, which is unusable, but it works well on the
other models. Unfortunately when you track down the drives the site
states that all future drivers will be kernel based and not released
otherwise.

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

Title:
  Add support for newer I219-LM NICs to the 5.4.0 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Some newer Dell systems (I experienced this on an Optiplex 7000)
  include an Intel I219-LM NIC that is not supported by the 5.4.0
  kernel. Later versions of the HWE kernel do support this NIC.

  That makes it impossible to use these systems with the FIPS kernel.
  Since our imaging environment does not have FIPS mode enabled, we need
  support for this NIC when used both with and without FIPS mode.

  Please backport the latest stable e1000e driver to both the 5.4.0 non-
  FIPS kernel & the 5.4.0 FIPS kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001567/+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 1535840] Re: systemd ignoring /etc/modules due to blacklist

[James Cuzella]

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

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

Title:
  systemd ignoring /etc/modules due to blacklist

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Opinion

Bug description:
  I tried the daily build of 16.04 32-bit to test out the watchdog
  daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in
  /etc/modules so it is loaded at boot-time, as watchdog timer modules
  are not normally auto-loaded due to the risk of an unexpected reboot.

  However I now find that systemd is choosing to ignore my command to
  load the module in /etc/modules since it appears in the watchdog
  blacklist. Typical syslog entries look like this:

  Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is 
blacklisted
  Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is 
blacklisted

  This is just dumb! I have explicitly told the system to load the
  module, an action that works perfectly well using modprobe or by
  adding it to the start script for the watchdog, and yet systemd
  chooses to override that because of the blacklist for auto-loaded
  modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf).

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy systemd
  systemd:
Installed: 228-4ubuntu1
Candidate: 228-4ubuntu1
Version table:
   *** 228-4ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  What I expect to happen is modules added to /etc/modules are loaded at
  boot time, and not subject to the blacklist for hardware detect /
  automatic loading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535840/+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 1896604] Re: Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal instances

[James Falcon]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3789

** Bug watch added: github.com/canonical/cloud-init/issues #3789
   https://github.com/canonical/cloud-init/issues/3789

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

Title:
  Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal
  instances

Status in cloud-images:
  Fix Released
Status in cloud-init:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  Starting with kernel 5.8 the default nr_uarts has been changed from 4
  to 2 for amd64, but this seems to affect i3.metal instances in AWS,
  because ttyS0 is now remapped to ttyS4 and this is breaking tools like
  cloud-init (and probably something else).

  [Test case]

  # echo > /dev/console
  bash: echo: write error: Input/output error

  [Fix]

  Setting nr_uarts=4 by default (via CONFIG_SERIAL_8250_RUNTIME_UARTS)
  restores the previous behavior and writing to /dev/console works
  without returning any error.

  [Regression potential]

  Minimal. Restores the old behavior used in 5.4 (that shouldn't have
  changed in the first place).

  [Original bug report]

  Hi,

  When running Groovy daily images on i3.metal instances a broken
  /dev/console is created. The char device appears to be writable but
  writing to it causes an Input/output error. This is breaking cloud-
  init, as it tries to log to /dev/console, and is likely to break other
  programs.

  On Focal:

  root@ip-172-31-24-163:~# ls -l /dev/console
  crw--- 1 root root 5, 1 Sep 21 16:07 /dev/console
  root@ip-172-31-24-163:~# echo x > /dev/console
  root@ip-172-31-24-163:~#

  On Groovy:

  root@ip-172-31-20-184:~# ls -l /dev/console
  crw--w 1 root tty 5, 1 Sep 21 16:03 /dev/console
  root@ip-172-31-20-184:~# echo x > /dev/console
  bash: echo: write error: Input/output error

  The Groovy kernel log has a

  [ 3.561696] fbcon: Taking over console

  line in it, which is not present in the Focal kernel log
  (5.4.0-1024-aws). Perhaps fbcon should be prevented from taking over
  console?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1896604/+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 1858615] Re: dmidecode triggers system reboot on Inforce 6640

[James Falcon]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3525

** Bug watch added: github.com/canonical/cloud-init/issues #3525
   https://github.com/canonical/cloud-init/issues/3525

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

Title:
  dmidecode triggers system reboot on Inforce 6640

Status in cloud-init:
  Invalid
Status in dmidecode package in Ubuntu:
  Fix Released
Status in dmidecode source package in Xenial:
  Fix Released
Status in dmidecode source package in Bionic:
  Fix Released
Status in dmidecode source package in Eoan:
  Fix Released
Status in dmidecode source package in Focal:
  Fix Released
Status in dmidecode package in Debian:
  Fix Released

Bug description:
  [Impact]
  Running 'sudo dmidecode' on non-UEFI ARM systems can cause them to 
crash/reboot. cloud-init apparently runs dmidecode as root, so it breaks any 
cloud-init based installation.

  [Test Case]
  sudo dmidecode

  [Fix]
  Upstream has the following fix:

  commit e12ec26e19e02281d3e7258c3aabb88a5cf5ec1d
  Author: Jean Delvare 
  Date: Mon Aug 26 14:20:15 2019 +0200

  dmidecode: Only scan /dev/mem for entry point on x86

  [Regression Risk]
  In Ubuntu, dmidecode only builds on amd64, arm64, armhf & i386.
  The fix is to disable code on !x86, so the regression risk is restricted to 
ARM platforms, where we know /dev/mem trolling is bad news.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1858615/+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 1803173] Re: cloud-init disables user on azure at second reboot

[James Falcon]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3279

** Bug watch added: github.com/canonical/cloud-init/issues #3279
   https://github.com/canonical/cloud-init/issues/3279

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

Title:
  cloud-init disables user on azure at second reboot

Status in cloud-init:
  Invalid
Status in linux package in Ubuntu:
  Triaged
Status in walinuxagent package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Environment:

  platform: Azure
  arm image: Canonical UbuntuServer 16.04-DAILY-LTS latest

  Steps:

  Deploy VM with user/pass authentication
  Install latest linux-next-upstream kernel (for example 4.19.0-4db9d11bcbef, 
where 4db9d11bcbef is the git tag from the linux-next latest tree: 
https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next/)
  reboot (all good)
  reboot again
  cloud-init disables the username password authentication
  I checked the cloud-init logs and found:

  2018-11-01 16:45:28,566 - init.py[INFO]: User already exists, skipping.
  2018-11-01 16:45:28,570 - util.py[DEBUG]: Running command ['passwd', '-l', 
''] with allowed return codes [0] (shell=False, capture=True)
  2018-11-01 16:45:28,793 - util.py[DEBUG]: Reading from /etc/sudoers 
(quiet=False)
  2018-11-01 16:45:28,795 - util.py[DEBUG]: Read 781 bytes from /etc/sudoers
  2018-11-01 16:45:28,796 - util.py[DEBUG]: Writing to 
/etc/sudoers.d/90-cloud-init-users - ab: [None] 51 bytes
  2018-11-01 16:45:28,797 - handlers.py[DEBUG]: finish: 
init-network/config-users-groups: SUCCESS: config-users-groups ran successfully

  This issue is very bad one, as it can render your vm inaccessible on Azure.
  I think this problem is due to the new kernel installation.

  Initial bug report:
  https://github.com/Azure/WALinuxAgent/issues/1386

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1803173/+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 1778891] Re: KVM Instance booting from volume stacktraces

[James Falcon]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3199

** Bug watch added: github.com/canonical/cloud-init/issues #3199
   https://github.com/canonical/cloud-init/issues/3199

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

Title:
  KVM Instance booting from volume stacktraces

Status in cloud-init:
  Invalid
Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Expired

Bug description:
  I've booted two instances from the same backing image (http://cloud-
  images.ubuntu.com/trusty/current/trusty-server-cloudimg-
  amd64-disk1.img), one using locally attached storage for the boot
  volume, one using a Cinder volume. The instance booted from cinder
  volume  shows a cloud-init trace in the console log, while the local
  instance works correctly.

  Instance booted from volume:

  Cloud-init v. 0.7.5 running 'init' at Wed, 27 Jun 2018 09:43:10 +. Up 
15.61 seconds.
  ci-info: ++Net device info+++
  ci-info: ++--+--+---+---+
  ci-info: | Device |  Up  |   Address|  Mask | Hw-Address|
  ci-info: ++--+--+---+---+
  ci-info: |   lo   | True |  127.0.0.1   |   255.0.0.0   | . |
  ci-info: |  eth0  | True | 192.168.21.8 | 255.255.255.0 | fa:16:3e:aa:c3:54 |
  ci-info: ++--+--+---+---+
  ci-info: +++Route 
info+++
  ci-info: 
+---+-+--+-+---+---+
  ci-info: | Route |   Destination   |   Gateway| Genmask | 
Interface | Flags |
  ci-info: 
+---+-+--+-+---+---+
  ci-info: |   0   | 0.0.0.0 | 192.168.21.1 | 0.0.0.0 |eth0 
  |   UG  |
  ci-info: |   1   | 169.254.169.254 | 192.168.21.1 | 255.255.255.255 |eth0 
  |  UGH  |
  ci-info: |   2   |   192.168.21.0  |   0.0.0.0|  255.255.255.0  |eth0 
  |   U   |
  ci-info: 
+---+-+--+-+---+---+
  dmesg: write failed: Broken pipe
  Generating public/private rsa key pair.
  Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
  Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.
  The key fingerprint is:
  c7:fb:76:96:ae:aa:6e:73:b1:28:ea:38:40:fa:34:75 root@20180627093956
  The key's randomart image is:
  +--[ RSA 2048]+
  | |
  | |
  | |
  | .  . E  .   |
  |o  . .  S o  |
  |o o  ... |
  | + . ..o   . |[   36.260523] general protection fault:  [#1] SMP 
  [   36.260523] Modules linked in: dm_crypt kvm_intel kvm crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel serio_raw aesni_intel aes_x86_64 glue_helper 
lrw gf128mul ablk_helper cryptd psmouse floppy
  [   36.260523] CPU: 0 PID: 1 Comm: init Not tainted 3.13.0-151-generic 
#201-Ubuntu
  [   36.260523] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.10.2-1ubuntu1~cloud0 04/01/2014
  [   36.260523] task: 88007c088000 ti: 88007c086000 task.ti: 
88007c086000
  [   36.260523] RIP: 0010:[]  [] 
switch_mm_irqs_off+0xbb/0x120
  [   36.260523] RSP: 0018:88007c087ee0  EFLAGS: 00010046
  [   36.260523] RAX: 0001 RBX: 880037a54700 RCX: 
0049
  [   36.260523] RDX:  RSI: 880037a54700 RDI: 
880037a54700
  [   36.260523] RBP: 88007c087f00 R08:  R09: 

  [   36.260523] R10: 0001 R11: 88007b666780 R12: 
8800378d6700
  [   36.260523] R13:  R14: 880037653000 R15: 
880037653000
  [   36.260523] FS:  7f81d6e9a840() GS:88007fc0() 
knlGS:
  [   36.260523] CS:  0010 DS:  ES:  CR0: 80050033
  [   36.260523] CR2: 7ffcc8f0fec0 CR3: 37924000 CR4: 
00360670
  [   36.260523] DR0:  DR1:  DR2: 

  [   36.260523] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   36.260523] Stack:
  [   36.260523]  8800378d6700 88007fc13b40 880037a54700 

  [   36.260523]  88007c087f60 8173c613 88007c088000 
00013b40
  [   36.260523]  88007c087fd8 00013b40 88007c088000 
7ffcc8f10ae0
  [   36.260523] Call Trace:
  [   36.260523]  [] __schedule+0x2b3/0x750
  [   36.260523]  [] schedule_user+0x2e/0xa0
  [   36.260523]  [] sysret_careful+0x14/0x1a
  [   36.260523] Code: 24 e0 02 00 00 75 28 5b 41 5c 41 5d 41 5e 5d c3 48 8b 05 
a5 58 cb 00 48 c1 e8 33 a8 01 74 d7 31 d2 b8 01 00 00 00 b9 49 00 00 00 <0f> 30 
eb c7 

[Kernel-packages] [Bug 1727358] Re: cloud-init is slow to complete init on minimized images

[James Falcon]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3042

** Bug watch added: github.com/canonical/cloud-init/issues #3042
   https://github.com/canonical/cloud-init/issues/3042

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

Title:
  cloud-init is slow to complete init on minimized images

Status in cloud-init:
  Won't Fix
Status in cloud-init package in Ubuntu:
  Won't Fix
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in python3.6 package in Ubuntu:
  Triaged

Bug description:
  http://paste.ubuntu.com/25816789/ for the full logs.

  cloud-init is very slow to complete its initialization steps.
  Specifically, the 'init' takes over 150 seconds.

  Cloud-init v. 17.1 running 'init-local' at Wed, 25 Oct 2017 13:22:07 +. 
Up 2.39 seconds.
  2017-10-25 13:22:07,157 - util.py[WARNING]: did not find either path 
/sys/class/dmi/id or dmidecode command
  Cloud-init v. 17.1 running 'init' at Wed, 25 Oct 2017 13:22:16 +. Up 
11.37 seconds.
  ci-info: Net device 
info+
  ci-info: 
++---+-+---+---+---+
  ci-info: | Device |   Up  | Address |  Mask | Scope | 
Hw-Address|
  ci-info: 
++---+-+---+---+---+
  ci-info: | ens3:  |  True | 192.168.100.161 | 255.255.255.0 |   .   | 
52:54:00:bb:ad:fb |
  ci-info: | ens3:  |  True |.|   .   |   d   | 
52:54:00:bb:ad:fb |
  ci-info: |  lo:   |  True |127.0.0.1|   255.0.0.0   |   .   | 
. |
  ci-info: |  lo:   |  True |.|   .   |   d   | 
. |
  ci-info: | sit0:  | False |.|   .   |   .   | 
. |
  ci-info: 
++---+-+---+---+---+
  ci-info: Route IPv4 
info
  ci-info: 
+---+---+---+-+---+---+
  ci-info: | Route |  Destination  |Gateway| Genmask | 
Interface | Flags |
  ci-info: 
+---+---+---+-+---+---+
  ci-info: |   0   |0.0.0.0| 192.168.100.1 | 0.0.0.0 |ens3  
 |   UG  |
  ci-info: |   1   | 192.168.100.0 |0.0.0.0|  255.255.255.0  |ens3  
 |   U   |
  ci-info: |   2   | 192.168.100.1 |0.0.0.0| 255.255.255.255 |ens3  
 |   UH  |
  ci-info: 
+---+---+---+-+---+---+
  2017-10-25 13:24:38,187 - util.py[WARNING]: Failed to resize filesystem 
(cmd=('resize2fs', '/dev/root'))
  2017-10-25 13:24:38,193 - util.py[WARNING]: Running module resizefs () failed
  Generating public/private rsa key pair.
  Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
  Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.
  The key fingerprint is:
  SHA256:LKNlCqqOgPB8KBKGfPhFO5Rs6fDMnAvVet/W9i4vLxY root@cloudimg
  The key's randomart image is:
  +---[RSA 2048]+
  | |
  |. +  |
  |   . O . |
  |o . % +. |
  |++.o %=.S|
  |+=ooo=+o. . .E   |
  |* +.+.   . o o.  |
  |=. .  . .=.  |
  |+.  . B= |
  +[SHA256]-+
  Generating public/private dsa key pair.
  Your identification has been saved in /etc/ssh/ssh_host_dsa_key.
  Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.
  The key fingerprint is:
  SHA256:dNWNyBHqTUCl820/vL0dEhOVDFYJzqr1WeuqV1PAmjk root@cloudimg
  The key's randomart image is:
  +---[DSA 1024]+
  | .oo=X==o|
  |   =* *+.|
  |. = .B . |
  |   . o =E.. .|
  |S .oo+o..|
  |  o ..*+.|
  | .   +.=o|
  | .o *|
  |   .o..++|
  +[SHA256]-+
  Generating public/private ecdsa key pair.
  Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key.
  Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub.
  The key fingerprint is:
  SHA256:N3RTlPa7KU5ryq6kJAO8Tiq90ub4P1DGSofn6jFkM3k root@cloudimg
  The key's randomart image is:
  +---[ECDSA 256]---+
  | .o. |
  | .o  |
  |   o  . o. . |
  |  +.*. . .  .|
  | .*XE   S o .|
  | oo++. .   . |
  | oo= o . .   .  o|
  |o.Oo. + o . .o.o |
  |oB=+.. . .o++o.  |
  +[SHA256]-+
  Generating public/private ed25519 key pair.
  Your identification has been saved in /etc/ssh/ssh_host_ed25519_key.
  Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub.
  The key fingerprint is:
  SHA256:B6B/1SyUB/TFPfmU1ADIotnD+wjISO5L2JZkWe2lDUA root@cloudimg
  The key's randomart image is:
  +--[ED25519 256]--+
  |   .E .  o++.o+++|
  | + ...++...++|
  |o o=o.o.+  

[Kernel-packages] [Bug 1701297] Re: NTP reload failure (unable to read library) on overlayfs

[James Falcon]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2936

** Bug watch added: github.com/canonical/cloud-init/issues #2936
   https://github.com/canonical/cloud-init/issues/2936

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

Title:
  NTP reload failure (unable to read library) on overlayfs

Status in cloud-init:
  Won't Fix
Status in apparmor package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-
  init/0.7.9-153-g16a7302f-0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

  Related bugs:
   * bug 1645644: cloud-init ntp not using expected servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

[James Falcon]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2858

** Bug watch added: github.com/canonical/cloud-init/issues #2858
   https://github.com/canonical/cloud-init/issues/2858

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

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

   * cloud-init test case

  
  
  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/get-proposed-cloudimg;
  chmod 755 get-proposed-cloudimg;

  for release in xenial yakkety zesty; do
./get-proposed-cloudimg $release;
MODE=vlan ./btest-launch.sh $release-server-cloudimg-amd64-proposed.img 
;
# ubuntu/passw0rd
python3 -c 'from cloudinit.net import get_interfaces_by_mac; 
print(get_interfaces_by_mac())'; # results in no runtime error and doesn't 
report vlan interface name
  done
   


  
  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.7+ kernels.

  [Other Info]

   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into
  v4.4 kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs

  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.

  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
  to the MAC of the physical interface and thus for DAD to behave as
  expected.

  Signed-off-by: Mike Manning 
  Signed-off-by: David S. Miller 

   * Original bug report

  When attempting to verify sru for bug 1669860, I found that vlans
  are not properly filtered out by 'get_interfaces_by_mac'.  That means
  that the bug is still present with vlans.

  The reason for this is that /sys/class/net//addr_assign_type
  shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8.
  See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
  for doc on addr_assign_type.

  Related bugs:
   * bug 1669860: cloud-init attempts to rename bonds

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1682871/+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 1551747] Re: ubuntu-fan causes issues during network configuration

[James Falcon]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2623

** Bug watch added: github.com/canonical/cloud-init/issues #2623
   https://github.com/canonical/cloud-init/issues/2623

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

Title:
  ubuntu-fan causes issues during network configuration

Status in cloud-init:
  Invalid
Status in Snappy:
  Invalid
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Yakkety:
  Fix Released

Bug description:
  it seems that ubuntu-fan is causing issues with network configuration.

  On 16.04 daily image:

  root@localhost:~# snappy list
  NameDate   Version  Developer
  canonical-pi2   2016-02-02 3.0  canonical
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical
  ubuntu-core 2016-02-22 16.04.0-10.armhf canonical

  I see this when I'm activating a wifi card on a raspberry pi 2.

  root@localhost:~# ifdown wlan0
  ifdown: interface wlan0 not configured
  root@localhost:~# ifup wlan0
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/wlan0/c4:e9:84:17:31:9b
  Sending on   LPF/wlan0/c4:e9:84:17:31:9b
  Sending on   Socket/fallback
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x81c0c95e)
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x81c0c95e)
  DHCPREQUEST of 192.168.0.170 on wlan0 to 255.255.255.255 port 67 
(xid=0x5ec9c081)
  DHCPOFFER of 192.168.0.170 from 192.168.0.251
  DHCPACK of 192.168.0.170 from 192.168.0.251
  RTNETLINK answers: File exists
  bound to 192.168.0.170 -- renewal in 17145 seconds.
  run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1
  Failed to bring up wlan0.

  ===
  [Impact]

  Installing ubuntu-fan can trigger error messages when initialising
  with no fan configuration.

  [Test Case]

  As above.

  [Regression Potential]

  Low, suppresses errorneous error messages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1551747/+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 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails

[James Falcon]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2586

** Bug watch added: github.com/canonical/cloud-init/issues #2586
   https://github.com/canonical/cloud-init/issues/2586

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

Title:
  maas wily deployment to HP Proliant m400 arm64 server cartridge fails

Status in cloud-init:
  Fix Released
Status in curtin:
  Invalid
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in cloud-init source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  This is the error seen on the console:

  [   64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: 
Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin
  [  124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - 
url_helper.py[WARNING]: Calling 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
[2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', 
port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id 
(Caused by 
ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect 
timeout=50.0)'))]
  [  124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - 
DataSourceEc2.py[CRITICAL]: Giving up on md from 
['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds
  [  124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - 
url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404]

  This times out eventually and the node is left at the login prompt. I
  can install wily via netboot without issue and some time back, wily
  was deployable to this node from MAAS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1499869/+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 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured

[James Troup]

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

Title:
  Intel E810 NICs driver in causing hangs when booting and bonds
  configured

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  jammy 22.04.1
  linux-image-generic 5.15.0-58-generic
  Intel E810-XXV Dual Port NICs in Dell PowerEdge 650

  - 5.15 in jammy -> reproducible
  - 5.19 in hwe-edge -> reproducible
  - 6.2.rc6 in the mainline build -> works
  - Intel's ice driver 1.10.1.2.2 -> works

  
  After beonding is enabled on switch and server side, the system will hang at 
initialing ubuntu.  The kernel loads but around starting the Network Services 
the system can hang for sometimes 5 minutes, and in other cases, indefinitely.

  The message of:

  echo 0 > /proc/sys/kernel/hung_task_timeout_sec”  systemd-resolve
  blocked for more than 120 seconds

  appears, and eventually the Network services just attempts to start
  and never does.  This is with or without DHCP enabled.

  Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and
  linux-oem kernels and all exhibit the same failure.

  To work around this. installing the Intel 'ice' driver of version
  1.10.1.2.2 works.  The system doesn't even remotely hang at startup
  and all networking functions remain working (ping, DNS, general
  accessibility).

  The driver can be found at 
https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 31 13:08 seq
   crw-rw 1 root audio 116, 33 Jan 31 13:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5json:
   {
     "result": "skip"
   }DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia: 
Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R650
  Package: linux (not installed)
  PciMultimedia:

  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'Tags:  jammy 
uec-images
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 0PJ7YJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd09/14/2022:br1.8:svnDellInc.:pnPowerEdgeR650:pvr:rvnDellInc.:rn0PJ7YJ:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=0912;ModelName=PowerEdgeR650:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R650
  dmi.product.sku: SKU=0912;ModelName=PowerEdge R650
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262/+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 2004099] [NEW] package linux-image-5.15.0-58-generic 5.15.0-58.64 failed to install/upgrade: installed linux-image-5.15.0-58-generic package post-installation script subprocess

[Clay James]

Public bug reported:

i have no idea, new to linux

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-58-generic 5.15.0-58.64
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  clay931 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Jan 29 01:12:22 2023
DuplicateSignature:
 package:linux-image-5.15.0-58-generic:5.15.0-58.64
 Setting up linux-image-5.15.0-58-generic (5.15.0-58.64) ...
 Bus error (core dumped)
 dpkg: error processing package linux-image-5.15.0-58-generic (--configure):
  installed linux-image-5.15.0-58-generic package post-installation script 
subprocess returned error exit status 135
ErrorMessage: installed linux-image-5.15.0-58-generic package post-installation 
script subprocess returned error exit status 135
InstallationDate: Installed on 2022-12-03 (56 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
IwConfig:
 lono wireless extensions.
 
 enp9s0no wireless extensions.
MachineType: Dell Inc. Latitude E5500
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=9f03f959-50ba-42d3-857d-b32606040dd0 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
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: grub-pc 2.06-2ubuntu7.1
RfKill:
 0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-5.15.0-58-generic 5.15.0-58.64 failed to 
install/upgrade: installed linux-image-5.15.0-58-generic package 
post-installation script subprocess returned error exit status 135
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2009
dmi.bios.release: 1.1
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0DW634
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd04/15/2009:br1.1:efr1.1:svnDellInc.:pnLatitudeE5500:pvr:rvnDellInc.:rn0DW634:rvr:cvnDellInc.:ct8:cvr:sku:
dmi.product.name: Latitude E5500
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package hardware-error jammy 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/2004099

Title:
  package linux-image-5.15.0-58-generic 5.15.0-58.64 failed to
  install/upgrade: installed linux-image-5.15.0-58-generic package post-
  installation script subprocess returned error exit status 135

Status in linux package in Ubuntu:
  Invalid

Bug description:
  i have no idea, new to linux

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-58-generic 5.15.0-58.64
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clay931 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sun Jan 29 01:12:22 2023
  DuplicateSignature:
   package:linux-image-5.15.0-58-generic:5.15.0-58.64
   Setting up linux-image-5.15.0-58-generic (5.15.0-58.64) ...
   Bus error (core dumped)
   dpkg: error processing package linux-image-5.15.0-58-generic (--configure):
installed linux-image-5.15.0-58-generic package post-installation script 
subprocess returned error exit status 135
  ErrorMessage: installed linux-image-5.15.0-58-generic package 
post-installation script subprocess returned error exit status 135
  InstallationDate: Installed on 2022-12-03 (56 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: Dell Inc. Latitude E5500
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=9f03f959-50ba-42d3-857d-b32606040dd0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: 

[Kernel-packages] [Bug 1239459] Re: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds

[Joff James]

Hey Admin! I just love your content. Here are some of mine. Please let me know 
if you like them. Thank you!
https://www.gadgetswhy.com/access-lg-smart-tv-secret-menu/

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

Title:
  1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few
  seconds

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  With the new 3.11.0-12-generic kernel, wifi has problems to connect with many 
errors like these:
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: 
rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrea 1791 F pulseaudio
  Date: Sun Oct 13 23:45:04 2013
  HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15
  InstallationDate: Installed on 2013-10-12 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. X200CA
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200CA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[james]

FYI: I have built a kernel with the previously (on this thread) discussed patch 
(on a 5.4 kernel) and I still have the error multiple times per day.


(In reply to James H from comment #207)
> I'm using a 2.5gb ethernet usb device and getting this error intermittently
> (a dozen times per day).
> 
> $ uname -a
> Linux hephaestus 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC
> 2022 x86_64 x86_64 x86_64 GNU/Linux
> 
> 
> $ lsusb
> 
> Bus 003 Device 016: ID 0bda:8156 Realtek Semiconductor Corp. USB
> 10/100/1G/2.5G 
> 
> 
> 
> This is what plays out via /var/log/syslog each time:
> 
> Dec 21 10:26:47 hephaestus kernel: [346923.166782] usb 3-4: USB disconnect,
> device number 15
> Dec 21 10:26:47 hephaestus kernel: [346923.166913] xhci_hcd :00:14.0:
> WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> Dec 21 10:26:47 hephaestus kernel: [346923.166927] cdc_ncm 3-4:2.0 eth1:
> unregister 'cdc_ncm' usb-:00:14.0-4, CDC NCM
> Dec 21 10:26:47 hephaestus kernel: [346923.167071] xhci_hcd :00:14.0:
> WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> Dec 21 10:26:47 hephaestus kernel: [346923.170644] xhci_hcd :00:14.0:
> WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> Dec 21 10:26:47 hephaestus dhclient[320734]: receive_packet failed on eth1:
> Network is down
> Dec 21 10:26:47 hephaestus systemd[1]: Stopping ifup for eth1...
> Dec 21 10:26:47 hephaestus dhclient[325522]: Killed old client process
> Dec 21 10:26:47 hephaestus ifdown[325522]: Killed old client process
> Dec 21 10:26:47 hephaestus kernel: [346923.478913] usb 3-4: new SuperSpeed
> Gen 1 USB device number 16 using xhci_hcd
> Dec 21 10:26:47 hephaestus kernel: [346923.499567] usb 3-4: New USB device
> found, idVendor=0bda, idProduct=8156, bcdDevice=31.00
> Dec 21 10:26:47 hephaestus kernel: [346923.499573] usb 3-4: New USB device
> strings: Mfr=1, Product=2, SerialNumber=6
> Dec 21 10:26:47 hephaestus kernel: [346923.499577] usb 3-4: Product: USB
> 10/100/1G/2.5G LAN
> Dec 21 10:26:47 hephaestus kernel: [346923.499580] usb 3-4: Manufacturer:
> Realtek
> Dec 21 10:26:47 hephaestus kernel: [346923.499583] usb 3-4: SerialNumber:
> 00101
> Dec 21 10:26:47 hephaestus kernel: [346923.523736] cdc_ncm 3-4:2.0:
> MAC-Address: xx:xx:xx:xx:xx:xx
> Dec 21 10:26:47 hephaestus kernel: [346923.523742] cdc_ncm 3-4:2.0: setting
> rx_max = 16384
> Dec 21 10:26:47 hephaestus kernel: [346923.523836] cdc_ncm 3-4:2.0: setting
> tx_max = 16384
> Dec 21 10:26:47 hephaestus kernel: [346923.524578] cdc_ncm 3-4:2.0 eth1:
> register 'cdc_ncm' at usb-:00:14.0-4, CDC NCM, xx:xx:xx:xx:xx:xx
> Dec 21 10:26:47 hephaestus systemd-udevd[325501]: Using default interface
> naming scheme 'v245'.
> Dec 21 10:26:47 hephaestus systemd-udevd[325501]: ethtool: autonegotiation
> is unset or enabled, the speed and duplex are not writable.
> Dec 21 10:26:47 hephaestus systemd[1]: Found device USB_10_100_1G_2.5G_LAN.
> (then things start back up and the ethernet link goes live again after about
> 10 seconds)

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  Fix Released
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-
  live/current/zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 

[Kernel-packages] [Bug 1749961]

[james]

FYI: I have built a kernel with the previously (on this thread) discussed patch 
(on a 5.4 kernel) and I still have the error multiple times per day.


(In reply to James H from comment #207)
> I'm using a 2.5gb ethernet usb device and getting this error intermittently
> (a dozen times per day).
> 
> $ uname -a
> Linux hephaestus 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC
> 2022 x86_64 x86_64 x86_64 GNU/Linux
> 
> 
> $ lsusb
> 
> Bus 003 Device 016: ID 0bda:8156 Realtek Semiconductor Corp. USB
> 10/100/1G/2.5G 
> 
> 
> 
> This is what plays out via /var/log/syslog each time:
> 
> Dec 21 10:26:47 hephaestus kernel: [346923.166782] usb 3-4: USB disconnect,
> device number 15
> Dec 21 10:26:47 hephaestus kernel: [346923.166913] xhci_hcd :00:14.0:
> WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> Dec 21 10:26:47 hephaestus kernel: [346923.166927] cdc_ncm 3-4:2.0 eth1:
> unregister 'cdc_ncm' usb-:00:14.0-4, CDC NCM
> Dec 21 10:26:47 hephaestus kernel: [346923.167071] xhci_hcd :00:14.0:
> WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> Dec 21 10:26:47 hephaestus kernel: [346923.170644] xhci_hcd :00:14.0:
> WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
> Dec 21 10:26:47 hephaestus dhclient[320734]: receive_packet failed on eth1:
> Network is down
> Dec 21 10:26:47 hephaestus systemd[1]: Stopping ifup for eth1...
> Dec 21 10:26:47 hephaestus dhclient[325522]: Killed old client process
> Dec 21 10:26:47 hephaestus ifdown[325522]: Killed old client process
> Dec 21 10:26:47 hephaestus kernel: [346923.478913] usb 3-4: new SuperSpeed
> Gen 1 USB device number 16 using xhci_hcd
> Dec 21 10:26:47 hephaestus kernel: [346923.499567] usb 3-4: New USB device
> found, idVendor=0bda, idProduct=8156, bcdDevice=31.00
> Dec 21 10:26:47 hephaestus kernel: [346923.499573] usb 3-4: New USB device
> strings: Mfr=1, Product=2, SerialNumber=6
> Dec 21 10:26:47 hephaestus kernel: [346923.499577] usb 3-4: Product: USB
> 10/100/1G/2.5G LAN
> Dec 21 10:26:47 hephaestus kernel: [346923.499580] usb 3-4: Manufacturer:
> Realtek
> Dec 21 10:26:47 hephaestus kernel: [346923.499583] usb 3-4: SerialNumber:
> 00101
> Dec 21 10:26:47 hephaestus kernel: [346923.523736] cdc_ncm 3-4:2.0:
> MAC-Address: xx:xx:xx:xx:xx:xx
> Dec 21 10:26:47 hephaestus kernel: [346923.523742] cdc_ncm 3-4:2.0: setting
> rx_max = 16384
> Dec 21 10:26:47 hephaestus kernel: [346923.523836] cdc_ncm 3-4:2.0: setting
> tx_max = 16384
> Dec 21 10:26:47 hephaestus kernel: [346923.524578] cdc_ncm 3-4:2.0 eth1:
> register 'cdc_ncm' at usb-:00:14.0-4, CDC NCM, xx:xx:xx:xx:xx:xx
> Dec 21 10:26:47 hephaestus systemd-udevd[325501]: Using default interface
> naming scheme 'v245'.
> Dec 21 10:26:47 hephaestus systemd-udevd[325501]: ethtool: autonegotiation
> is unset or enabled, the speed and duplex are not writable.
> Dec 21 10:26:47 hephaestus systemd[1]: Found device USB_10_100_1G_2.5G_LAN.
> (then things start back up and the ethernet link goes live again after about
> 10 seconds)

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR T

[Kernel-packages] [Bug 2000652] [NEW] Ubuntu 20.04 on Nvidia DPU sometimes shows eMMC error

[James Tau]

Public bug reported:

In some cases, we see that the Ubuntu 20.04 kernel
(5.4.0-1023-bluefield) complains about the eMMC:

Line 107: [Thu Nov 3 19:45:36 2022] dw_mmc PRP0001:00: IDMAC supports 64-bit 
address mode.
Line 108: [Thu Nov 3 19:45:36 2022] dw_mmc PRP0001:00: Using internal DMA 
controller.
Line 109: [Thu Nov 3 19:45:36 2022] dw_mmc PRP0001:00: Version ID is 270a
Line 110: [Thu Nov 3 19:45:36 2022] dw_mmc PRP0001:00: DW MMC controller at irq 
13,32 bit host data width,256 deep fifo
Line 110: [Thu Nov 3 19:45:36 2022] dw_mmc PRP0001:00: DW MMC controller at irq 
13,32 bit host data width,256 deep fifo
Line 111: [Thu Nov 3 19:45:36 2022] mmc_host mmc0: Bus speed (slot 0) = 
5000Hz (slot req 40Hz, actual 396825HZ div = 63)
Line 111: [Thu Nov 3 19:45:36 2022] mmc_host mmc0: Bus speed (slot 0) = 
5000Hz (slot req 40Hz, actual 396825HZ div = 63)
Line 155: [Thu Nov 3 19:45:36 2022] mmc_host mmc0: Bus speed (slot 0) = 
5000Hz (slot req 5000Hz, actual 5000HZ div = 0)
Line 155: [Thu Nov 3 19:45:36 2022] mmc_host mmc0: Bus speed (slot 0) = 
5000Hz (slot req 5000Hz, actual 5000HZ div = 0)
Line 156: [Thu Nov 3 19:45:36 2022] mmc0: new high speed MMC card at address 
0001
Line 156: [Thu Nov 3 19:45:36 2022] mmc0: new high speed MMC card at address 
0001
Line 157: [Thu Nov 3 19:45:36 2022] mmcblk0: mmc0:0001 TA2964 58.3 GiB
Line 157: [Thu Nov 3 19:45:36 2022] mmcblk0: mmc0:0001 TA2964 58.3 GiB
Line 158: [Thu Nov 3 19:45:36 2022] mmcblk0boot0: mmc0:0001 TA2964 partition 1 
4.00 MiB
Line 158: [Thu Nov 3 19:45:36 2022] mmcblk0boot0: mmc0:0001 TA2964 partition 1 
4.00 MiB
Line 159: [Thu Nov 3 19:45:36 2022] mmcblk0boot1: mmc0:0001 TA2964 partition 2 
4.00 MiB
Line 159: [Thu Nov 3 19:45:36 2022] mmcblk0boot1: mmc0:0001 TA2964 partition 2 
4.00 MiB
Line 160: [Thu Nov 3 19:45:36 2022] mmcblk0: p1 p2
Line 376: [Thu Nov 3 19:46:56 2022] mmc_host mmc0: Timeout sending command (cmd 
0×20 arg 0×0 status 0×8020)
Line 376: [Thu Nov 3 19:46:56 2022] mmc_host mmc0: Timeout sending command (cmd 
0×20 arg 0×0 status 0×8020)
Line 377: [Thu Nov 3 19:46:57 2022] dw_mmc PRP0001:00: Card stuck in wrong 
state! card_busy_detect status: 0×0

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

** Summary changed:

- Ubuntu 20.04 on Nvidia DPU sometimes show eMMC error
+ Ubuntu 20.04 on Nvidia DPU sometimes shows eMMC error

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

Title:
  Ubuntu 20.04 on Nvidia DPU sometimes shows eMMC error

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  In some cases, we see that the Ubuntu 20.04 kernel
  (5.4.0-1023-bluefield) complains about the eMMC:

  Line 107: [Thu Nov 3 19:45:36 2022] dw_mmc PRP0001:00: IDMAC supports 64-bit 
address mode.
  Line 108: [Thu Nov 3 19:45:36 2022] dw_mmc PRP0001:00: Using internal DMA 
controller.
  Line 109: [Thu Nov 3 19:45:36 2022] dw_mmc PRP0001:00: Version ID is 270a
  Line 110: [Thu Nov 3 19:45:36 2022] dw_mmc PRP0001:00: DW MMC controller at 
irq 13,32 bit host data width,256 deep fifo
  Line 110: [Thu Nov 3 19:45:36 2022] dw_mmc PRP0001:00: DW MMC controller at 
irq 13,32 bit host data width,256 deep fifo
  Line 111: [Thu Nov 3 19:45:36 2022] mmc_host mmc0: Bus speed (slot 0) = 
5000Hz (slot req 40Hz, actual 396825HZ div = 63)
  Line 111: [Thu Nov 3 19:45:36 2022] mmc_host mmc0: Bus speed (slot 0) = 
5000Hz (slot req 40Hz, actual 396825HZ div = 63)
  Line 155: [Thu Nov 3 19:45:36 2022] mmc_host mmc0: Bus speed (slot 0) = 
5000Hz (slot req 5000Hz, actual 5000HZ div = 0)
  Line 155: [Thu Nov 3 19:45:36 2022] mmc_host mmc0: Bus speed (slot 0) = 
5000Hz (slot req 5000Hz, actual 5000HZ div = 0)
  Line 156: [Thu Nov 3 19:45:36 2022] mmc0: new high speed MMC card at address 
0001
  Line 156: [Thu Nov 3 19:45:36 2022] mmc0: new high speed MMC card at address 
0001
  Line 157: [Thu Nov 3 19:45:36 2022] mmcblk0: mmc0:0001 TA2964 58.3 GiB
  Line 157: [Thu Nov 3 19:45:36 2022] mmcblk0: mmc0:0001 TA2964 58.3 GiB
  Line 158: [Thu Nov 3 19:45:36 2022] mmcblk0boot0: mmc0:0001 TA2964 partition 
1 4.00 MiB
  Line 158: [Thu Nov 3 19:45:36 2022] mmcblk0boot0: mmc0:0001 TA2964 partition 
1 4.00 MiB
  Line 159: [Thu Nov 3 19:45:36 2022] mmcblk0boot1: mmc0:0001 TA2964 partition 
2 4.00 MiB
  Line 159: [Thu Nov 3 19:45:36 2022] mmcblk0boot1: mmc0:0001 TA2964 partition 
2 4.00 MiB
  Line 160: [Thu Nov 3 19:45:36 2022] mmcblk0: p1 p2
  Line 376: [Thu Nov 3 19:46:56 2022] mmc_host mmc0: Timeout sending command 
(cmd 0×20 arg 0×0 status 0×8020)
  Line 376: [Thu Nov 3 19:46:56 2022] mmc_host mmc0: Timeout sending command 
(cmd 0×20 arg 0×0 status 0×8020)
  Line 377: [Thu Nov 3 19:46:57 2022] dw_mmc PRP0001:00: Card stuck in wrong 
state! card_busy_detect status: 0×0

To manage notifications about this 

[Kernel-packages] [Bug 1667750]

[james]

I'm using a 2.5gb ethernet usb device and getting this error
intermittently (a dozen times per day).

$ uname -a
Linux hephaestus 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux


$ lsusb

Bus 003 Device 016: ID 0bda:8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G 


This is what plays out via /var/log/syslog each time:

Dec 21 10:26:47 hephaestus kernel: [346923.166782] usb 3-4: USB disconnect, 
device number 15
Dec 21 10:26:47 hephaestus kernel: [346923.166913] xhci_hcd :00:14.0: WARN 
Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 21 10:26:47 hephaestus kernel: [346923.166927] cdc_ncm 3-4:2.0 eth1: 
unregister 'cdc_ncm' usb-:00:14.0-4, CDC NCM
Dec 21 10:26:47 hephaestus kernel: [346923.167071] xhci_hcd :00:14.0: WARN 
Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 21 10:26:47 hephaestus kernel: [346923.170644] xhci_hcd :00:14.0: WARN 
Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 21 10:26:47 hephaestus dhclient[320734]: receive_packet failed on eth1: 
Network is down
Dec 21 10:26:47 hephaestus systemd[1]: Stopping ifup for eth1...
Dec 21 10:26:47 hephaestus dhclient[325522]: Killed old client process
Dec 21 10:26:47 hephaestus ifdown[325522]: Killed old client process
Dec 21 10:26:47 hephaestus kernel: [346923.478913] usb 3-4: new SuperSpeed Gen 
1 USB device number 16 using xhci_hcd
Dec 21 10:26:47 hephaestus kernel: [346923.499567] usb 3-4: New USB device 
found, idVendor=0bda, idProduct=8156, bcdDevice=31.00
Dec 21 10:26:47 hephaestus kernel: [346923.499573] usb 3-4: New USB device 
strings: Mfr=1, Product=2, SerialNumber=6
Dec 21 10:26:47 hephaestus kernel: [346923.499577] usb 3-4: Product: USB 
10/100/1G/2.5G LAN
Dec 21 10:26:47 hephaestus kernel: [346923.499580] usb 3-4: Manufacturer: 
Realtek
Dec 21 10:26:47 hephaestus kernel: [346923.499583] usb 3-4: SerialNumber: 
00101
Dec 21 10:26:47 hephaestus kernel: [346923.523736] cdc_ncm 3-4:2.0: 
MAC-Address: xx:xx:xx:xx:xx:xx
Dec 21 10:26:47 hephaestus kernel: [346923.523742] cdc_ncm 3-4:2.0: setting 
rx_max = 16384
Dec 21 10:26:47 hephaestus kernel: [346923.523836] cdc_ncm 3-4:2.0: setting 
tx_max = 16384
Dec 21 10:26:47 hephaestus kernel: [346923.524578] cdc_ncm 3-4:2.0 eth1: 
register 'cdc_ncm' at usb-:00:14.0-4, CDC NCM, xx:xx:xx:xx:xx:xx
Dec 21 10:26:47 hephaestus systemd-udevd[325501]: Using default interface 
naming scheme 'v245'.
Dec 21 10:26:47 hephaestus systemd-udevd[325501]: ethtool: autonegotiation is 
unset or enabled, the speed and duplex are not writable.
Dec 21 10:26:47 hephaestus systemd[1]: Found device USB_10_100_1G_2.5G_LAN.
(then things start back up and the ethernet link goes live again after about 10 
seconds)

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  Fix Released
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-
  live/current/zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: 

[Kernel-packages] [Bug 1749961]

[james]

I'm using a 2.5gb ethernet usb device and getting this error
intermittently (a dozen times per day).

$ uname -a
Linux hephaestus 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux


$ lsusb

Bus 003 Device 016: ID 0bda:8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G 


This is what plays out via /var/log/syslog each time:

Dec 21 10:26:47 hephaestus kernel: [346923.166782] usb 3-4: USB disconnect, 
device number 15
Dec 21 10:26:47 hephaestus kernel: [346923.166913] xhci_hcd :00:14.0: WARN 
Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 21 10:26:47 hephaestus kernel: [346923.166927] cdc_ncm 3-4:2.0 eth1: 
unregister 'cdc_ncm' usb-:00:14.0-4, CDC NCM
Dec 21 10:26:47 hephaestus kernel: [346923.167071] xhci_hcd :00:14.0: WARN 
Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 21 10:26:47 hephaestus kernel: [346923.170644] xhci_hcd :00:14.0: WARN 
Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 21 10:26:47 hephaestus dhclient[320734]: receive_packet failed on eth1: 
Network is down
Dec 21 10:26:47 hephaestus systemd[1]: Stopping ifup for eth1...
Dec 21 10:26:47 hephaestus dhclient[325522]: Killed old client process
Dec 21 10:26:47 hephaestus ifdown[325522]: Killed old client process
Dec 21 10:26:47 hephaestus kernel: [346923.478913] usb 3-4: new SuperSpeed Gen 
1 USB device number 16 using xhci_hcd
Dec 21 10:26:47 hephaestus kernel: [346923.499567] usb 3-4: New USB device 
found, idVendor=0bda, idProduct=8156, bcdDevice=31.00
Dec 21 10:26:47 hephaestus kernel: [346923.499573] usb 3-4: New USB device 
strings: Mfr=1, Product=2, SerialNumber=6
Dec 21 10:26:47 hephaestus kernel: [346923.499577] usb 3-4: Product: USB 
10/100/1G/2.5G LAN
Dec 21 10:26:47 hephaestus kernel: [346923.499580] usb 3-4: Manufacturer: 
Realtek
Dec 21 10:26:47 hephaestus kernel: [346923.499583] usb 3-4: SerialNumber: 
00101
Dec 21 10:26:47 hephaestus kernel: [346923.523736] cdc_ncm 3-4:2.0: 
MAC-Address: xx:xx:xx:xx:xx:xx
Dec 21 10:26:47 hephaestus kernel: [346923.523742] cdc_ncm 3-4:2.0: setting 
rx_max = 16384
Dec 21 10:26:47 hephaestus kernel: [346923.523836] cdc_ncm 3-4:2.0: setting 
tx_max = 16384
Dec 21 10:26:47 hephaestus kernel: [346923.524578] cdc_ncm 3-4:2.0 eth1: 
register 'cdc_ncm' at usb-:00:14.0-4, CDC NCM, xx:xx:xx:xx:xx:xx
Dec 21 10:26:47 hephaestus systemd-udevd[325501]: Using default interface 
naming scheme 'v245'.
Dec 21 10:26:47 hephaestus systemd-udevd[325501]: ethtool: autonegotiation is 
unset or enabled, the speed and duplex are not writable.
Dec 21 10:26:47 hephaestus systemd[1]: Found device USB_10_100_1G_2.5G_LAN.
(then things start back up and the ethernet link goes live again after about 10 
seconds)

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13

  A similar issue was already reported on Launchpad:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750

  The fix to this issue seems to be the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109

  Tests in our scenario with this patch proved still broken. Our next
  approach is to modify the patch a bit and re-test.

  

[Kernel-packages] [Bug 1998863] [NEW] mlxbf-pmc: Fix event string typo

[James Hurley]

Public bug reported:

SRU Justification:

[Impact]

Due to a typo, duplicate events are shown

[Fix]

* Fix event name typo.

[Test Case]

* cd /sys/class/hwmon/hwmon0/tilenetX ("X" may be 0..7)
root@localhost:/sys/class/hwmon/hwmon0/tilenet3# cat event_list | grep CRED
15: CDN_DIAG_N_OUT_OF_CRED
16: CDN_DIAG_S_OUT_OF_CRED
17: CDN_DIAG_E_OUT_OF_CRED
18: CDN_DIAG_W_OUT_OF_CRED
19: CDN_DIAG_C_OUT_OF_CRED
25: DDN_DIAG_N_OUT_OF_CRED
26: DDN_DIAG_S_OUT_OF_CRED
27: DDN_DIAG_E_OUT_OF_CRED
28: DDN_DIAG_W_OUT_OF_CRED
29: DDN_DIAG_C_OUT_OF_CRED
35: NDN_DIAG_N_OUT_OF_CRED  <== Incorrectly was set to NDN_DIAG_S_OUT_OF_CRED
36: NDN_DIAG_S_OUT_OF_CRED
37: NDN_DIAG_E_OUT_OF_CRED
38: NDN_DIAG_W_OUT_OF_CRED
39: NDN_DIAG_C_OUT_OF_CRED
 

[Regression Potential]

* Duplicate events still get shown

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

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

Title:
  mlxbf-pmc: Fix event string typo

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  Due to a typo, duplicate events are shown

  [Fix]

  * Fix event name typo.

  [Test Case]

  * cd /sys/class/hwmon/hwmon0/tilenetX ("X" may be 0..7)
  root@localhost:/sys/class/hwmon/hwmon0/tilenet3# cat event_list | grep CRED
  15: CDN_DIAG_N_OUT_OF_CRED
  16: CDN_DIAG_S_OUT_OF_CRED
  17: CDN_DIAG_E_OUT_OF_CRED
  18: CDN_DIAG_W_OUT_OF_CRED
  19: CDN_DIAG_C_OUT_OF_CRED
  25: DDN_DIAG_N_OUT_OF_CRED
  26: DDN_DIAG_S_OUT_OF_CRED
  27: DDN_DIAG_E_OUT_OF_CRED
  28: DDN_DIAG_W_OUT_OF_CRED
  29: DDN_DIAG_C_OUT_OF_CRED
  35: NDN_DIAG_N_OUT_OF_CRED  <== Incorrectly was set to NDN_DIAG_S_OUT_OF_CRED
  36: NDN_DIAG_S_OUT_OF_CRED
  37: NDN_DIAG_E_OUT_OF_CRED
  38: NDN_DIAG_W_OUT_OF_CRED
  39: NDN_DIAG_C_OUT_OF_CRED
   

  [Regression Potential]

  * Duplicate events still get shown

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


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

[Kernel-packages] [Bug 1990190] Re: Focal update: v5.4.211 upstream stable release

[James Dingwall]

I have encountered the problem noted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990190/comments/4
with prometheus-node-exporter on a Raspberry Pi running kernel
5.4.0-1074-raspi.

I've also seen a similar problem with CouchDB 3.2.2 on 5.4.0-133.149
(local build), we didn't encounter the issue on the same systems which
were previously running 5.4.0-131.147.

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

Title:
  Focal update: v5.4.211 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification

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

     v5.4.211 upstream stable release
     from git://git.kernel.org/

  Makefile: link with -z noexecstack --no-warn-rwx-segments
  x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments
  scsi: Revert "scsi: qla2xxx: Fix disk failure to rediscover"
  ALSA: bcd2000: Fix a UAF bug on the error path of probing
  igc: Remove _I_PHY_ID checking
  wifi: mac80211_hwsim: fix race condition in pending packet
  wifi: mac80211_hwsim: add back erroneously removed cast
  wifi: mac80211_hwsim: use 32-bit skb cookie
  add barriers to buffer_uptodate and set_buffer_uptodate
  HID: wacom: Only report rotation for art pen
  HID: wacom: Don't register pad_input for touch switch
  KVM: nVMX: Snapshot pre-VM-Enter BNDCFGS for !nested_run_pending case
  KVM: nVMX: Snapshot pre-VM-Enter DEBUGCTL for !nested_run_pending case
  KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0
  KVM: nVMX: Let userspace set nVMX MSR to any _host_ supported value
  KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks
  KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP
  mm/mremap: hold the rmap lock in write mode when moving page table entries.
  ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model
  ALSA: hda/cirrus - support for iMac 12,1 model
  ALSA: hda/realtek: Add quirk for another Asus K42JZ model
  tty: vt: initialize unicode screen buffer
  vfs: Check the truncate maximum size in inode_newsize_ok()
  fs: Add missing umask strip in vfs_tmpfile
  thermal: sysfs: Fix cooling_device_stats_setup() error code path
  fbcon: Fix boundary checks for fbcon=vc:n1-n2 parameters
  usbnet: Fix linkwatch use-after-free on disconnect
  ovl: drop WARN_ON() dentry is NULL in ovl_encode_fh()
  parisc: Fix device names in /proc/iomem
  parisc: io_pgetevents_time64() needs compat syscall in 32-bit compat mode
  drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error
  drm/nouveau: fix another off-by-one in nvbios_addr
  drm/amdgpu: Check BO's requested pinning domains against its preferred_domains
  iio: light: isl29028: Fix the warning in isl29028_remove()
  fuse: limit nsec
  serial: mvebu-uart: uart2 error bits clearing
  md-raid10: fix KASAN warning
  ia64, processor: fix -Wincompatible-pointer-types in ia64_get_irr()
  PCI: Add defines for normal and subtractive PCI bridges
  powerpc/fsl-pci: Fix Class Code of PCIe Root Port
  powerpc/ptdump: Fix display of RW pages on FSL_BOOK3E
  powerpc/powernv: Avoid crashing if rng is NULL
  MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
  coresight: Clear the connection field properly
  USB: HCD: Fix URB giveback issue in tasklet function
  ARM: dts: uniphier: Fix USB interrupts for PXs2 SoC
  arm64: dts: uniphier: Fix USB interrupts for PXs3 SoC
  netfilter: nf_tables: fix null deref due to zeroed list head
  epoll: autoremove wakers even more aggressively
  x86: Handle idle=nomwait cmdline properly for x86_idle
  arm64: Do not forget syscall when starting a new thread.
  arm64: fix oops in concurrently setting insn_emulation sysctls
  ext2: Add more validity checks for inode counts
  genirq: Don't return error on missing optional irq_request_resources()
  wait: Fix __wait_event_hrtimeout for RT/DL tasks
  ARM: dts: imx6ul: add missing properties for sram
  ARM: dts: imx6ul: change operating-points to uint32-matrix
  ARM: dts: imx6ul: fix csi node compatible
  ARM: dts: imx6ul: fix lcdif node compatible
  ARM: dts: imx6ul: fix qspi node compatible
  spi: synquacer: Add missing clk_disable_unprepare()
  ARM: OMAP2+: display: Fix refcount leak bug
  ACPI: EC: Remove duplicate ThinkPad X1 Carbon 6th entry from DMI quirks
  ACPI: PM: save NVS memory for Lenovo G40-45
  ACPI: LPSS: Fix missing check in register_device_clock()
  arm64: dts: qcom: 

[Kernel-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes

[James Lewis]

Sorry, this answer has confused me even more... heres an example of what
we're currently using, perhaps you can speak to that,,, the user in this
case has no special rights, certainly not cap_sys_admin.

james@trinity:~$ grep james /etc/subuid
james:10:65536
james@trinity:~$ ls -asl .local/share/lxc/2004test/rootfs/ | head -8
total 68
4 drwxr-xr-x 17 10 10 4096 Aug 14  2020 .
4 drwxrwx---  3 10 james  4096 Aug 14  2020 ..
0 lrwxrwxrwx  1 10 107 Aug 14  2020 bin -> usr/bin
4 drwxr-xr-x  2 10 10 4096 Apr 15  2020 boot
4 drwxr-xr-x  3 10 10 4096 Aug 14  2020 dev
4 drwxr-xr-x 70 10 10 4096 Aug 14  2020 etc
4 drwxr-xr-x  3 10 10 4096 Aug 14  2020 home


james@trinity:~$ whoami
james
james@trinity:~$ lxc-start -n 2004test
james@trinity:~$ lxc-attach -n 2004test
root@2004test:/# exit
exit
james@trinity:~$ lxc-stop -n 2004test
james@trinity:~$

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

Title:
  unconfined profile denies userns_create for chromium based processes

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

Bug description:
  For Ubuntu 22.10, since the last kernel update, i can´t launch any
  chromium based browser, due to apparmor denying userns_create

  dmesg shows:
  apparmor="DENIED" operation="userns_create" class="namespace" info="User 
namespace creation restricted" error=-13 profile="unconfined" pid=21323 
comm="steamwebhelper" requested="userns_create" denied="userns_create"

  This happens for every process which uses a chromium engine, like
  google chrome itself or in this case steamwebhelper.

  Might be related to this change?:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/

  not sure if it got merged in this form though..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1990064] Re: unconfined profile denies userns_create for chromium based processes

[James Lewis]

I'm still trying to understand the exact implications of this, since I
make extensive use of LXC containers, using subuid/subgid mapping, so
that users can create containers without needing access to UID 0.

Are we talking about blocking namespaces where UID 0 in the container is
mapped to the real UID 0, or will it also impact containers where UID 0
in the container is mapped to some other UID.

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

Title:
  unconfined profile denies userns_create for chromium based processes

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

Bug description:
  For Ubuntu 22.10, since the last kernel update, i can´t launch any
  chromium based browser, due to apparmor denying userns_create

  dmesg shows:
  apparmor="DENIED" operation="userns_create" class="namespace" info="User 
namespace creation restricted" error=-13 profile="unconfined" pid=21323 
comm="steamwebhelper" requested="userns_create" denied="userns_create"

  This happens for every process which uses a chromium engine, like
  google chrome itself or in this case steamwebhelper.

  Might be related to this change?:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/

  not sure if it got merged in this form though..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1990618] Re: PXE Boot - errors in dhclient-script

[James Verbunk]

I can not boot into the full environment to collect logs.

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

Title:
  PXE Boot - errors in dhclient-script

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting 22.04.1 using ISO pulled vmlinuz/initrd/squashfs there
  are some errors in /sbin/dhclient-script. IDs redacted.

  
  Internet Systems Consortium DHCP Client 4.4.1
  Copyright 2004-2018 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/eno1/f0:92:~:~:~:~
  Sending on   LPF/eno1/f0:92:~:~:~:~
  Sending on   Socket/fallback
  DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 3 (xid=0xa9d4e16d)
  DHCPOFFER of 10.0.~.~ from 10.0.~.1
  DHCPREQUEST for 10.0.~.~ on eno1 to 255.255.255.255 port 67 (xid=0x6de1d4a9)
  DHCPACK of 10.0.~.~ from 10.0.~.1 (xid=0xa9d4e16d)
  /sbin/dhclient-script: line 99: chown: not found
  chmod: unrecognized option '--reference=/etc/resolv.conf'
  BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) multi-call binary.

  Usage: chmod [-R] MODE[,MODE]... FILE...

  Each MODE is one or more of the letters ugoa, one of the
  symbols +-= and one or more of the letters rwxst

-R  Recurse
  bound to 10.0.~.~ -- renewal in 2963 seconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990618/+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 1990621] [NEW] PXE Boot contains wrong suggested link to ISO for live file system

[James Verbunk]

Public bug reported:

When PXE booting without pulling in squashfs correctly the system tried
to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a
link to the old version which is not present anymore.

---
Unable to find a medium containing a live file system
Attempt interactive netboot from a URL?
yes no (default yes): 
Two methods available for IP configuration:
  * static: for static IP configuration
  * dhcp: for automatic IP configuration
static dhcp (default 'dhcp'): 
vlan id (optional): 
 https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default)
 https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso
url: 
http_proxy (optional): 
[  125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: RX/TX
[  125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount 
https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... 

BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443)
wget: server returned error: HTTP/1.1 404 Not Found
done.
Unable to find a medium containing a live file system

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

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

Title:
  PXE Boot contains wrong suggested link to ISO for live file system

Status in linux package in Ubuntu:
  New

Bug description:
  When PXE booting without pulling in squashfs correctly the system
  tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release
  contains a link to the old version which is not present anymore.

  ---
  Unable to find a medium containing a live file system
  Attempt interactive netboot from a URL?
  yes no (default yes): 
  Two methods available for IP configuration:
* static: for static IP configuration
* dhcp: for automatic IP configuration
  static dhcp (default 'dhcp'): 
  vlan id (optional): 
   https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso 
(default)
   https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso
  url: 
  http_proxy (optional): 
  [  125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: RX/TX
  [  125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
  Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount 
https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... 

  BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443)
  wget: server returned error: HTTP/1.1 404 Not Found
  done.
  Unable to find a medium containing a live file system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990621/+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 1990618] [NEW] PXE Boot - errors in dhclient-script

[James Verbunk]

Public bug reported:

When booting 22.04.1 using ISO pulled vmlinuz/initrd/squashfs there are
some errors in /sbin/dhclient-script. IDs redacted.


Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eno1/f0:92:~:~:~:~
Sending on   LPF/eno1/f0:92:~:~:~:~
Sending on   Socket/fallback
DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 3 (xid=0xa9d4e16d)
DHCPOFFER of 10.0.~.~ from 10.0.~.1
DHCPREQUEST for 10.0.~.~ on eno1 to 255.255.255.255 port 67 (xid=0x6de1d4a9)
DHCPACK of 10.0.~.~ from 10.0.~.1 (xid=0xa9d4e16d)
/sbin/dhclient-script: line 99: chown: not found
chmod: unrecognized option '--reference=/etc/resolv.conf'
BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) multi-call binary.

Usage: chmod [-R] MODE[,MODE]... FILE...

Each MODE is one or more of the letters ugoa, one of the
symbols +-= and one or more of the letters rwxst

-R  Recurse
bound to 10.0.~.~ -- renewal in 2963 seconds.

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


** Tags: boot pxe

** Summary changed:

- PXE Boot 
+ PXE Boot - errors in dhclient-script

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

Title:
  PXE Boot - errors in dhclient-script

Status in linux package in Ubuntu:
  New

Bug description:
  When booting 22.04.1 using ISO pulled vmlinuz/initrd/squashfs there
  are some errors in /sbin/dhclient-script. IDs redacted.

  
  Internet Systems Consortium DHCP Client 4.4.1
  Copyright 2004-2018 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/eno1/f0:92:~:~:~:~
  Sending on   LPF/eno1/f0:92:~:~:~:~
  Sending on   Socket/fallback
  DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 3 (xid=0xa9d4e16d)
  DHCPOFFER of 10.0.~.~ from 10.0.~.1
  DHCPREQUEST for 10.0.~.~ on eno1 to 255.255.255.255 port 67 (xid=0x6de1d4a9)
  DHCPACK of 10.0.~.~ from 10.0.~.1 (xid=0xa9d4e16d)
  /sbin/dhclient-script: line 99: chown: not found
  chmod: unrecognized option '--reference=/etc/resolv.conf'
  BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) multi-call binary.

  Usage: chmod [-R] MODE[,MODE]... FILE...

  Each MODE is one or more of the letters ugoa, one of the
  symbols +-= and one or more of the letters rwxst

-R  Recurse
  bound to 10.0.~.~ -- renewal in 2963 seconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990618/+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 1990064] Re: unconfined profile denies userns_create for chromium based processes

[James Lewis]

NB, also broke Steam (from .deb).

Is there a link anywhere to some of this discussion, happy for security
to be improved, but I'd like to understand what is being disabled, and
what the specific issue is.

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

Title:
  unconfined profile denies userns_create for chromium based processes

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

Bug description:
  For Ubuntu 22.10, since the last kernel update, i can´t launch any
  chromium based browser, due to apparmor denying userns_create

  dmesg shows:
  apparmor="DENIED" operation="userns_create" class="namespace" info="User 
namespace creation restricted" error=-13 profile="unconfined" pid=21323 
comm="steamwebhelper" requested="userns_create" denied="userns_create"

  This happens for every process which uses a chromium engine, like
  google chrome itself or in this case steamwebhelper.

  Might be related to this change?:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/

  not sure if it got merged in this form though..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1990064] Re: unconfined profile denies userns_create for chromium based processes

[James Lewis]

It broke for me between 5.19.0-15 and 5.19.0-17, and breaks every
flatpak app I have installed.

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

Title:
  unconfined profile denies userns_create for chromium based processes

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

Bug description:
  For Ubuntu 22.10, since the last kernel update, i can´t launch any
  chromium based browser, due to apparmor denying userns_create

  dmesg shows:
  apparmor="DENIED" operation="userns_create" class="namespace" info="User 
namespace creation restricted" error=-13 profile="unconfined" pid=21323 
comm="steamwebhelper" requested="userns_create" denied="userns_create"

  This happens for every process which uses a chromium engine, like
  google chrome itself or in this case steamwebhelper.

  Might be related to this change?:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/

  not sure if it got merged in this form though..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs

[James Falcon]

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  NTP reload failure (unable to read library) on overlayfs

Status in cloud-init:
  Won't Fix
Status in apparmor package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-
  init/0.7.9-153-g16a7302f-0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

  Related bugs:
   * bug 1645644: cloud-init ntp not using expected servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1002952] Re: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards

[James Budarz]

This issue also exists for "Yeti Stereo Microphone" and "HD Pro Webcam
C920".

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

Title:
  [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards

Status in alsa-lib package in Ubuntu:
  Confirmed

Bug description:
  === Read me first ===

  = Symptom =

  If you have a USB headset, or other USB device that does not have any
  S/PDIF output, but yet sometimes there is an extra device called
  "Digital Output (S/PDIF)" for that device, you're suffering from this
  bug.

  This bug is only for USB devices - if you have an invalid digital
  output for some other type of device, please file a separate bug
  instead.

  = Workaround =

  If you're affected, please try this workaround:

  first check the output of "aplay -l" (lowercase L), or "arecord -l" if
  it's an input device, and grab the first of two name in brackets:

  Example:
  card 3: Headset [Sennheiser USB Headset], device 0: USB Audio [USB Audio]
  here grab the name "Sennheiser USB Headset". Now edit the file 
/usr/share/alsa/cards/USB-Audio.conf (requires root permissions)
  Around line 40, you will find a line saying "Logitech USB Headset" 999
  Add a new line after this line, so that there is now a new line called
  "Sennheiser USB Headset" 999
  (including quotes, and replace "Sennheiser USB Headset" with whatever your 
particular card was named.)

  Save the file and reboot your computer for the changes to take effect.

  = Already known devices =

  These card names are already in 12.04:

  "Blue Snowball"
  "Logitech USB Headset"
  "Logitech Web Camera"

  These card names are on their way into 12.04:

  "Logitech Speaker Lapdesk N700"
  "Logitech Wireless Headset"
  "Plantronics USB Headset"
  "Sennheiser USB headset"

  If you have one of the above four, please help out by testing the
  proposed repository and report back in bug 987163.

  If your name is not listed above, please add a comment to this bug,
  including your alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo -
  they will be collected for a SRU later on, or at least make it into
  the next release of Ubuntu.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1002952/+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 1983787] Re: USB hub only works in USB2 ports

[James Lanham]

I booted into kernel 5.13.0-051300-generic and see no change in
behavior.

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

Title:
  USB hub only works in USB2 ports

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

Bug description:
  I have an IOGear GUS404 USB hub/switch
  (https://www.iogear.com/product/GUS404/), which works only when
  plugged into a USB2.0 port. When plugged into a USB3.0 port, none of
  the attached peripherals work. The attached peripherals are:

  1) Corsair Vengeance K70 RGB Keyboard
  (https://www.corsair.com/us/en/Categories/Products/Gaming-
  Keyboards/Vengeance%C2%AE-K70-RGB-%28Limited-Edition%29-Mechanical-
  Gaming-Keyboard-%E2%80%94-CHERRY%C2%AE-MX-Brown/p/CH-993-NA)

  2) Logitech G9x Mouse
  (https://www.newegg.com/logitech-g9x/p/N82E16826104261)

  3) Logitech C922 Webcam
  (https://www.bestbuy.com/site/logitech-c922-pro-stream-1080-webcam-
  for-hd-video-streaming-black/5579380.p?skuId=5579380)

  Ubuntu release: 
  ~$ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Aug  7 15:57:21 2022
  InstallationDate: Installed on 2022-06-11 (57 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1983787/+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 1915175] Re: wifi network stops working and shows a green wifi icon

[James Beale]

I am seeing something similar in 20.04 LTS on a laptop, HP EliteBook 840
G4.

According to this post, it may be a kernel thing, and also affecting
22.04 LTS:

https://askubuntu.com/questions/1403954/wifi-issues-in-ubuntu-22-04lts

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

Title:
  wifi network stops working and shows a green wifi icon

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently started using ubuntu 20.04, I connected it to my 2.4ghz Wi-Fi, at 
first the wifi worked fine, but suddenly the wifi stopped connecting, and after 
a few seconds it said "unable to activate network". I checked the "additional 
drivers tab" and it showed my wifi adapter, but it said "this device is using 
an alternate driver".
  right now I'm using my 5ghz Wi-Fi network, but sometimes it happens that it 
stops working, usually after suspend.

  UPDATE #1: Apparently it's working now, I suppose it's from an update.
  Anyways I guess it's fixed.

  UPDATE #2: it's broken again

  UPDATE #3: after checking the error a long time I've realized that
  this error happens when I leave it suspended it for a long time, it is
  fixed by doing about 3-4 restarts. I'm going to try to use a code that
  restarts the network-service after suspend, I'll see if it works.

  UPDATE #4 (probably final update): the error can be fixed temporarily
  by turning off and then on the router,i'm going to contact my network
  provider to see if the error can be fixed by configuring the router.

  UPDATE #5: after upgrading to Groovy the issue still persists, I
  really hope this can be fixed, I don't want to have to move to another
  distro

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.2
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  9 12:09:28 2021
  InstallationDate: Installed on 2021-02-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  IpRoute:
   default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp1s0 scope link metric 1000
   192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.8 metric 600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2021-02-08T22:50:26.196692
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION   CON-UUID
  CON-PATH
   wlp1s0  wifi  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Betancur 5G  
cda009c8-c845-4366-8436-8e9c44da2cbf  
/org/freedesktop/NetworkManager/ActiveConnection/1
   lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gustavo1035 F pulseaudio
   /dev/snd/controlC0:  gustavo1035 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-08 (6 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X509DA_M509DA
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=ded079f2-3f25-4b66-9496-ffb73191187f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-43-generic N/A
   linux-backports-modules-5.8.0-43-generic  N/A
   linux-firmware1.187.9
  Tags:  focal
  Uname: Linux 5.8.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/11/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X509DA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X509DA
  

[Kernel-packages] [Bug 1892074] Re: Intel Killer AX1650i [8086:34f0] Subsystem [1a56:1651] WiFi keeps disconnecting

[James Beale]

I am seeing something similar in 20.04 LTS on a laptop, HP EliteBook 840
G4.

According to this post, it may be a kernel thing, and also affecting
22.04 LTS:

https://askubuntu.com/questions/1403954/wifi-issues-in-ubuntu-22-04lts

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

Title:
  Intel Killer AX1650i [8086:34f0] Subsystem [1a56:1651] WiFi keeps
  disconnecting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  2) $ apt-cache policy linux-image-5.4.0-42-generic
  linux-image-5.4.0-42-generic:
Installed: 5.4.0-42.46
Candidate: 5.4.0-42.46
Version table:
   *** 5.4.0-42.46 500
  500 http://at.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) No WiFi disconnects
  4) WiFi disconnects (other clients don't have any issues)

  The WiFi AP is a Mikrotik cAP AC running RouterOS v6.47.1, 2.4/5GHz
  dual-band (4 channels), WPA2-PSK.

  I see reglular WiFi disconnects since a few days now, possibly related
  to a kernel and/or firmware upgrade.

  https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1889182
  looks similar, but I have different Intel hardware:

  00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i
  160MHz Wireless Network Adapter (201NGW) (rev 30)

  [87471.950797] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [87471.950881] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [87471.950884] iwlwifi :00:14.3: Status: 0x0040, count: 6
  [87471.950887] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0
  [87471.950889] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [87471.950891] iwlwifi :00:14.3: 0xA200 | trm_hw_status0
  [87471.950893] iwlwifi :00:14.3: 0x | trm_hw_status1
  [87471.950895] iwlwifi :00:14.3: 0x004CA468 | branchlink2
  [87471.950897] iwlwifi :00:14.3: 0x004B5438 | interruptlink1
  [87471.950898] iwlwifi :00:14.3: 0x004B5438 | interruptlink2
  [87471.950900] iwlwifi :00:14.3: 0x004C54E6 | data1
  [87471.950902] iwlwifi :00:14.3: 0x1000 | data2
  [87471.950903] iwlwifi :00:14.3: 0xF008 | data3
  [87471.950905] iwlwifi :00:14.3: 0x8580BFB0 | beacon time
  [87471.950907] iwlwifi :00:14.3: 0xF6D4B028 | tsf low
  [87471.950909] iwlwifi :00:14.3: 0x0013 | tsf hi
  [87471.950910] iwlwifi :00:14.3: 0x | time gp1
  [87471.950912] iwlwifi :00:14.3: 0x03470D2D | time gp2
  [87471.950914] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [87471.950915] iwlwifi :00:14.3: 0x0030 | uCode version major
  [87471.950917] iwlwifi :00:14.3: 0x4FA0041F | uCode version minor
  [87471.950919] iwlwifi :00:14.3: 0x0332 | hw version
  [87471.950921] iwlwifi :00:14.3: 0x00C89008 | board version
  [87471.950922] iwlwifi :00:14.3: 0x8028FD19 | hcmd
  [87471.950924] iwlwifi :00:14.3: 0x2402 | isr0
  [87471.950926] iwlwifi :00:14.3: 0x | isr1
  [87471.950927] iwlwifi :00:14.3: 0x18F84802 | isr2
  [87471.950929] iwlwifi :00:14.3: 0x00C1FFCC | isr3
  [87471.950931] iwlwifi :00:14.3: 0x | isr4
  [87471.950932] iwlwifi :00:14.3: 0x009D01D1 | last cmd Id
  [87471.950934] iwlwifi :00:14.3: 0x004C54E6 | wait_event
  [87471.950936] iwlwifi :00:14.3: 0x00D4 | l2p_control
  [87471.950938] iwlwifi :00:14.3: 0x00018014 | l2p_duration
  [87471.950939] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid
  [87471.950941] iwlwifi :00:14.3: 0x | l2p_addr_match
  [87471.950943] iwlwifi :00:14.3: 0x0008 | lmpm_pmg_sel
  [87471.950944] iwlwifi :00:14.3: 0x | timestamp
  [87471.950946] iwlwifi :00:14.3: 0x988C | flow_handler
  [87471.950984] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [87471.950986] iwlwifi :00:14.3: Status: 0x0040, count: 7
  [87471.950988] iwlwifi :00:14.3: 0x200014FD | ADVANCED_SYSASSERT
  [87471.950989] iwlwifi :00:14.3: 0x | umac branchlink1
  [87471.950991] iwlwifi :00:14.3: 0xC008D49C | umac branchlink2
  [87471.950993] iwlwifi :00:14.3: 0xC00871A4 | umac interruptlink1
  [87471.950995] iwlwifi :00:14.3: 0x | umac interruptlink2
  [87471.950996] iwlwifi :00:14.3: 0x0082 | umac data1
  [87471.950998] iwlwifi :00:14.3: 0xDEADBEEF | umac data2
  [87471.951000] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [87471.951001] iwlwifi :00:14.3: 0x0030 | umac major
  [87471.951003] iwlwifi :00:14.3: 0x4FA0041F | umac minor
  [87471.951005] iwlwifi :00:14.3: 0x03470D20 | frame pointer
  [87471.951006] iwlwifi :00:14.3: 0xC0885EA0 | stack pointer
  [87471.951008] iwlwifi 

[Kernel-packages] [Bug 1983787] Re: USB hub only works in USB2 ports

[James Lanham]

Here is the full dmesg log during my fooling around.

** Attachment added: "dmesg-full.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1983787/+attachment/5607363/+files/dmesg-full.txt

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

Title:
  USB hub only works in USB2 ports

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

Bug description:
  I have an IOGear GUS404 USB hub/switch
  (https://www.iogear.com/product/GUS404/), which works only when
  plugged into a USB2.0 port. When plugged into a USB3.0 port, none of
  the attached peripherals work. The attached peripherals are:

  1) Corsair Vengeance K70 RGB Keyboard
  (https://www.corsair.com/us/en/Categories/Products/Gaming-
  Keyboards/Vengeance%C2%AE-K70-RGB-%28Limited-Edition%29-Mechanical-
  Gaming-Keyboard-%E2%80%94-CHERRY%C2%AE-MX-Brown/p/CH-993-NA)

  2) Logitech G9x Mouse
  (https://www.newegg.com/logitech-g9x/p/N82E16826104261)

  3) Logitech C922 Webcam
  (https://www.bestbuy.com/site/logitech-c922-pro-stream-1080-webcam-
  for-hd-video-streaming-black/5579380.p?skuId=5579380)

  Ubuntu release: 
  ~$ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Aug  7 15:57:21 2022
  InstallationDate: Installed on 2022-06-11 (57 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1983787/+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 1983787] Re: USB hub only works in USB2 ports

[James Lanham]

Agreed that loading an older kernel might give some interesting info,
but it might not be until later this week that I can re-image my machine
and get that to you. In the meantime, here is the dmesg info, and my
observations:

At 219.322795, I disconnect from the USB2 port, plug into USB3 at 220.959698, 
and an interesting error appears at 224.531221: 
[  224.531221] usb 8-2.2: Not enough bandwidth for new device state.
[  224.531226] usb 8-2.2: can't set config #1, error -28

This is just after it tries to load the mouse, but the same error appears when 
it detects the keybaord as well. 
I did some experimenting, and it turns out if I ONLY plug the webcam into the 
hub, then it works fine in both port types. But if I ONLY plug in a standard 
plain office keyboard, then it again works only in USB2 ports. It's as if USB3 
ports don't like non 'high-speed' devices plugged into the hub. 

Here is the log from when I only have the plain office keybaord plugged into 
the hub -> USB2:
[  921.131359] usb 1-5.2: new low-speed USB device number 19 using ehci-pci
[  921.378603] usb 1-5.2: New USB device found, idVendor=03f0, idProduct=034a, 
bcdDevice= 1.21
[  921.378610] usb 1-5.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[  921.378612] usb 1-5.2: Product: HP Elite USB Keyboard
[  921.378614] usb 1-5.2: Manufacturer: Chicony
[  921.387895] input: Chicony HP Elite USB Keyboard as 
/devices/pci:00/:00:12.2/usb1/1-5/1-5.2/1-5.2:1.0/0003:03F0:034A.000E/input/input39
[  921.447589] hid-generic 0003:03F0:034A.000E: input,hidraw0: USB HID v1.10 
Keyboard [Chicony HP Elite USB Keyboard] on usb-:00:12.2-5.2/input0
[  921.454660] input: Chicony HP Elite USB Keyboard System Control as 
/devices/pci:00/:00:12.2/usb1/1-5/1-5.2/1-5.2:1.1/0003:03F0:034A.000F/input/input40
[  921.511524] input: Chicony HP Elite USB Keyboard Consumer Control as 
/devices/pci:00/:00:12.2/usb1/1-5/1-5.2/1-5.2:1.1/0003:03F0:034A.000F/input/input41
[  921.511621] hid-generic 0003:03F0:034A.000F: input,hidraw1: USB HID v1.10 
Device [Chicony HP Elite USB Keyboard] on usb-:00:12.2-5.2/input1

And the same for USB3:
[  892.290826] usb 8-2.2: new low-speed USB device number 10 using xhci_hcd
[  892.554392] usb 8-2.2: New USB device found, idVendor=03f0, idProduct=034a, 
bcdDevice= 1.21
[  892.554397] usb 8-2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[  892.554400] usb 8-2.2: Product: HP Elite USB Keyboard
[  892.554401] usb 8-2.2: Manufacturer: Chicony
[  892.554542] usb 8-2.2: Not enough bandwidth for new device state.
[  892.554548] usb 8-2.2: can't set config #1, error -28

I'll include what you requested as dmesg.txt, but everything, including
my experimenting with multiple unplugs/replugs, is in dmesg-full.txt

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1983787/+attachment/5607362/+files/dmesg.txt

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

Title:
  USB hub only works in USB2 ports

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

Bug description:
  I have an IOGear GUS404 USB hub/switch
  (https://www.iogear.com/product/GUS404/), which works only when
  plugged into a USB2.0 port. When plugged into a USB3.0 port, none of
  the attached peripherals work. The attached peripherals are:

  1) Corsair Vengeance K70 RGB Keyboard
  (https://www.corsair.com/us/en/Categories/Products/Gaming-
  Keyboards/Vengeance%C2%AE-K70-RGB-%28Limited-Edition%29-Mechanical-
  Gaming-Keyboard-%E2%80%94-CHERRY%C2%AE-MX-Brown/p/CH-993-NA)

  2) Logitech G9x Mouse
  (https://www.newegg.com/logitech-g9x/p/N82E16826104261)

  3) Logitech C922 Webcam
  (https://www.bestbuy.com/site/logitech-c922-pro-stream-1080-webcam-
  for-hd-video-streaming-black/5579380.p?skuId=5579380)

  Ubuntu release: 
  ~$ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Aug  7 15:57:21 2022
  InstallationDate: Installed on 2022-06-11 (57 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1983787] [NEW] USB hub only works in USB2 ports

[James Lanham]

Public bug reported:

I have an IOGear GUS404 USB hub/switch
(https://www.iogear.com/product/GUS404/), which works only when plugged
into a USB2.0 port. When plugged into a USB3.0 port, none of the
attached peripherals work. The attached peripherals are:

1) Corsair Vengeance K70 RGB Keyboard
(https://www.corsair.com/us/en/Categories/Products/Gaming-
Keyboards/Vengeance%C2%AE-K70-RGB-%28Limited-Edition%29-Mechanical-
Gaming-Keyboard-%E2%80%94-CHERRY%C2%AE-MX-Brown/p/CH-993-NA)

2) Logitech G9x Mouse
(https://www.newegg.com/logitech-g9x/p/N82E16826104261)

3) Logitech C922 Webcam (https://www.bestbuy.com/site/logitech-c922-pro-
stream-1080-webcam-for-hd-video-streaming-black/5579380.p?skuId=5579380)

Ubuntu release: 
~$ lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Sun Aug  7 15:57:21 2022
InstallationDate: Installed on 2022-06-11 (57 days ago)
InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.15
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  USB hub only works in USB2 ports

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

Bug description:
  I have an IOGear GUS404 USB hub/switch
  (https://www.iogear.com/product/GUS404/), which works only when
  plugged into a USB2.0 port. When plugged into a USB3.0 port, none of
  the attached peripherals work. The attached peripherals are:

  1) Corsair Vengeance K70 RGB Keyboard
  (https://www.corsair.com/us/en/Categories/Products/Gaming-
  Keyboards/Vengeance%C2%AE-K70-RGB-%28Limited-Edition%29-Mechanical-
  Gaming-Keyboard-%E2%80%94-CHERRY%C2%AE-MX-Brown/p/CH-993-NA)

  2) Logitech G9x Mouse
  (https://www.newegg.com/logitech-g9x/p/N82E16826104261)

  3) Logitech C922 Webcam
  (https://www.bestbuy.com/site/logitech-c922-pro-stream-1080-webcam-
  for-hd-video-streaming-black/5579380.p?skuId=5579380)

  Ubuntu release: 
  ~$ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Aug  7 15:57:21 2022
  InstallationDate: Installed on 2022-06-11 (57 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1983787/+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 1419439] Re: Screen freeze when watching video in VLC

[James Wilson]

You can also watch Netflix OTT platform without freezing your screen for
Latest shows you can visit
https://streamingpit.com/channels/netflix/july-2022-netflix-upcoming-
releases/

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

Title:
  Screen freeze when watching video in VLC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Screen freezes when I watch video in VLC media player. Moving mouse is
  of no use and Ctrl + Alt + T short cut does not launch terminal. But I
  Could hear the audio even after screen freeze.

  If I press Ctrl + Alt + F1 and wait for several minutes switches to
  console. Then switching to GUI brings back the screen and I am able to
  work as usual.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prasanna   2562 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb  8 18:51:57 2015
  HibernationDevice: RESUME=UUID=0af44a95-238c-498a-88f2-425c00e1c9a6
  InstallationDate: Installed on 2014-12-15 (54 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 24663C1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=0155df5a-b3ef-4cff-bf83-c45841ac9ed0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-30-generic N/A
   linux-backports-modules-3.16.0-30-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G3ET90WW(2.50)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24663C1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG3ET90WW(2.50):bd12/26/2012:svnLENOVO:pn24663C1:pvrThinkPadL430:rvnLENOVO:rn24663C1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 24663C1
  dmi.product.version: ThinkPad L430
  dmi.sys.vendor: LENOVO

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

[James Benkart]

I have similar lernel panics launching docker-ce instances on the google
cloud platform after recent ubuntu update, 20.04 LTS. 22.04 is
unaffected.

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

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

Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed

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 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.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246
  [   12.610166] RAX:  RBX: 000a801d RCX: 
9152e0716000
  [   12.615417] RDX: 9152cf075280 RSI: 0001 RDI: 

  [   12.620635] RBP: b50280d9fdb0 R08: 0001 R09: 
9152dfcba2c8
  [   12.625878] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 
9152d04e9d00
  [   12.631121] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 
9152dfc2e180
  [   12.636358] FS:  () GS:9153ea90() 
knlGS:
  [   12.643770] CS:  0010 DS: 

[Kernel-packages] [Bug 1962359] Re: Hibernation fails due to resource busy during swap file check

[James]

Same here.  I have 48GB Ram and 76GB swap partition.  Where did you see
the error code -16 is EBUSY?

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

Title:
  Hibernation fails due to resource busy during swap file check

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hopefully, the automatically collected information is useful. The
  issue manifests when I try to hibernate the device. I see the
  following in the logs:

  ~$ journalctl --no-hostname -b -1 | tail -6
  Feb 25 08:23:54 systemd[1]: nvidia-hibernate.service: Deactivated 
successfully.
  Feb 25 08:23:54 systemd[1]: Finished NVIDIA system hibernate actions.
  Feb 25 08:23:54 systemd[1]: Starting Hibernate...
  Feb 25 08:23:54 kernel: PM: Image not found (code -16)
  Feb 25 08:23:54 systemd-sleep[50360]: Entering sleep state 'hibernate'...
  Feb 25 08:23:54 kernel: PM: hibernation: hibernation entry

  I looked up error code 16 as EBUSY. This happens when using pm-
  hibernate or "systemctl hibernate". I played qaround with the nvidia
  systemd hibernate units but it didn't help.

  Hibernate used to work before I upgraded to jammy. I was on focal and
  bionic before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-18-generic 5.15.0-18.18
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 26 09:27:29 2022
  InstallationDate: Installed on 2019-08-07 (933 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash 
resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220217.git6342082c-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: X399 AORUS XTREME-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X399 AORUS XTREME
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962359/+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 1960242] Re: [amdgpu] kernel fault on monitor wakeup, only reboot recovers.

[James Renken]

I've been encountering this problem with an RX 6600 using linux-
image-5.15.0-22-lowlatency and linux-image-5.15.0-23-generic on Jammy.
This had not been happening with linux-image-5.13.0-37-lowlatency on
Impish.

[78421.618570] INFO: task gnome-shell:2364 blocked for more than 241 seconds.
[78421.618575]   Not tainted 5.15.0-23-generic #23-Ubuntu
[78421.618577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[78421.618578] task:gnome-shell state:D stack:0 pid: 2364 ppid:  2194 
flags:0x4002
[78421.618581] Call Trace:
[78421.618583]  
[78421.618585]  __schedule+0x23d/0x590
[78421.618590]  schedule+0x4e/0xb0
[78421.618591]  schedule_preempt_disabled+0xe/0x10
[78421.618593]  __mutex_lock.constprop.0+0x263/0x490
[78421.618596]  __mutex_lock_slowpath+0x13/0x20
[78421.618597]  mutex_lock+0x34/0x40
[78421.618598]  amdgpu_dm_atomic_commit_tail+0x5a5/0x1430 [amdgpu]
[78421.618737]  ? dcn30_calculate_wm_and_dlg_fp+0x7b0/0xac0 [amdgpu]
[78421.618861]  ? hubbub3_get_dcc_compression_cap+0x92/0x2d0 [amdgpu]
[78421.618995]  ? dcn20_get_dcc_compression_cap+0x23/0x30 [amdgpu]
[78421.619126]  ? fill_gfx9_plane_attributes_from_modifiers+0x217/0x2e0 [amdgpu]
[78421.619240]  ? dcn30_validate_bandwidth+0x1a0/0x340 [amdgpu]
[78421.619355]  ? ttm_bo_mem_compat+0x30/0x90 [ttm]
[78421.619359]  ? fill_plane_buffer_attributes+0x137/0x290 [amdgpu]
[78421.619470]  ? __cond_resched+0x1a/0x50
[78421.619472]  ? __wait_for_common+0x3e/0x150
[78421.619474]  ? dm_plane_helper_prepare_fb+0x236/0x290 [amdgpu]
[78421.619579]  ? usleep_range_state+0x90/0x90
[78421.619581]  ? wait_for_completion_timeout+0x1d/0x20
[78421.619583]  commit_tail+0xc5/0x170 [drm_kms_helper]
[78421.619593]  ? drm_atomic_helper_swap_state+0x246/0x370 [drm_kms_helper]
[78421.619601]  drm_atomic_helper_commit+0x123/0x150 [drm_kms_helper]
[78421.619608]  drm_atomic_commit+0x4a/0x50 [drm]
[78421.619623]  drm_mode_atomic_ioctl+0x530/0x740 [drm]
[78421.619636]  ? drm_plane_create_color_properties.cold+0x48/0x48 [drm]
[78421.619650]  ? drm_atomic_set_property+0x150/0x150 [drm]
[78421.619661]  drm_ioctl_kernel+0xae/0xf0 [drm]
[78421.619673]  drm_ioctl+0x264/0x4b0 [drm]
[78421.619683]  ? drm_atomic_set_property+0x150/0x150 [drm]
[78421.619695]  ? recalibrate_cpu_khz+0x10/0x10
[78421.619697]  ? ktime_get_mono_fast_ns+0x52/0xa0
[78421.619699]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
[78421.619770]  __x64_sys_ioctl+0x91/0xc0
[78421.619773]  do_syscall_64+0x5c/0xc0
[78421.619776]  ? syscall_exit_to_user_mode+0x27/0x50
[78421.619777]  ? do_syscall_64+0x69/0xc0
[78421.619778]  ? syscall_exit_to_user_mode+0x27/0x50
[78421.619779]  ? do_syscall_64+0x69/0xc0
[78421.619781]  ? do_syscall_64+0x69/0xc0
[78421.619782]  ? do_syscall_64+0x69/0xc0
[78421.619783]  ? irqentry_exit_to_user_mode+0x9/0x20
[78421.619784]  ? irqentry_exit+0x19/0x30
[78421.619785]  ? sysvec_apic_timer_interrupt+0x4e/0x90
[78421.619786]  ? asm_sysvec_apic_timer_interrupt+0xa/0x20
[78421.619788]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[78421.619789] RIP: 0033:0x7fd826692aff
[78421.619791] RSP: 002b:7ffed2c1a150 EFLAGS: 0246 ORIG_RAX: 
0010
[78421.619793] RAX: ffda RBX: 7ffed2c1a1f0 RCX: 7fd826692aff
[78421.619794] RDX: 7ffed2c1a1f0 RSI: c03864bc RDI: 0009
[78421.619794] RBP: c03864bc R08: 000f R09: 000f
[78421.619795] R10: 0007 R11: 0246 R12: 561f321406c0
[78421.619796] R13: 0009 R14: 561f33630420 R15: 561f349c6660
[78421.619797]  
[78421.619966] INFO: task kworker/4:1:96189 blocked for more than 241 seconds.
[78421.619968]   Not tainted 5.15.0-23-generic #23-Ubuntu
[78421.619969] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[78421.619970] task:kworker/4:1 state:D stack:0 pid:96189 ppid: 2 
flags:0x4000
[78421.619972] Workqueue: events drm_sched_job_timedout [gpu_sched]
[78421.619976] Call Trace:
[78421.619977]  
[78421.619977]  __schedule+0x23d/0x590
[78421.619980]  schedule+0x4e/0xb0
[78421.619981]  schedule_preempt_disabled+0xe/0x10
[78421.619983]  __mutex_lock.constprop.0+0x263/0x490
[78421.619985]  __mutex_lock_slowpath+0x13/0x20
[78421.619986]  mutex_lock+0x34/0x40
[78421.619987]  dm_suspend+0xaa/0x270 [amdgpu]
[78421.620118]  ? nv_common_set_clockgating_state+0x9f/0xb0 [amdgpu]
[78421.620201]  ? amdgpu_device_set_cg_state+0x12f/0x280 [amdgpu]
[78421.620274]  amdgpu_device_ip_suspend_phase1+0xa7/0x190 [amdgpu]
[78421.620345]  amdgpu_device_ip_suspend+0x21/0x70 [amdgpu]
[78421.620415]  amdgpu_device_pre_asic_reset+0xdd/0x480 [amdgpu]
[78421.620485]  ? drm_fb_helper_set_suspend_unlocked+0x33/0xa0 [drm_kms_helper]
[78421.620493]  amdgpu_device_gpu_recover.cold+0x6ec/0x8f8 [amdgpu]
[78421.620621]  amdgpu_job_timedout+0x14f/0x170 [amdgpu]
[78421.620722]  drm_sched_job_timedout+0x6f/0x110 [gpu_sched]
[78421.620724]  process_one_work+0x22b/0x3d0
[78421.620727]  worker_thread+0x53/0x410

[Kernel-packages] [Bug 1966793] [NEW] Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

[James Campbell]

Public bug reported:

This problem exists on an HP ProBook 440 G8
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04


Wifi Adapter information :
   description: Wireless interface
   product: Wi-Fi 6 AX201
   vendor: Intel Corporation
   physical id: 14.3
   bus info: pci@:00:14.3
   logical name: wlp0s20f3
   version: 20
   serial: 28:d0:ea:21:6a:a1
   width: 64 bits
   clock: 33MHz
   capabilities: bus_master cap_list ethernet physical wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=5.15.0-23-generic firmware=66.f1c864e0.0 QuZ-a0-jf-b0-66.u 
latency=0 link=no multicast=yes wireless=IEEE 802.11
   resources: iomemory:600-5ff irq:16 memory:600324c000-600324

Error Information:
[   60.882505] CPU: 6 PID: 630 Comm: wpa_supplicant Not tainted 
5.15.0-23-generic #23-Ubuntu
[   60.882512] Hardware name: HP HP ProBook 440 G8 Notebook PC/8807, BIOS T85 
Ver. 01.06.03 08/26/2021
[   60.882514] Call Trace:
[   60.882517]  
[   60.882521]  show_stack+0x52/0x58
[   60.882532]  dump_stack_lvl+0x4a/0x5f
[   60.882541]  dump_stack+0x10/0x12
[   60.882545]  iwl_trans_txq_send_hcmd_sync+0x345/0x350 [iwlwifi]
[   60.882582]  ? wait_woken+0x70/0x70
[   60.882589]  iwl_trans_txq_send_hcmd+0xaa/0x140 [iwlwifi]
[   60.882619]  iwl_trans_send_cmd+0x84/0x110 [iwlwifi]
[   60.882646]  iwl_mvm_send_cmd_pdu+0x6d/0xc0 [iwlmvm]
[   60.882675]  iwl_mvm_ppag_send_cmd+0x1b5/0x270 [iwlmvm]
[   60.882695]  iwl_mvm_up+0x656/0xa80 [iwlmvm]
[   60.882716]  ? __iwl_err.cold+0x25/0x2a [iwlwifi]
[   60.882755]  __iwl_mvm_mac_start+0x2b/0x1a0 [iwlmvm]
[   60.882777]  iwl_mvm_mac_start+0x5f/0xc0 [iwlmvm]
[   60.882799]  drv_start+0x4f/0xe0 [mac80211]
[   60.882858]  ieee80211_do_open+0x488/0x9c0 [mac80211]
[   60.882926]  ? ieee80211_check_concurrent_iface+0x158/0x1c0 [mac80211]
[   60.882987]  ieee80211_open+0x6c/0x90 [mac80211]
[   60.883048]  __dev_open+0xf0/0x1c0
[   60.883054]  __dev_change_flags+0x1a3/0x220
[   60.883058]  dev_change_flags+0x26/0x60
[   60.883061]  devinet_ioctl+0x598/0x6f0
[   60.883068]  ? netdev_name_node_lookup_rcu+0x6b/0x80
[   60.883075]  ? _copy_from_user+0x2e/0x60
[   60.883082]  inet_ioctl+0x165/0x190
[   60.883088]  sock_do_ioctl+0x42/0x100
[   60.883093]  ? do_readlinkat+0x10f/0x120
[   60.883099]  sock_ioctl+0xef/0x310
[   60.883103]  ? do_syscall_64+0x69/0xc0
[   60.883110]  __x64_sys_ioctl+0x91/0xc0
[   60.883116]  do_syscall_64+0x59/0xc0
[   60.883120]  ? do_syscall_64+0x69/0xc0
[   60.883125]  ? do_syscall_64+0x69/0xc0
[   60.883129]  ? syscall_exit_to_user_mode+0x27/0x50
[   60.883133]  ? __x64_sys_readlink+0x1e/0x30
[   60.883137]  ? do_syscall_64+0x69/0xc0
[   60.883142]  ? do_syscall_64+0x69/0xc0
[   60.883147]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   60.883152] RIP: 0033:0x7f66c7592aff
[   60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 
00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 
3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00
[   60.883162] RSP: 002b:7ffc168507c0 EFLAGS: 0246 ORIG_RAX: 
0010
[   60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff
[   60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009
[   60.883174] RBP: 0009 R08:  R09: 55e021909e90
[   60.883176] R10: 0007 R11: 0246 R12: 55e02190e028
[   60.883178] R13:  R14: 7ffc16850820 R15: 0005
[   60.883182]  
[   60.883206] iwlwifi :00:14.3: failed to send PER_PLATFORM_ANT_GAIN_CMD 
(-5)
[   60.894910] iwlwifi :00:14.3: mac start retry 1
[   61.068762] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
[   61.068863] iwlwifi :00:14.3: Start IWL Error Log Dump:
[   61.068866] iwlwifi :00:14.3: Transport status: 0x004B, valid: 6
[   61.068871] iwlwifi :00:14.3: Loaded firmware version: 66.f1c864e0.0 
QuZ-a0-jf-b0-66.ucode
[   61.068874] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
[   61.068878] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0
[   61.068881] iwlwifi :00:14.3: 0x | trm_hw_status1
[   61.068883] iwlwifi :00:14.3: 0x004C2726 | branchlink2
[   61.068886] iwlwifi :00:14.3: 0x004B974E | interruptlink1
[   61.068889] iwlwifi :00:14.3: 0x004B974E | interruptlink2
[   61.068891] iwlwifi :00:14.3: 0x004BD86E | data1
[   61.068893] iwlwifi :00:14.3: 0x1000 | data2
[   61.068896] iwlwifi :00:14.3: 0x | data3
[   61.068898] iwlwifi :00:14.3: 0x | beacon time
[   61.068901] iwlwifi :00:14.3: 0x000215F2 | tsf low
[   61.068903] iwlwifi :00:14.3: 0x | tsf hi
[   61.068906] iwlwifi :00:14.3: 0x | time gp1
[   61.068908] iwlwifi :00:14.3: 0x00026E8A | time gp2
[   61.068911] iwlwifi :00:14.3: 0x0001 | uCode revision type
[   61.068913] 

[Kernel-packages] [Bug 1966546] Re: Touchpad becomes unresponsive after resuming from sleep

[James Bashforth]

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model

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

[James Bashforth]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1966546/+attachment/5573191/+files/RfKill.txt

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish

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

[James Bashforth]

apport information

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish

[Kernel-packages] [Bug 1966546] IwConfig.txt

[James Bashforth]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1966546/+attachment/5573178/+files/IwConfig.txt

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish

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

[James Bashforth]

apport information

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy

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

[James Bashforth]

apport information

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish

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

[James Bashforth]

apport information

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "

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

[James Bashforth]

apport information

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish

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

[James Bashforth]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1966546/+attachment/5573182/+files/Lsusb-t.txt

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish

[Kernel-packages] [Bug 1966546] CRDA.txt

[James Bashforth]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1966546/+attachment/5573176/+files/CRDA.txt

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish

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

[James Bashforth]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1966546/+attachment/5573181/+files/Lsusb.txt

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish

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

[James Bashforth]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1966546/+attachment/5573184/+files/PaInfo.txt

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish

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

[James Bashforth]

apport information

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish

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

[James Bashforth]

apport information

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

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish

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

[James Bashforth]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1966546/+attachment/5573190/+files/PulseList.txt

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy

[Kernel-packages] [Bug 1966546] AlsaInfo.txt

[James Bashforth]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1966546/+attachment/5573175/+files/AlsaInfo.txt

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

Title:
  Touchpad becomes unresponsive after resuming from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.

  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish

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

[James Bashforth]

apport information

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

** Description changed:

  I have a Razer Blade Advanced 15 (Late 2021).  I'm running ubuntu 22.04 and 
it is working really well apart from after resuming from sleep.  Once resumed 
the touchpad seems to act erratically and is unusable.
  There is an error that appears on screen just before the login screen appears 
which seems to suggest that the touchpad has failed.
  
  13:52:54 kernel: ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
  13:52:54 kernel: thermal thermal_zone7: failed to read out thermal zone (-61)
  13:52:54 kernel: Restarting tasks ... done.
  13:52:54 kernel: OOM killer enabled.
  13:52:54 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
  13:52:54 kernel: [drm] DisplayID checksum invalid, remainder is 20
  13:52:54 kernel: usb 3-8: reset high-speed USB device number 5 using xhci_hcd
  13:52:54 kernel: nvme nvme0: 16/0/0 default/read/poll queues
  13:52:54 kernel: i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete 
report (14/65280)
  13:52:54 kernel: usb usb2: root hub lost power or was reset
  13:52:54 kernel: xhci_hcd :00:0d.0: xHC error in resume, USBSTS 0x401, 
Reinit
  13:52:54 kernel: ACPI: EC: event unblocked
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK 
(20210730/hwesleep-47)
  13:52:54 kernel: ACPI Error: Aborting method \_WAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \RWAK due to previous error 
(AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.RTEC due to 
previous error (AE_NOT_EXIST) (20210730/psparse-529)
  13:52:54 kernel: 
  13:52:54 kernel: No Arguments are initialized for method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: No Local Variables are initialized for Method [RTEC]
  13:52:54 kernel: 
  13:52:54 kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler 
(20210730/exfldio-261)
  13:52:54 kernel: ACPI: PM: Waking up from system sleep state S3
  13:52:54 kernel: CPU15 is up
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  1800 F pulseaudio
   /dev/snd/controlC0:  james  1800 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu79
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  james  1800 F pulseaudio
+  /dev/snd/controlC0:  james  1800 F pulseaudio
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-03-26 (0 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
+ MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
roo