[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!

[Laurent Bonnaud]

This bug is no longer present in kernel 6.8.0-22-generic from Ubuntu noble.
Thanks for 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/2037214

Title:
  evict_inodes inode xxx, i_count = 1, was skipped!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  during boot the kernel logs the following messages:

  # dmesg | grep evict_inodes
  [   12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
  [   12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
  [   12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
  [   12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
  [   12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!

  Those messages are not displayed when I boot my system with a mainline Linux 
kernel.
  Moreover, in the mainline Linux source code, I do not find the lines where 
such a message could be printed.

  Therefore, those messages are probably caused by an Ubuntu patch.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   4827 F wireplumber
   /dev/snd/seq:bonnaudl   4808 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 14:39:10 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off 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.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 1959384] Re: CONFIG_IO_STRICT_DEVMEM could be enabled

[Laurent Bonnaud]

In Ubuntu noble:

$ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
/boot/config-6.8.0-22-generic:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-6.8.0-7-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set


** Tags removed: kinetic lunar
** Tags added: noble

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

Title:
  CONFIG_IO_STRICT_DEVMEM could be enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace
  access of active io-memory ranges.

  This could impact kernel debugability. In that case, you may reboot with
  iomem=relaxed on the kernel command line to override this setting.

  This config option is recommended by the Kernel Self Protection
  Project[1] and a 2019 study performed by Capsule 8 shows that it is
  enabled in many other major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

  In Ubuntu impish:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set

  In Debian 11:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y

  In Debian sid:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959384/+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 1971186] Re: Suggests linux-lowlatency-tools instead of linux-tools-lowlatency

[Laurent Bonnaud]

** Tags added: noble

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

Title:
  Suggests linux-lowlatency-tools instead of linux-tools-lowlatency

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  Hi,

  the linux-image-*-lowlatency kernel package suggests the linux-
  lowlatency-tools package:

  $ apt show linux-image-5.15.0-27-lowlatency
  Package: linux-image-5.15.0-27-lowlatency
  Version: 5.15.0-27.28
  [...]
  Suggests: fdutils, linux-doc | linux-lowlatency-source-5.15.0, 
linux-lowlatency-tools, linux-headers-5.15.0-27-lowlatency, 
linux-modules-extra-5.15.0-27-lowlatency

  The linux-lowlatency-tools package does not exist.  However, a linux-
  tools-lowlatency does exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-lowlatency 5.15.0-27.28
  Uname: Linux 5.17.5-051705-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon May  2 20:06:21 2022
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/1971186/+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 1993566] Re: dbus-daemon: Unknown group "power" in message bus configuration file

[Laurent Bonnaud]

** Tags added: noble

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

Title:
  dbus-daemon: Unknown group "power" in message bus configuration file

Status in thermald package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I see the following error message in the logs:

  # journalctl | grep 'Unknown group "power"'
  Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in 
message bus configuration file
  Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file
  Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file

  The problem comes from this file:

  # grep -r power /etc/dbus-1/
  /etc/dbus-1/system.d/org.freedesktop.thermald.conf:

[Kernel-packages] [Bug 2037212] Re: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)

[Laurent Bonnaud]

This problem still exists in noble:

# journalctl | grep ConfigurationDirectory
Apr 15 11:00:12 vougeot (uetoothd)[3112]: bluetooth.service: 
ConfigurationDirectory 'bluetooth' already exists but the mode is different. 
(File system: 755 ConfigurationDirectoryMode: 555)


** Tags added: noble

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

Title:
  ConfigurationDirectory 'bluetooth' already exists but the mode is
  different. (File system: 755 ConfigurationDirectoryMode: 555)

Status in bluez package in Ubuntu:
  Confirmed
Status in bluez package in Debian:
  Confirmed

Bug description:
  Hi,

  when my system boots it logs the following warning in the journal:

  $ journalctl | grep ConfigurationDirectory
  Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 
ConfigurationDirectoryMode: 555)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: bluez 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 13:28:20 2023
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 70:9C:D1:50:1F:7B  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037212/+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 1942133] Re: Nvidia driver packages prevent suspend due to leftover Systemd units

[Laurent Simon]

** Information type changed from Public to Public Security

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

Title:
  Nvidia driver packages prevent suspend due to leftover Systemd units

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed

Bug description:
  When the nvidia driver packages are uninstalled, they leave some
  symlinks that prevent suspend.

  I whink that, when attempting to suspend, the error is logged as this
  (edited):

  ModemManager[3287]:   [sleep-monitor] inhibit failed: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
  upowerd[5771]: Could not acquire inhibitor lock: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
  dbus-daemon[2888]: [system] Activating via systemd: service 
name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' 
requested by ':1.53' (uid=1000 pid=8227 
comm="/usr/lib/x86_64-linux-gnu/indicator-session/indica" label="unconfined")
  systemd[1]: systemd-logind.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
  systemd[1]: systemd-logind.service: Scheduled restart job, restart 
counter is at 7.
  systemd[1]: Stopped Login Service.
  systemd[1]: Condition check resulted in Load Kernel Module drm being 
skipped.
  systemd[1]: Starting Login Service...

  I've deleted the problematic symlinks while trying to solving the
  problem, however, they should be these:

  
/etc/systemd/system/systemd-suspend-service.requires/nvidia-suspend.service
  /etc/systemd/system/systemd-suspend-service.requires/nvidia-resume.service
  
/etc/systemd/system/systemd-hibernate-service.requires/nvidia-suspend.service
  
/etc/systemd/system/systemd-hibernate-service.requires/nvidia-resume.service

  I've briefly checked before removing them; at least a couple of them
  were masked, but they were still causing the problem.

  I don't see any reason why they should hang around the systemd
  configuration once the packages are purged. Additionally, this is a
  problem that is not easy to diagnose.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nvidia-driver-470 (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CasperVersion: 1.445.1
  CurrentDesktop: MATE
  Date: Mon Aug 30 21:10:52 2021
  LiveMediaBuild: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-470
  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-470/+bug/1942133/+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 2042858] [NEW] No newer mainline kernel builds

[Laurent Bonnaud]

Public bug reported:

Hi,

no mainline kernel builds have been published since a while, and
available builds are a few versions old.

Can you do something about this problem ?

Thanks!

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

Title:
  No newer mainline kernel builds

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  no mainline kernel builds have been published since a while, and
  available builds are a few versions old.

  Can you do something about this problem ?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042858/+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 2037214] [NEW] evict_inodes inode xxx, i_count = 1, was skipped!

[Laurent Bonnaud]

Public bug reported:

Hi,

during boot the kernel logs the following messages:

# dmesg | grep evict_inodes
[   12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[   12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[   12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[   12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[   12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[   12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[   12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[   12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[   12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[   13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[   13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[   13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[   13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[   13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!

Those messages are not displayed when I boot my system with a mainline Linux 
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where such 
a message could be printed.

Therefore, those messages are probably caused by an Ubuntu patch.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bonnaudl   4827 F wireplumber
 /dev/snd/seq:bonnaudl   4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off 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.
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-5-generic N/A
 linux-backports-modules-6.5.0-5-generic  N/A
 linux-firmware   20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO

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


** Tags: amd64 apport-bug 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/2037214

Title:
  evict_inodes inode xxx, i_count = 1, was skipped!

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  during boot the kernel logs the following messages:

  # dmesg | grep evict_inodes
  [   12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
  [   12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
  [   12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
  [   12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
  [   12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412673] evict_inodes inode ec873c71, i_count = 1, was s

[Kernel-packages] [Bug 2037212] [NEW] ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)

[Laurent Bonnaud]

Public bug reported:

Hi,

when my system boots it logs the following warning in the journal:

$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 
ConfigurationDirectoryMode: 555)

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 13:28:20 2023
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 70:9C:D1:50:1F:7B  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0

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

** Affects: bluez (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug mantic

** Bug watch added: Debian Bug tracker #1017988
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017988

** Also affects: bluez (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017988
   Importance: Unknown
   Status: Unknown

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

Title:
  ConfigurationDirectory 'bluetooth' already exists but the mode is
  different. (File system: 755 ConfigurationDirectoryMode: 555)

Status in bluez package in Ubuntu:
  New
Status in bluez package in Debian:
  Unknown

Bug description:
  Hi,

  when my system boots it logs the following warning in the journal:

  $ journalctl | grep ConfigurationDirectory
  Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 
ConfigurationDirectoryMode: 555)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: bluez 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 13:28:20 2023
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 70:9C:D1:50:1F:7B  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0

To manage notifications about this bug go to:
htt

[Kernel-packages] [Bug 1806437] Re: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)

[Laurent Bonnaud]

This bug is fixed in recent kernels.
Thanks:

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

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

Title:
  acpi PNP0C14:02: duplicate WMI GUID
  05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on
  PNP0C14:01)

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

Bug description:
  Hello,

  dmesg:
  [   15.390738] acpi PNP0C14:02: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2769 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 12:49:26 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806437/+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 1912509] Re: ucsi_acpi USBC000:00: PPM init failed (-110)

[Laurent Bonnaud]

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

Title:
  ucsi_acpi USBC000:00: PPM init failed (-110)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting with kernel 5.8.0-38-generic on my Asus Tuf 15 with 2 NVMe 
drives I get:
  usci_acpi USBC000:00: PPM init failed (-110) and the laptop freezes.

  kernel 5.4.0-26-generic usually boots (but get an occasional freeze).

  Since I cannot boot in the 5.8 kernel I cannot file the bug with that
  kernel running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vincent1381 F pulseaudio
   /dev/snd/controlC0:  vincent1381 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 20 17:28:23 2021
  InstallationDate: Installed on 2021-01-20 (0 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LI_FX506LI
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=74589408-5655-4728-b040-86c06177a989 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX506LI.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX506LI
  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.:bvrFX506LI.307:bd12/17/2020:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LI_FX506LI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ASUS TUF Gaming F15
  dmi.product.name: ASUS TUF Gaming F15 FX506LI_FX506LI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912509/+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 1959384] Re: CONFIG_IO_STRICT_DEVMEM could be enabled

[Laurent Bonnaud]

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

Title:
  CONFIG_IO_STRICT_DEVMEM could be enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace
  access of active io-memory ranges.

  This could impact kernel debugability. In that case, you may reboot with
  iomem=relaxed on the kernel command line to override this setting.

  This config option is recommended by the Kernel Self Protection
  Project[1] and a 2019 study performed by Capsule 8 shows that it is
  enabled in many other major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

  In Ubuntu impish:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set

  In Debian 11:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y

  In Debian sid:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959384/+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 1971186] Re: Suggests linux-lowlatency-tools instead of linux-tools-lowlatency

[Laurent Bonnaud]

** Tags added: mantic

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

Title:
  Suggests linux-lowlatency-tools instead of linux-tools-lowlatency

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  Hi,

  the linux-image-*-lowlatency kernel package suggests the linux-
  lowlatency-tools package:

  $ apt show linux-image-5.15.0-27-lowlatency
  Package: linux-image-5.15.0-27-lowlatency
  Version: 5.15.0-27.28
  [...]
  Suggests: fdutils, linux-doc | linux-lowlatency-source-5.15.0, 
linux-lowlatency-tools, linux-headers-5.15.0-27-lowlatency, 
linux-modules-extra-5.15.0-27-lowlatency

  The linux-lowlatency-tools package does not exist.  However, a linux-
  tools-lowlatency does exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-lowlatency 5.15.0-27.28
  Uname: Linux 5.17.5-051705-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon May  2 20:06:21 2022
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/1971186/+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 1991691] Re: cannot change mount namespace

[Laurent Bonnaud]

The fix a now upstream according to last comment.
Thanks!

** Changed in: linux
   Status: New => Fix Released

** Changed in: snapd (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  cannot change mount namespace

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

Bug description:
  Multiple snaps are either broken or "only" display permission denied
  messages.

  slack snap is not starting at all with:

  > update.go:85: cannot change mount namespace according to change
  mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none
  bind,rw,x-snapd.ignore-missing 0 0): cannot inspect
  "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied

  firefox snap does start, but also logs errors:

  
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot 
inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat 
/var/lib/snapd/hostfs/usr/share/doc: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat 
/var/lib/snapd/hostfs/usr/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat 
/usr/local/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none 
bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission 
denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none 
bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat 
/var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": 
lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: snap (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Oct  4 17:29:01 2022
  InstallationDate: Installed on 2017-09-26 (1834 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
  SourcePackage: snap
  UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1991691/+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 1993566] Re: dbus-daemon: Unknown group "power" in message bus configuration file

[Laurent Bonnaud]

** Tags added: mantic

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

Title:
  dbus-daemon: Unknown group "power" in message bus configuration file

Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Hi,

  I see the following error message in the logs:

  # journalctl | grep 'Unknown group "power"'
  Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in 
message bus configuration file
  Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file
  Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file

  The problem comes from this file:

  # grep -r power /etc/dbus-1/
  /etc/dbus-1/system.d/org.freedesktop.thermald.conf:

[Kernel-packages] [Bug 1979633] Re: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated"

[Laurent Bonnaud]

I am closing this bug since the error messages are not displayed any longer.
Thanks!


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

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 2027567] Re: No more HDMI

[Laurent Lyaudet]

Hello,
I just tested latest kernel proposed in
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed
6.2.0-27.28 solves my problem :)
Thank you very much :)
Best regards,
   Laurent Lyaudet

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

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

Title:
  No more HDMI

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:    laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 2027567] Re: No more HDMI

[Laurent Lyaudet]

And I also cannot log in here:
https://discourse.ubuntu.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/2027567

Title:
  No more HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:    laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 2027567] Re: No more HDMI

[Laurent Lyaudet]

I wanted to correct the wiki by updating the PPA here:
https://wiki.ubuntu.com/Kernel/FAQ
But when I try to login to the wiki using Ubuntu One it says invalid 
email/password combination.
But it is exactly the same email/password combination that I use for 
launchpad.net.
Is the wiki limited to Ubuntu staff?

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

Title:
  No more HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:    laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 2027567] Re: No more HDMI

[Laurent Lyaudet]

After listing all packages in the PPA for Lunar Lobster, I did not found
anything newer.

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

Title:
  No more HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:    laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 2027567] Re: No more HDMI

[Laurent Lyaudet]

I think I found relevant info here:
https://wiki.ubuntu.com/Kernel/FAQ
"""
My bug is Fix Committed but the fix is not in the kernel?

Once a fix has been reviewed and approved on the Kernel Team email list it will 
then be applied to the kernel git tree. When sufficient updates have 
accumulated a -proposed kernel will be uploaded; you need the proposed pocket 
enabled to get these kernels. It can take some time before these changes are 
uploaded, however every day the tree is checked and if there are any new 
patches a new pre-proposed kernel is automatically uploaded to the kernel team 
pre-proposed PPA ppa:~kernel-ppa/pre-proposed. Adding both the proposed pocket 
and the pre-proposed PPA will get you all pending fixes as soon as possible. 
See Kernel/Dev/KernelTesting for details. 
"""

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

Title:
  No more HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 2027567] Re: No more HDMI

[Laurent Lyaudet]

laurent@laurent-GL73-8SD:~$ sudo apt-add-repository ppa:~kernel-ppa/pre-proposed
[sudo] Mot de passe de laurent : 
ERROR: ppa 'kernel-ppa/pre-proposed' not found (use --login if private)

It seems the FAQ is not up to date.

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

Title:
  No more HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 2027567] Re: No more HDMI

[Laurent Lyaudet]

I found this instead:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed

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

Title:
  No more HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:    laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 2027567] Re: No more HDMI

[Laurent Lyaudet]

I have read:
https://wiki.ubuntu.com/Kernel/Bugs

It seems the next step to help is this:
> 4. Finally, it's critical to also make sure to test the latest development 
> Ubuntu kernel version as well as the latest upstream mainline kernel. 

But the wiki for latest upstream mainline kernel tells that I may need
to disable the Nvidia driver which will guaranty that I'm not testing
what the bug is about.

And I did not found a wiki for "test the latest development Ubuntu kernel 
version as well".
When I look here:
https://packages.ubuntu.com/search?keywords=linux-generic
I do not see any newer kernel for lunar lobster.

Any help on this would be great :)

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

Title:
  No more HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 2027567] Re: No more HDMI

[Laurent Lyaudet]

** Attachment added: "Capture d’écran du 2023-07-12 11-24-42.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+attachment/5685790/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-07-12%2011-24-42.png

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

Title:
  No more HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 2027567] Re: No more HDMI

[Laurent Lyaudet]

I'm sorry. I just tried again to upload the screenshot. But it is not
possible to open the PNG files when I click on them in the bug report.

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

Title:
  No more HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
      Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:    laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 2027567] Re: No more HDMI

[Laurent Lyaudet]

** Attachment added: "resultOfCommandWith6_2_0_24"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+attachment/5685683/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-07-12%2011-29-20.png

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

Title:
  No more HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 2027567] [NEW] No more HDMI

[Laurent Lyaudet]

Public bug reported:

Hello,
Thanks for your hard work :)
I just upgraded to kernel 6.2.0-25.
There is no more HDMI and my external screen can not be used.
Moreover, when I stop my laptop, it takes 30s.
If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes 
a few seconds.
I'll join screenshots of command:
ls /sys/class/drm/*

Thanks, best regards,
Laurent Lyaudet

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-25-generic 6.2.0-25.25
ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
Uname: Linux 6.2.0-25-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  laurent5201 F wireplumber
 /dev/snd/controlC1:  laurent5201 F wireplumber
 /dev/snd/seq:    laurent5192 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 12 11:34:15 2023
InstallationDate: Installed on 2020-07-01 (1105 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Micro-Star International Co., Ltd. GL73 8SD
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-25-generic N/A
 linux-backports-modules-6.2.0-25-generic  N/A
 linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
SourcePackage: linux
UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
dmi.bios.date: 03/29/2019
dmi.bios.release: 1.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17C7IMS.10E
dmi.board.asset.tag: Default string
dmi.board.name: MS-17C7
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
dmi.product.family: GL
dmi.product.name: GL73 8SD
dmi.product.sku: 17C7.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

** Attachment added: "resultOfCommandWith6_2_0_25"
   
https://bugs.launchpad.net/bugs/2027567/+attachment/5685665/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-07-12%2011-24-42.png

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

Title:
  No more HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: 

[Kernel-packages] [Bug 2023986] Re: Drivers not working using kernel linux-image-6.2.0-1003-oracle

[Guillaume LAURENT]

OK, I'm not crazy.

My dual screen stopped working tonight, and the Nvidia panel stays
empty.

I had to switch back to 6.2.0-23-generic.

** Attachment added: "history.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oracle/+bug/2023986/+attachment/5680314/+files/history.log

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

Title:
  Drivers not working using kernel linux-image-6.2.0-1003-oracle

Status in linux-signed-oracle package in Ubuntu:
  Confirmed

Bug description:
  My Ubuntu 23.04 installed two kernels linux-image-6.2.0-1003-oracle
  and linux-image-6.2.0-1003-lowlatency using software updater along
  with other updates. After install and restart, most drivers including
  wifi, bluetooth, touchpad and ethernet stopped working. Rebooting
  using 6.2.0-1003-lowlatency or 6.2.0-20-generic solved the driver
  issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-1003-oracle 6.2.0-1003.3
  ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6
  Uname: Linux 6.2.0-1003-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 15 16:34:56 2023
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: linux-signed-oracle
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oracle/+bug/2023986/+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 2009271] Re: Too many BDL entries regression

[Laurent Lyaudet]

Hello :)

I upgraded Ubuntu to Lunar Lobster 23.04 on Saturday evening.
Since then, I no more have this bug with new kernel 6.2 :)

Thanks, best regards,
Laurent Lyaudet

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

Title:
  Too many BDL entries regression

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed

Bug description:
  Hello,

  Thanks for your hard work :)
  I got this error after kernel update to 5.19.0-35 as explained here :
  
https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log
  and here :
  
https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u

  A load of syslog "Too many BDL entries" appears.

  Have a nice week-end, best regards,
      Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-35-generic 5.19.0-35.36
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5004 F wireplumber
   /dev/snd/controlC1:  laurent5004 F wireplumber
   /dev/snd/seq:    laurent5000 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  4 16:47:55 2023
  InstallationDate: Installed on 2020-07-01 (976 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+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 2009271] Re: Too many BDL entries regression

[Laurent Lyaudet]

Hello :)

I updated to linux 5.19.0-40, a few days ago, and the bug is still here.

Thanks, best regards,
Laurent Lyaudet

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

Title:
  Too many BDL entries regression

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed

Bug description:
  Hello,

  Thanks for your hard work :)
  I got this error after kernel update to 5.19.0-35 as explained here :
  
https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log
  and here :
  
https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u

  A load of syslog "Too many BDL entries" appears.

  Have a nice week-end, best regards,
      Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-35-generic 5.19.0-35.36
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5004 F wireplumber
   /dev/snd/controlC1:  laurent5004 F wireplumber
   /dev/snd/seq:    laurent5000 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  4 16:47:55 2023
  InstallationDate: Installed on 2020-07-01 (976 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+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 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Laurent Bonnaud]

This bug is very old, and I do not see it any longer on a newer Dell
laptop and a newer Ubuntu release.

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

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597415/+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 1912509] Re: ucsi_acpi USBC000:00: PPM init failed (-110)

[Laurent Bonnaud]

The bug is still there in lunar:

# dmesg | grep PPM
[5.477076] ucsi_acpi USBC000:00: PPM init failed (-110)

# uname -a
Linux vougeot 6.2.0-18-generic #18-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 16 
00:09:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux


** Summary changed:

- usci_acpi USBC000:00: PPM init failed (-110)
+ ucsi_acpi USBC000:00: PPM init failed (-110)

** Tags removed: impish
** Tags added: jammy kinetic lunar

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

Title:
  ucsi_acpi USBC000:00: PPM init failed (-110)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting with kernel 5.8.0-38-generic on my Asus Tuf 15 with 2 NVMe 
drives I get:
  usci_acpi USBC000:00: PPM init failed (-110) and the laptop freezes.

  kernel 5.4.0-26-generic usually boots (but get an occasional freeze).

  Since I cannot boot in the 5.8 kernel I cannot file the bug with that
  kernel running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vincent1381 F pulseaudio
   /dev/snd/controlC0:  vincent1381 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 20 17:28:23 2021
  InstallationDate: Installed on 2021-01-20 (0 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LI_FX506LI
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=74589408-5655-4728-b040-86c06177a989 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX506LI.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX506LI
  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.:bvrFX506LI.307:bd12/17/2020:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LI_FX506LI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ASUS TUF Gaming F15
  dmi.product.name: ASUS TUF Gaming F15 FX506LI_FX506LI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912509/+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 1959384] Re: CONFIG_IO_STRICT_DEVMEM could be enabled

[Laurent Bonnaud]

** Tags added: kinetic lunar

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

Title:
  CONFIG_IO_STRICT_DEVMEM could be enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace
  access of active io-memory ranges.

  This could impact kernel debugability. In that case, you may reboot with
  iomem=relaxed on the kernel command line to override this setting.

  This config option is recommended by the Kernel Self Protection
  Project[1] and a 2019 study performed by Capsule 8 shows that it is
  enabled in many other major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

  In Ubuntu impish:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set

  In Debian 11:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y

  In Debian sid:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959384/+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 1971186] Re: Suggests linux-lowlatency-tools instead of linux-tools-lowlatency

[Laurent Bonnaud]

** Tags added: kinetic lunar

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

Title:
  Suggests linux-lowlatency-tools instead of linux-tools-lowlatency

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  Hi,

  the linux-image-*-lowlatency kernel package suggests the linux-
  lowlatency-tools package:

  $ apt show linux-image-5.15.0-27-lowlatency
  Package: linux-image-5.15.0-27-lowlatency
  Version: 5.15.0-27.28
  [...]
  Suggests: fdutils, linux-doc | linux-lowlatency-source-5.15.0, 
linux-lowlatency-tools, linux-headers-5.15.0-27-lowlatency, 
linux-modules-extra-5.15.0-27-lowlatency

  The linux-lowlatency-tools package does not exist.  However, a linux-
  tools-lowlatency does exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-lowlatency 5.15.0-27.28
  Uname: Linux 5.17.5-051705-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon May  2 20:06:21 2022
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/1971186/+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 1993566] Re: dbus-daemon: Unknown group "power" in message bus configuration file

[Laurent Bonnaud]

The same problem exists in lunar and this package version:

Package: thermald
Version: 2.5.2-1


** Tags added: lunar

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

Title:
  dbus-daemon: Unknown group "power" in message bus configuration file

Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Hi,

  I see the following error message in the logs:

  # journalctl | grep 'Unknown group "power"'
  Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in 
message bus configuration file
  Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file
  Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file

  The problem comes from this file:

  # grep -r power /etc/dbus-1/
  /etc/dbus-1/system.d/org.freedesktop.thermald.conf:

[Kernel-packages] [Bug 2009271] Re: Too many BDL entries regression

[Laurent Lyaudet]

Hello :)
I had the bug again this evening.
So the bug is less frequent (at least for me) but still exists also on my 
hardware.
Best regards,
   Laurent Lyaudet

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

Title:
  Too many BDL entries regression

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed

Bug description:
  Hello,

  Thanks for your hard work :)
  I got this error after kernel update to 5.19.0-35 as explained here :
  
https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log
  and here :
  
https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u

  A load of syslog "Too many BDL entries" appears.

  Have a nice week-end, best regards,
      Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-35-generic 5.19.0-35.36
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5004 F wireplumber
   /dev/snd/controlC1:  laurent5004 F wireplumber
   /dev/snd/seq:    laurent5000 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  4 16:47:55 2023
  InstallationDate: Installed on 2020-07-01 (976 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+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 2009271] Re: Too many BDL entries regression

[Laurent Lyaudet]

Hello :)

I just updated to linux 5.19.0-38 and the bug seems to be gone :)
But other users still have it like FedKad on 
https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log


Thanks, best regards,
Laurent Lyaudet

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

Title:
  Too many BDL entries regression

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed

Bug description:
  Hello,

  Thanks for your hard work :)
  I got this error after kernel update to 5.19.0-35 as explained here :
  
https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log
  and here :
  
https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u

  A load of syslog "Too many BDL entries" appears.

  Have a nice week-end, best regards,
      Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-35-generic 5.19.0-35.36
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5004 F wireplumber
   /dev/snd/controlC1:  laurent5004 F wireplumber
   /dev/snd/seq:    laurent5000 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  4 16:47:55 2023
  InstallationDate: Installed on 2020-07-01 (976 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+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 2009271] [NEW] Too many BDL entries regression

[Laurent Lyaudet]

Public bug reported:

Hello,

Thanks for your hard work :)
I got this error after kernel update to 5.19.0-35 as explained here :
https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log
and here :
https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u

A load of syslog "Too many BDL entries" appears.

Have a nice week-end, best regards,
    Laurent Lyaudet

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-35-generic 5.19.0-35.36
ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  laurent5004 F wireplumber
 /dev/snd/controlC1:  laurent5004 F wireplumber
 /dev/snd/seq:    laurent5000 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  4 16:47:55 2023
InstallationDate: Installed on 2020-07-01 (976 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Micro-Star International Co., Ltd. GL73 8SD
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d 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.
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-35-generic N/A
 linux-backports-modules-5.19.0-35-generic  N/A
 linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
SourcePackage: linux
UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago)
dmi.bios.date: 03/29/2019
dmi.bios.release: 1.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17C7IMS.10E
dmi.board.asset.tag: Default string
dmi.board.name: MS-17C7
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
dmi.product.family: GL
dmi.product.name: GL73 8SD
dmi.product.sku: 17C7.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug kinetic

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

Title:
  Too many BDL entries regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Thanks for your hard work :)
  I got this error after kernel update to 5.19.0-35 as explained here :
  
https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log
  and here :
  
https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u

  A load of syslog "Too many BDL entries" appears.

  Have a nice week-end, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-35-generic 5.19.0-35.36
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USER    PID ACCESS COMMAND
   /dev/snd/controlC0:  laurent    5004 F wireplumber
   /dev/snd/controlC1:  laurent    5004 F wireplumber
   /dev/snd/seq:laurent5000 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  4 16:47:55 2023
  InstallationDate: Installed on 2020-07-01 (976 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

[Laurent Pinchart]

@kolbjorn could you please provide the output of `lsusb -v -d 0408:4033`
(running as root, for instance with sudo, if possible) ? Attaching a
file would be preferred to avoid messing up formatting.

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Typ

[Kernel-packages] [Bug 2002834] Re: Network bridge issue after updating kernel to 5.4.0-137

[Laurent]

Exact same issue here with jammy and going from 5.15.0-57.63 to 5.15.0-58.64
the issue is also reproduced with 5.15.0.59.57 (proposed)

Context is xen host, bond + vlans + bridge for xen VMs
Network is ok on the host, VM are not working, very weird, you can see some 
traffic coming through the bridge to the VM, but not on the other way around.

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

Title:
  Network bridge issue after updating kernel to 5.4.0-137

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  After updating the kernel from 5.4.0-136 to 5.4.0-137 network bridge are not 
working any more.
  I can see the bridge with "ip add show" or "brctl show". Network is up and I 
can reach the full network from the host through the bridge.

  VM on the host can not reach network or host and host can not reach
  the VM through the bridge.

  We have bonded interface used in the bridge and one bridge without IP
  and one with an IP. DHCP is off on booth bridge.

  Downgrading the kernel to 5.4.136 (Ubuntu 5.4.0-136.153-generic
  5.4.218) seem to work fine.

  Thank you for your help.

  Details
  Description:  Ubuntu 20.04.5 LTS
  Release:  20.04
  Not working version => Ubuntu 5.4.0-137.154-generic 5.4.218

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2002834/+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 1993566] Re: dbus-daemon: Unknown group "power" in message bus configuration file

[Laurent Bonnaud]

The same problem exists in kinetic and this package version:

Package: thermald
Version: 2.5.1-1

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

Title:
  dbus-daemon: Unknown group "power" in message bus configuration file

Status in thermald package in Ubuntu:
  New

Bug description:
  Hi,

  I see the following error message in the logs:

  # journalctl | grep 'Unknown group "power"'
  Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in 
message bus configuration file
  Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file
  Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file

  The problem comes from this file:

  # grep -r power /etc/dbus-1/
  /etc/dbus-1/system.d/org.freedesktop.thermald.conf:

[Kernel-packages] [Bug 1993566] Re: dbus-daemon: Unknown group "power" in message bus configuration file

[Laurent Bonnaud]

The same problem exists in kinetic and this package version:

Package: thermald
Version: 2.5.1-1

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

Title:
  dbus-daemon: Unknown group "power" in message bus configuration file

Status in thermald package in Ubuntu:
  New

Bug description:
  Hi,

  I see the following error message in the logs:

  # journalctl | grep 'Unknown group "power"'
  Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in 
message bus configuration file
  Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file
  Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file

  The problem comes from this file:

  # grep -r power /etc/dbus-1/
  /etc/dbus-1/system.d/org.freedesktop.thermald.conf:

[Kernel-packages] [Bug 1993566] [NEW] dbus-daemon: Unknown group "power" in message bus configuration file

[Laurent Bonnaud]

Public bug reported:

Hi,

I see the following error message in the logs:

# journalctl | grep 'Unknown group "power"'
Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in 
message bus configuration file
Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file
Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file

The problem comes from this file:

# grep -r power /etc/dbus-1/
/etc/dbus-1/system.d/org.freedesktop.thermald.conf:

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

[Laurent Bonnaud]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1979633/+attachment/5623922/+files/ProcCpuinfoMinimal.txt

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1979633/+attachment/5623933/+files/ProcModules.txt

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

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

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

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1979633/+attachment/5623937/+files/WifiSyslog.txt

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1979633/+attachment/5623931/+files/ProcEnviron.txt

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1979633/+attachment/5623921/+files/ProcCpuinfo.txt

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1979633/+attachment/5623914/+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/1979633

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1979633/+attachment/5623912/+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/1979633

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

[Laurent Bonnaud]

apport information

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

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 7.15
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.15RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.6
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] Re: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated"

[Laurent Bonnaud]

apport information

** Tags added: apport-collected

** Description changed:

  Hi,
  
  here is the problem:
  
  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated
  
  The loop4 device is used to mount the "bare" snap:
  
  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5
  
  Note that on another system, the loop device will probably have another
  number.  The error messages can be found with the following commands:
  
  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  
  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  
  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: snapd 2.55.5+22.04
  Uname: Linux 5.18.6-051806-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jun 23 11:39:16 2022
  Snap.Changes: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  bonnaudl   5120 F pulseaudio
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 22.04
+ MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-50-generic N/A
+  linux-backports-modules-5.15.0-50-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.6
+ Tags:  jammy
+ Uname: Linux 5.15.0-50-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/11/2022
+ dmi.bios.release: 7.15
+ dmi.bios.vendor: INSYDE Corp.
+ dmi.bios.version: 1.07.15RTR2
+ dmi.board.asset.tag: Tag 12345
+ dmi.board.name: NS50_70MU
+ dmi.board.vendor: TUXEDO
+ dmi.board.version: Applicable
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Notebook
+ dmi.chassis.version: N/A
+ dmi.ec.firmware.release: 7.6
+ dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
+ dmi.product.family: Not Applicable
+ dmi.product.name: TUXEDO InfinityBook S 15 Gen6
+ dmi.product.sku: Not Applicable
+ dmi.product.version: Not Applicable
+ dmi.sys.vendor: TUXEDO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1979633/+attachment/5623911/+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/1979633

Title:
  The "bare" snap is the cause of error messages "unable to read
  partition table" and "partition table beyond EOD, truncated"

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

Bug description:
  Hi,

  here is the problem:

  # journalctl | grep loop4
  Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table
  Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated

  The loop4 device is used to mount the "bare" snap:

  $ df -a | grep /snap/bare/
  [...]
  /dev/loop4  128   128 0 100% 
/snap/bare/5

  Note that on another system, the loop device will probably have
  another number.  The error messages can be found with the following
  commands:

  # journalctl | grep "unable to read RDB block"
  Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8

  # journalctl | grep "unable to read partition table"
  Jun 23 09:49:45 vougeot kernel:  loop4: unable to read partition table

  # journalctl | grep "partition table beyond EOD"
  Jun 23 09:49:45 vougeot kernel: loo

[Kernel-packages] [Bug 1971186] [NEW] Suggests linux-lowlatency-tools instead of linux-tools-lowlatency

[Laurent Bonnaud]

Public bug reported:

Hi,

the linux-image-*-lowlatency kernel package suggests the linux-
lowlatency-tools package:

$ apt show linux-image-5.15.0-27-lowlatency
Package: linux-image-5.15.0-27-lowlatency
Version: 5.15.0-27.28
[...]
Suggests: fdutils, linux-doc | linux-lowlatency-source-5.15.0, 
linux-lowlatency-tools, linux-headers-5.15.0-27-lowlatency, 
linux-modules-extra-5.15.0-27-lowlatency

The linux-lowlatency-tools package does not exist.  However, a linux-
tools-lowlatency does exist.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-27-lowlatency 5.15.0-27.28
Uname: Linux 5.17.5-051705-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Mon May  2 20:06:21 2022
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: linux-signed-lowlatency
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Suggests linux-lowlatency-tools instead of linux-tools-lowlatency

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  Hi,

  the linux-image-*-lowlatency kernel package suggests the linux-
  lowlatency-tools package:

  $ apt show linux-image-5.15.0-27-lowlatency
  Package: linux-image-5.15.0-27-lowlatency
  Version: 5.15.0-27.28
  [...]
  Suggests: fdutils, linux-doc | linux-lowlatency-source-5.15.0, 
linux-lowlatency-tools, linux-headers-5.15.0-27-lowlatency, 
linux-modules-extra-5.15.0-27-lowlatency

  The linux-lowlatency-tools package does not exist.  However, a linux-
  tools-lowlatency does exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-lowlatency 5.15.0-27.28
  Uname: Linux 5.17.5-051705-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon May  2 20:06:21 2022
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/1971186/+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 1933771] UdevDb.txt

[Laurent Dumont]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1933771/+attachment/5577463/+files/UdevDb.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

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

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

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

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1933771/+attachment/5577464/+files/WifiSyslog.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1933771/+attachment/5577452/+files/Lsusb.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1933771] Lsusb-v.txt

[Laurent Dumont]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1933771/+attachment/5577454/+files/Lsusb-v.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1933771] Re: Bluetooth headset random disconnects AX200

[Laurent Dumont]

I guess I now know what aport-collect does! :D

Another crash with

ii  linux-firmware
20220314.gitcd01f857-0ubuntu2  all  Firmware for
Linux kernel driver

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1933771/+attachment/5577462/+files/RfKill.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1933771] Lsusb-t.txt

[Laurent Dumont]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1933771/+attachment/5577453/+files/Lsusb-t.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1933771] Lspci-vt.txt

[Laurent Dumont]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1933771/+attachment/5577451/+files/Lspci-vt.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1933771/+attachment/5577457/+files/ProcCpuinfoMinimal.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1933771/+attachment/5577459/+files/ProcInterrupts.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1933771/+attachment/5577461/+files/PulseList.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1933771/+attachment/5577460/+files/ProcModules.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1933771/+attachment/5577458/+files/ProcEnviron.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1933771/+attachment/5577456/+files/ProcCpuinfo.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1933771/+attachment/5577455/+files/PaInfo.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1933771/+attachment/5577449/+files/IwConfig.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1933771] Re: Bluetooth headset random disconnects AX200

[Laurent Dumont]

ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  coldadmin   2501 F pulseaudio
 /dev/snd/controlC2:  coldadmin   2501 F pulseaudio
 /dev/snd/controlC1:  coldadmin   2501 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Dependencies:
 
DistroRelease: Ubuntu 21.10
HibernationDevice: RESUME=UUID=fe65245e-b825-45a8-8b9f-09ec44fbbcf7
InstallationDate: Installed on 2019-01-04 (1187 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Micro-Star International Co., Ltd. MS-7B22
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 20220314.gitcd01f857-0ubuntu2 [origin: unknown]
PackageArchitecture: all
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=95e90995-8bd5-4941-9778-7cbd5bb5fe34 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-35-generic N/A
 linux-backports-modules-5.13.0-35-generic  N/A
 linux-firmware 20220314.gitcd01f857-0ubuntu2
Tags: third-party-packages impish
Uname: Linux 5.13.0-35-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package. Please 
retry after updating the indexes of available packages, if that does not work 
then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo ubridge
_MarkForUpload: True
dmi.bios.date: 12/26/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.90
dmi.board.asset.tag: Default string
dmi.board.name: B360-A PRO (MS-7B22)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.90:bd12/26/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B22:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360-APRO(MS-7B22):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7B22
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.


** Tags added: apport-collected impish third-party-packages

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

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

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1933771/+attachment/5577446/+files/AlsaInfo.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

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

[Laurent Dumont]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1933771/+attachment/5577447/+files/CRDA.txt

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1933771] Re: Bluetooth headset random disconnects AX200

[Laurent Dumont]

Tried the new version from jammy, same issue :(

ii  linux-firmware
20220314.gitcd01f857-0ubuntu2  all  Firmware for
Linux kernel drivers

Disconnect at 10:41 EST

Mar 20 10:41:03 big-potato bluetoothd[1084]: 
src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice 
gateway: getpeername: Transport endpoint is not connected (107)
Mar 20 10:41:10 big-potato bluetoothd[1084]: 
/org/bluez/hci0/dev_00_8A_76_26_7B_69/sep1/fd1: fd(41) ready

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1933771] Re: Bluetooth headset random disconnects AX200

[Laurent Dumont]

Same issue with the new Firmware.

Mar  5 12:35:17 big-potato bluetoothd[1069]: 
profiles/audio/avdtp.c:handle_unanswered_req() No reply to Suspend request
Mar  5 12:35:17 big-potato bluetoothd[1069]: 
src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice 
gateway: getpeername: Transport endpoint is not connected (107)

sudo dpkg -l | grep linux-firmware  



Sat 05 Mar 2022 12:35:20 PM
hi  linux-firmware  
20220302.gitee0667aa-0ubuntu1  all  Firmware for Linux 
kernel drivers

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1933771] Re: Bluetooth headset random disconnects AX200

[Laurent Dumont]

Sure! I'll install the deb.

[3.195365] Bluetooth: Core ver 2.22
[3.195382] Bluetooth: HCI device and connection manager initialized
[3.195384] Bluetooth: HCI socket layer initialized
[3.195385] Bluetooth: L2CAP socket layer initialized
[3.195387] Bluetooth: SCO socket layer initialized
[3.201408] Bluetooth: hci0: Firmware revision 0.0 build 121 week 7 2021
[3.263426] Bluetooth: hci0: MSFT filter_enable is already on
[5.114319] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[5.114322] Bluetooth: BNEP filters: protocol multicast
[5.114326] Bluetooth: BNEP socket layer initialized
[   12.504895] Bluetooth: RFCOMM TTY layer initialized
[   12.504899] Bluetooth: RFCOMM socket layer initialized
[   12.504902] Bluetooth: RFCOMM ver 1.11
[ 5417.756529] Bluetooth: hci0: urb f43df3ae submission failed (90)
[ 5417.756535] Bluetooth: hci0: sending frame failed (-90)
[ 5417.756537] Bluetooth: hci0: urb f43df3ae submission failed (90)
[ 5417.756538] Bluetooth: hci0: sending frame failed (-90)
[ 5423.910998] Bluetooth: hci0: SCO packet for unknown connection handle 513

sudo lsusb |grep Bluetooth  



Sat 05 Mar 2022 12:18:04 PM
Bus 001 Device 007: ID 8087:0029 Intel Corp. AX200 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/1933771

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  New

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1933771] Re: Bluetooth headset random disconnects AX200

[Laurent Dumont]

Seeing this on 21.10.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 21.10
Release:21.10
Codename:   impish

coldadmin@big-potato:~$ dpkg -l | grep linux-firmware
ii  linux-firmware  1.201.4 
   all  Firmware for Linux kernel drivers


Logs from syslog

Feb 27 16:22:34 big-potato bluetoothd[1073]: 
profiles/audio/avdtp.c:handle_unanswered_req() No reply to Suspend request
Feb 27 16:22:34 big-potato bluetoothd[1073]: 
src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice 
gateway: getpeername: Transport endpoint is not connected (107)
Feb 27 16:22:40 big-potato bluetoothd[1073]: 
/org/bluez/hci0/dev_00_8A_76_26_7B_69/sep1/fd6: fd(41) ready

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

Title:
  Bluetooth headset random disconnects AX200

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  In Progress

Bug description:
  [Impact]

  Using several different bluetooth headsets I find that the Bluetooth
  functionality of the built-in AX200 module of my motherboard keeps
  randomly disconnecting. I found that this has been fixed in recent
  Linux firmware updates, but I am not sure that fix has landed yet in
  Ubuntu Hirsute.

  Herewith I am posting the link to exactly the issue I am having:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155

  And the Linux Firmware commit that resolves this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180

  A related Fedora bug:
  https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274

  It's difficult to relate the upstream kernel version firmware version
  in which this was fixed (linux-firmware-20210511) to the version of
  the linux-firmware Ubuntu package (for me). Perhaps someone can
  comment on whether this has been merged in. I am still experiencing
  disconnects with 1.197.1 at least.

  --

  Description:  Ubuntu 21.04
  Release:  21.04

  linux-firmware:
    Installed: 1.197.1
    Candidate: 1.197.1

  I expected:
    Bluetooth headset to remain connected

  What happened:
    Bluetooth headset connects, then randomly disconnects and reconnects while 
playing media

  [Test Case]

  See above.

  [Fix]

  Update AX20x firmware blobs.

  [Where Problems Could Occur]

  New firmware blobs so previously working adapter might now fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1959384] Re: CONFIG_IO_STRICT_DEVMEM could be enabled

[Laurent Bonnaud]

** Tags added: jammy

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

Title:
  CONFIG_IO_STRICT_DEVMEM could be enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace
  access of active io-memory ranges.

  This could impact kernel debugability. In that case, you may reboot with
  iomem=relaxed on the kernel command line to override this setting.

  This config option is recommended by the Kernel Self Protection
  Project[1] and a 2019 study performed by Capsule 8 shows that it is
  enabled in many other major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

  In Ubuntu impish:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set

  In Debian 11:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y

  In Debian sid:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959384/+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 1855338] Re: CONFIG_IO_STRICT_DEVMEM should be enabled

[Laurent Bonnaud]

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

** This bug has been marked a duplicate of bug 1959384
   CONFIG_IO_STRICT_DEVMEM could be enabled

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

Title:
  CONFIG_IO_STRICT_DEVMEM should be enabled

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  We should enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access
  of active io-memory ranges.

  This could impact kernel debugability. In that case, you may reboot with
  iomem=relaxed on the kernel commandline to override this setting.

  
  This config option is recommended by the Kernel Self Protection Project[1] 
and a 2019 study performed by Capsule 8 shows that it is enabled in many other 
major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855338/+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 1959384] [NEW] CONFIG_IO_STRICT_DEVMEM could be enabled

[Laurent Bonnaud]

Public bug reported:

Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access
of active io-memory ranges.

This could impact kernel debugability. In that case, you may reboot with
iomem=relaxed on the kernel command line to override this setting.

This config option is recommended by the Kernel Self Protection
Project[1] and a 2019 study performed by Capsule 8 shows that it is
enabled in many other major distro kernels[2].

[1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
[2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

In Ubuntu impish:

$ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
/boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set

In Debian 11:

$ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
/boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y
/boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y

In Debian sid:

$ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
/boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y
/boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y

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

Title:
  CONFIG_IO_STRICT_DEVMEM could be enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace
  access of active io-memory ranges.

  This could impact kernel debugability. In that case, you may reboot with
  iomem=relaxed on the kernel command line to override this setting.

  This config option is recommended by the Kernel Self Protection
  Project[1] and a 2019 study performed by Capsule 8 shows that it is
  enabled in many other major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

  In Ubuntu impish:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set

  In Debian 11:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y

  In Debian sid:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959384/+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 1912509] Re: usci_acpi USBC000:00: PPM init failed (-110)

[Laurent Bonnaud]

** Tags added: hirsute impish

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

Title:
  usci_acpi USBC000:00: PPM init failed (-110)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting with kernel 5.8.0-38-generic on my Asus Tuf 15 with 2 NVMe 
drives I get:
  usci_acpi USBC000:00: PPM init failed (-110) and the laptop freezes.

  kernel 5.4.0-26-generic usually boots (but get an occasional freeze).

  Since I cannot boot in the 5.8 kernel I cannot file the bug with that
  kernel running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vincent1381 F pulseaudio
   /dev/snd/controlC0:  vincent1381 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 20 17:28:23 2021
  InstallationDate: Installed on 2021-01-20 (0 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LI_FX506LI
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=74589408-5655-4728-b040-86c06177a989 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX506LI.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX506LI
  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.:bvrFX506LI.307:bd12/17/2020:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LI_FX506LI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ASUS TUF Gaming F15
  dmi.product.name: ASUS TUF Gaming F15 FX506LI_FX506LI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912509/+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 1943144] [NEW] low performance when using Zoom client compared to linux-generic 5.4.0.x

[Laurent CREPET]

Public bug reported:

Hi,

Recently, I got kernel linux-generic-hwe-20.04 installed, so 5.11.0.x.
Not sure if I intended to, as I already tested when it was based on
5.8.x, but got the same issue... So, well, as many, I use Zoom client
(latest deb file downloaded from Zoom site) on the following laptop:

Manufacturer: Dell Inc.
Product Name: Latitude 7400
CPU: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz

With linux-generic-hwe-20.04 based on 5.8.x, I noticed a huge increase
of CPU used by Zoom (just looking at top), sometimes having 350% when
someones was sharing screen.

With linux-generic-hwe-20.04 based on 5.11. the CPU usage seems correct,
but the load average get doubled after a moment, and the system becomes
far less usable.

Going back to linux-kernel 5.4.0-84-generic, and performance is stable, even 
without thinking about
changing the CPU governor to performance.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-generic-hwe-20.04 5.11.0.34.36~20.04.13
ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
Uname: Linux 5.4.0-84-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep  9 15:28:58 2021
InstallationDate: Installed on 2021-02-09 (211 days ago)
InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
SourcePackage: linux-meta-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-meta-hwe-5.11 (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-meta-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1943144

Title:
  low performance when using Zoom client compared to linux-generic
  5.4.0.x

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

Bug description:
  Hi,

  Recently, I got kernel linux-generic-hwe-20.04 installed, so 5.11.0.x.
  Not sure if I intended to, as I already tested when it was based on
  5.8.x, but got the same issue... So, well, as many, I use Zoom client
  (latest deb file downloaded from Zoom site) on the following laptop:

  Manufacturer: Dell Inc.
  Product Name: Latitude 7400
  CPU: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz

  With linux-generic-hwe-20.04 based on 5.8.x, I noticed a huge increase
  of CPU used by Zoom (just looking at top), sometimes having 350% when
  someones was sharing screen.

  With linux-generic-hwe-20.04 based on 5.11. the CPU usage seems
  correct, but the load average get doubled after a moment, and the
  system becomes far less usable.

  Going back to linux-kernel 5.4.0-84-generic, and performance is stable, even 
without thinking about
  changing the CPU governor to performance.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-generic-hwe-20.04 5.11.0.34.36~20.04.13
  ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  9 15:28:58 2021
  InstallationDate: Installed on 2021-02-09 (211 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  SourcePackage: linux-meta-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.11/+bug/1943144/+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 1903920] Re: Warning message about cryptsetup during boot

[Laurent Dinclaux]

Upgrades to 21.04 (from a 20.04 fresh install) and the warning is still
showing up

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

Title:
  Warning message about cryptsetup during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that since upgrade to 20.04.1 (from 18.04), a warning
  message appears during boot: "cryptsetup: WARNING: Option 'size'
  missing in crypttab for plain dm-crypt mapping cryptswap1. Please read
  /usr/share/doc/cryptsetup-initramfs/README.initramfs.gz and add the
  correct 'size' option to your crypttab(5).".

  AFAICT, there is no problem however. I use ecryptfs to encrypt my home
  directory but I don't think it's related (since the message is related
  to swap). This message used to appear during updates under 18.04 but I
  never paid attention to it. I probably use the same setup since 16.04.

  Others have reported the problem
  (https://askubuntu.com/questions/1109463, https://medium.com/@anirudha
  /fixing-cryptsetup-wating-for-encrypted-source-device-swapfile-error-
  on-linux-boot-ubuntu-20-04-5483e0dcf9e9). From what I read:

    - The answers indicate to edit /etc/crypttab and add a value for size but I 
don't know what value to use.
    - It seems that before 20.04, just editing /etc/crypttab was enough but 
some users say that they need to manually regenerate the initramfs image after 
each update which is boring.

  I have asked the question at
  https://answers.launchpad.net/ubuntu/+question/693615 and @bernard010
  suggested to open a bug report.

  I have found anything worth in dmesg though.

  As I said everything seems fine (boot proceeds normally, I can use the
  computer) but I expect that there is a way to permanently make this
  warning disappear.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-53-generic 5.4.0-53.59
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2322 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 11 23:02:47 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-06 (1405 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP EliteBook 2570p
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic 
root=UUID=74d77edf-b4b7-4815-865f-b7602f3396b4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-10-04 (38 days ago)
  dmi.bios.date: 02/01/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ISB Ver. F.40
  dmi.board.name: 17DF
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 61.21
  dmi.chassis.asset.tag: CNU3229ST9
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ISBVer.F.40:bd02/01/2013:svnHewlett-Packard:pnHPEliteBook2570p:pvrA1029C1102:rvnHewlett-Packard:rn17DF:rvrKBCVersion61.21:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 2570p
  dmi.product.sku: C9S65EC#ABF
  dmi.product.version: A1029C1102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903920/+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 1912509] Re: usci_acpi USBC000:00: PPM init failed (-110)

[Laurent Bonnaud]

My system displays the same error message:

 - hardware: TUXEDO InfinityBook S 15 Gen6
 - kernel: mainline 5.11.14

It has only one NVMe drive and no Nvidia GPU.

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

Title:
  usci_acpi USBC000:00: PPM init failed (-110)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting with kernel 5.8.0-38-generic on my Asus Tuf 15 with 2 NVMe 
drives I get:
  usci_acpi USBC000:00: PPM init failed (-110) and the laptop freezes.

  kernel 5.4.0-26-generic usually boots (but get an occasional freeze).

  Since I cannot boot in the 5.8 kernel I cannot file the bug with that
  kernel running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vincent1381 F pulseaudio
   /dev/snd/controlC0:  vincent1381 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 20 17:28:23 2021
  InstallationDate: Installed on 2021-01-20 (0 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LI_FX506LI
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=74589408-5655-4728-b040-86c06177a989 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX506LI.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX506LI
  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.:bvrFX506LI.307:bd12/17/2020:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LI_FX506LI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ASUS TUF Gaming F15
  dmi.product.name: ASUS TUF Gaming F15 FX506LI_FX506LI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912509/+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 1920784] Re: qemu-system-ppc64le fails with kvm acceleration

[Laurent Vivier]

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

Title:
  qemu-system-ppc64le fails with kvm acceleration

Status in QEMU:
  New
Status in The Ubuntu-power-systems project:
  New
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  (Suspected glibc issue!)

  qemu-system-ppc64(le) fails when invoked with kvm acceleration with
  error "illegal instruction"

  > qemu-system-ppc64(le) -M pseries,accel=kvm

  Illegal instruction (core dumped)

  In dmesg:

  Facility 'SCV' unavailable (12), exception at 0x7624f8134c0c,
  MSR=9280f033

  
  Version-Release number of selected component (if applicable):
  qemu 5.2.0 
  Linux kernel 5.11
  glibc 2.33
  all latest updates as of submitting the bug report

  How reproducible:
  Always

  Steps to Reproduce:
  1. Run qemu with kvm acceleration

  Actual results:
  Illegal instruction

  Expected results:
  Normal VM execution

  Additional info:
  The machine is a Raptor Talos II Lite with a Sforza V1 8-core, but was also 
observed on a Raptor Blackbird with the same processor.

  This was also observed on Fedora 34 beta, which uses glibc 2.33
  Also tested on ArchPOWER (unofficial port of Arch Linux for ppc64le) with 
glibc 2.33
  Fedora 33 and Ubuntu 20.10, both using glibc 2.32 do not have this issue, and 
downgrading the Linux kernel from 5.11 to 5.4 LTS on ArchPOWER solved the 
problem. Kernel 5.9 and 5.10 have the same issue when combined with glibc2.33

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: qemu-system 1:5.2+dfsg-6ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic ppc64le
  .sys.firmware.opal.msglog: Error: [Errno 13] Permission denied: 
'/sys/firmware/opal/msglog'
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: ppc64el
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Mar 22 14:48:39 2021
  InstallationDate: Installed on 2021-03-22 (0 days ago)
  InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Alpha ppc64el 
(20210321)
  KvmCmdLine: COMMAND STAT  EUID  RUID PIDPPID %CPU COMMAND
  ProcKernelCmdLine: root=UUID=f3d03315-0944-4a02-9c87-09c00eba9fa1 ro
  ProcLoadAvg: 1.20 0.73 0.46 1/1054 6071
  ProcSwaps:
   Filename TypeSizeUsed
Priority
   /swap.img   file 8388544 0   
-2
  ProcVersion: Linux version 5.11.0-11-generic (buildd@bos02-ppc64el-002) (gcc 
(Ubuntu 10.2.1-20ubuntu1) 10.2.1 20210220, GNU ld (GNU Binutils for Ubuntu) 
2.36.1) #12-Ubuntu SMP Mon Mar 1 19:26:20 UTC 2021
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  acpidump:
   
  cpu_cores: Number of cores present = 8
  cpu_coreson: Number of cores online = 8
  cpu_smt: SMT=4

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1920784/+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 1898301] [NEW] Since my upgrade to 20.04 my intel 9462 wifi card can't be mounted

[Laurent-soulet]

Public bug reported:

I have made the upgrade from 18.04 to 20.04 since my wifi card raise an
error during the boot and is no longer detected.

➜  ~ dmesg | grep iwl
[8.037224] Loading modules backported from iwlwifi
[8.037225] iwlwifi-stack-public:master:8794:f51dd362
[8.129071] iwlwifi :00:14.3: WRT: Overriding region id 1
[8.129073] iwlwifi :00:14.3: WRT: Overriding region id 2
[8.129074] iwlwifi :00:14.3: WRT: Overriding region id 3
[8.129075] iwlwifi :00:14.3: WRT: Overriding region id 4
[8.129076] iwlwifi :00:14.3: WRT: Overriding region id 6
[8.129077] iwlwifi :00:14.3: WRT: Overriding region id 8
[8.129078] iwlwifi :00:14.3: WRT: Overriding region id 9
[8.129079] iwlwifi :00:14.3: WRT: Overriding region id 10
[8.129080] iwlwifi :00:14.3: WRT: Overriding region id 11
[8.129080] iwlwifi :00:14.3: WRT: Overriding region id 15
[8.129081] iwlwifi :00:14.3: WRT: Overriding region id 16
[8.129082] iwlwifi :00:14.3: WRT: Overriding region id 18
[8.129083] iwlwifi :00:14.3: WRT: Overriding region id 19
[8.129087] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM
[8.129088] iwlwifi :00:14.3: Found debug configuration: 0
[8.129421] iwlwifi :00:14.3: loaded firmware version 46.6bf1df06.0 
9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm
[8.169443] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9462, 
REV=0x318
[9.203265] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x0, CPU2 Status: 0x0
[9.451146] iwlwifi :00:14.3: Not valid error log pointer 0x for 
Init uCode
[9.451160] iwlwifi :00:14.3: Fseq Registers:
[9.451168] iwlwifi :00:14.3: 0xBFDB4F7D | FSEQ_ERROR_CODE
[9.451176] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
[9.451184] iwlwifi :00:14.3: 0x7BFDEDBF | FSEQ_CNVIO_INIT_VERSION
[9.451193] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
[9.451201] iwlwifi :00:14.3: 0xB200CDD2 | FSEQ_TOP_CONTENT_VERSION
[9.451209] iwlwifi :00:14.3: 0x49441488 | FSEQ_ALIVE_TOKEN
[9.451218] iwlwifi :00:14.3: 0x7A4BFC3D | FSEQ_CNVI_ID
[9.451226] iwlwifi :00:14.3: 0x4382210F | FSEQ_CNVR_ID
[9.451234] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
[9.451275] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP
[9.451349] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[9.451423] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[9.451432] iwlwifi :00:14.3: Failed to start INIT ucode: -110
[9.464970] iwlwifi :00:14.3: Failed to run INIT ucode: -110
➜  ~ 

linux-firmware/focal-updates,focal-updates,now 1.187.3 all [installed]

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

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

Title:
  Since my upgrade to 20.04 my intel 9462 wifi card can't be mounted

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I have made the upgrade from 18.04 to 20.04 since my wifi card raise
  an error during the boot and is no longer detected.

  ➜  ~ dmesg | grep iwl
  [8.037224] Loading modules backported from iwlwifi
  [8.037225] iwlwifi-stack-public:master:8794:f51dd362
  [8.129071] iwlwifi :00:14.3: WRT: Overriding region id 1
  [8.129073] iwlwifi :00:14.3: WRT: Overriding region id 2
  [8.129074] iwlwifi :00:14.3: WRT: Overriding region id 3
  [8.129075] iwlwifi :00:14.3: WRT: Overriding region id 4
  [8.129076] iwlwifi :00:14.3: WRT: Overriding region id 6
  [8.129077] iwlwifi :00:14.3: WRT: Overriding region id 8
  [8.129078] iwlwifi :00:14.3: WRT: Overriding region id 9
  [8.129079] iwlwifi :00:14.3: WRT: Overriding region id 10
  [8.129080] iwlwifi :00:14.3: WRT: Overriding region id 11
  [8.129080] iwlwifi :00:14.3: WRT: Overriding region id 15
  [8.129081] iwlwifi :00:14.3: WRT: Overriding region id 16
  [8.129082] iwlwifi :00:14.3: WRT: Overriding region id 18
  [8.129083] iwlwifi :00:14.3: WRT: Overriding region id 19
  [8.129087] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM
  [8.129088] iwlwifi :00:14.3: Found debug configuration: 0
  [8.129421] iwlwifi :00:14.3: loaded firmware version 46.6bf1df06.0 
9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm
  [8.169443] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9462, 
REV=0x318
  [9.203265] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x0, CPU2 Status: 
0x0
  [9.451146] iwlwifi :00:14.3: Not valid error log pointer 0x 
for Init uCode
  [9.451160] iwlwifi :00:14.3: Fseq Registers:
  [9.451168] iwlwifi :00:14.3: 0xBFDB4F7D | FSEQ_ERROR_CODE
  [9.451176] i