[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 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 

[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:

[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 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 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: 

[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 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 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 1857775] Re: dmesg/syslog flooded with: iwlwifi 0000:00:14.3: Unhandled alg: 0x707

[Laurent Bonnaud]

** Bug watch added: Linux Kernel Bug Tracker #205121
   https://bugzilla.kernel.org/show_bug.cgi?id=205121

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=205121
   Importance: Unknown
   Status: Unknown

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

Title:
  dmesg/syslog flooded with: iwlwifi :00:14.3: Unhandled alg: 0x707

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The syslog/dmesg is flooded with 'iwlwifi :00:14.3: Unhandled alg:
  0x707' messages on a Lenovo ThinkPad L390 Yoga

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04
  Codename: focal

  $ uname -a
  Linux gir 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux


  
  $ dmesg | grep iwl
  [   14.460824] iwlwifi :00:14.3: enabling device ( -> 0002)
  [   14.471663] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM
  [   14.471664] iwlwifi :00:14.3: Found debug configuration: 0
  [   14.471939] iwlwifi :00:14.3: loaded firmware version 46.6bf1df06.0 
op_mode iwlmvm
  [   14.549040] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 
160MHz, REV=0x318
  [   14.556875] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [   14.557465] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware 
monitor.
  [   14.602284] iwlwifi :00:14.3: base HW address: XX:XX:XX:XX:XX:XX
  [   14.670762] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
  [   14.745029] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  [   15.713257] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [   15.830577] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [   15.897113] iwlwifi :00:14.3: FW already configured (0) - 
re-configuring
  [   19.280089] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   19.379365] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   19.431493] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   19.437474] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   19.571333] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   19.821412] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   20.026492] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   20.072448] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   20.273403] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   20.350055] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   20.378102] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   20.438052] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   20.542372] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   21.072113] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   21.388731] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   21.458073] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   21.458089] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   21.775624] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   21.776376] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   21.777158] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   21.777163] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   21.777813] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   21.779256] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   21.779260] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   21.826260] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   22.112026] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   22.177452] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   22.381009] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   22.439389] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   23.379986] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   23.380009] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   23.380018] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   23.380025] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   23.380032] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   23.380038] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   23.381171] iwlwifi :00:14.3: Unhandled alg: 0x707
  [   23.381185] iwlwifi :00:14.3: Unhandled alg: 0x707

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

-- 
Mailing list: https://launchpad.net/~kernel-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]

The problem is still there in Ubuntu 20.04/focal:

$ grep CONFIG_IO_STRICT_DEVMEM /boot/config-5.*
/boot/config-5.4.0-21-generic:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-5.4.0-21-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-5.6.3-050603-generic:# CONFIG_IO_STRICT_DEVMEM is not set

Committing a fix is good, but releasing it is even better :>.


** Tags added: focal

-- 
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 Committed

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 1863627] Re: Intel Dual Band Wireless AC 9560 [8086:9df0] subsystem id [8086:0034] kernel oops in __iwl_mvm_mac_stop

[Laurent Bonnaud]

** Bug watch added: Linux Kernel Bug Tracker #204785
   https://bugzilla.kernel.org/show_bug.cgi?id=204785

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=204785
   Importance: Unknown
   Status: Unknown

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

Title:
  Intel Dual Band Wireless AC 9560 [8086:9df0] subsystem id [8086:0034]
  kernel oops in __iwl_mvm_mac_stop

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting, i always get this oops:

  
  [   31.477399] iwlwifi :00:14.3: RF_KILL bit toggled to disable radio.
  [   31.477400] iwlwifi :00:14.3: reporting RF_KILL (radio disabled)
  [   31.490515] [ cut here ]
  [   31.490516] UMAC scan UID 0 status was not cleaned
  [   31.490540] WARNING: CPU: 3 PID: 954 at 
drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c:1434 
__iwl_mvm_mac_stop+0x129/0x130 [iwlmvm]
  [   31.490540] Modules linked in: cmac nvidia_modeset(PO) snd_usb_audio 
snd_usbmidi_lib bnep aufs uvcvideo videobuf2_vmalloc videobuf2_memops overlay 
videobuf2_v4l2 videobuf2_common videodev mc btusb btrtl btbcm btintel bluetooth 
ecdh_generic ecc bbswitch(OE) binfmt_misc nls_iso8859_1 sof_pci_dev 
snd_sof_intel_hda_common snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc 
snd_sof x86_pkg_temp_thermal snd_sof_xtensa_dsp intel_powerclamp snd_soc_skl 
snd_soc_hdac_hda snd_hda_codec_hdmi snd_hda_ext_core coretemp snd_soc_skl_ipc 
snd_soc_sst_ipc iwlmvm snd_soc_sst_dsp kvm_intel snd_soc_acpi_intel_match 
snd_soc_acpi mac80211 kvm snd_soc_core snd_hda_codec_realtek snd_compress 
irqbypass ac97_bus snd_hda_codec_generic libarc4 nvidia(PO) snd_pcm_dmaengine 
intel_cstate mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event 
snd_rawmidi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_pcm 
iwlwifi intel_rapl_perf thinkpad_acpi joydev input_leds 
processor_thermal_device idma64 nvram
  [   31.490556]  intel_rapl_common ucsi_acpi mei_me serio_raw ledtrig_audio 
typec_ucsi ipmi_devintf intel_wmi_thunderbolt wmi_bmof snd_seq_device 
ipmi_msghandler cfg80211 mei virt_dma intel_soc_dts_iosf intel_pch_thermal 
typec snd_timer snd int3403_thermal soundcore int340x_thermal_zone 
int3400_thermal mac_hid acpi_thermal_rel acpi_pad sch_fq_codel parport_pc ppdev 
lp parport ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid i915 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_algo_bit drm_kms_helper 
syscopyarea aesni_intel sysfillrect sysimgblt fb_sys_fops aes_x86_64 
crypto_simd drm cryptd glue_helper nvme psmouse e1000e i2c_i801 sdhci_pci 
nvme_core thunderbolt cqhci intel_lpss_pci sdhci intel_lpss wmi 
pinctrl_cannonlake video pinctrl_intel [last unloaded: nvidia_modeset]
  [   31.490571] CPU: 3 PID: 954 Comm: kworker/3:3 Tainted: P   OE 
5.3.0-29-generic #31-Ubuntu
  [   31.490572] Hardware name: LENOVO 20N3S1HU00/20N3S1HU00, BIOS N2IET77W 
(1.55 ) 10/17/2019
  [   31.490587] Workqueue: events cfg80211_rfkill_sync_work [cfg80211]
  [   31.490591] RIP: 0010:__iwl_mvm_mac_stop+0x129/0x130 [iwlmvm]
  [   31.490592] Code: 9b 04 00 00 74 0e 42 c7 84 a3 ec 1d 00 00 00 00 00 00 eb 
c0 44 89 e6 48 c7 c7 20 65 24 c2 c6 05 41 9b 04 00 01 e8 02 7d c9 e0 <0f> 0b eb 
d8 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55
  [   31.490592] RSP: 0018:b8e0c0febc48 EFLAGS: 00010286
  [   31.490593] RAX:  RBX: 937ac5bf1e28 RCX: 
0006
  [   31.490594] RDX: 0007 RSI: 0082 RDI: 
937acc2d7440
  [   31.490594] RBP: b8e0c0febc58 R08: 0498 R09: 
0004
  [   31.490594] R10:  R11: 0001 R12: 

  [   31.490595] R13: 937ac5bf1e90 R14: 937ac5bf1e28 R15: 
937ac5bf3290
  [   31.490595] FS:  () GS:937acc2c() 
knlGS:
  [   31.490596] CS:  0010 DS:  ES:  CR0: 80050033
  [   31.490596] CR2: 5597e8a3b4e8 CR3: 00038d00a001 CR4: 
003606e0
  [   31.490597] Call Trace:
  [   31.490601]  iwl_mvm_mac_stop+0xed/0x110 [iwlmvm]
  [   31.490616]  drv_stop+0x39/0x100 [mac80211]
  [   31.490625]  ieee80211_stop_device+0x46/0x50 [mac80211]
  [   31.490632]  ieee80211_do_stop+0x583/0x810 [mac80211]
  [   31.490639]  ieee80211_stop+0x1a/0x20 [mac80211]
  [   31.490641]  __dev_close_many+0xa5/0x120
  [   31.490641]  dev_close_many+0x91/0x150
  [   31.490642]  dev_close.part.0+0x4a/0x70
  [   31.490643]  dev_close+0x18/0x20
  [   31.490649]  cfg80211_shutdown_all_interfaces+0x77/0xd0 [cfg80211]
  [   31.490653]  cfg80211_rfkill_sync_work+0x2b/0x40 [cfg80211]
  [   31.490655]  process_one_work+0x1db/0x380
  [   31.490656]  worker_thread+0x4d/0x400
  [   31.490657]  kthread+0x104/0x140
  [   31.490658]  ? process_one_work+0x380/0x380
  [   31.490659]  ? 

[Kernel-packages] [Bug 1863627] Re: Intel Dual Band Wireless AC 9560 [8086:9df0] subsystem id [8086:0034] kernel oops in __iwl_mvm_mac_stop

[Laurent Bonnaud]

A similar bug still exists in the mainline 5.5.7 kernel:

[106491.771242] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio.
[106491.771247] iwlwifi :02:00.0: reporting RF_KILL (radio disabled)
[106491.771342] wlan0: deauthenticating from e4:aa:5d:e0:e5:60 by local choice 
(Reason: 3=DEAUTH_LEAVING)
[106491.791040] [ cut here ]
[106491.791042] UMAC scan UID 0 status was not cleaned
[106491.791069] WARNING: CPU: 0 PID: 1588 at 
drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c:1236 
__iwl_mvm_mac_stop+0x14f/0x160 [iwlmvm]
[106491.791069] Modules linked in: ccm iwlmvm mac80211 libarc4 iwlwifi rfcomm 
bnep btusb btrtl btbcm btintel bluetooth ecdh_generic ecc uas usb_storage 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter 
bpfilter bridge stp llc overlay binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 
snd_hda_codec_realtek snd_hda_codec_generic joydev mei_hdcp intel_rapl_msr 
dell_rbtn x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_intel 
snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_rawmidi snd_seq snd_seq_device snd_timer dell_laptop ledtrig_audio 
dell_smm_hwmon uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_common i915 videodev aesni_intel crypto_simd mc cryptd input_leds 
glue_helper serio_raw dell_wmi hid_multitouch
[106491.791094]  intel_wmi_thunderbolt cfg80211 intel_cstate dell_smbios 
intel_rapl_perf dcdbas drm_kms_helper dell_wmi_descriptor wmi_bmof snd drm 
mei_me processor_thermal_device i2c_algo_bit fb_sys_fops ucsi_acpi 
intel_rapl_common syscopyarea soundcore sysfillrect intel_xhci_usb_role_switch 
typec_ucsi mei sysimgblt intel_soc_dts_iosf roles intel_pch_thermal typec 
int3400_thermal mac_hid acpi_thermal_rel intel_hid dell_smo8800 acpi_pad 
int3403_thermal sparse_keymap int340x_thermal_zone sch_fq_codel nf_tables 
nfnetlink kvm_intel kvm parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c usbhid hid_generic 
rtsx_pci_sdmmc nvme e1000e i2c_i801 ahci nvme_core rtsx_pci intel_lpss_pci 
libahci intel_lpss idma64 virt_dma wmi i2c_hid hid video [last unloaded: 
iwlwifi]
[106491.791119] CPU: 0 PID: 1588 Comm: NetworkManager Not tainted 
5.5.7-050507-generic #202002281805
[106491.791120] Hardware name: Dell Inc. Latitude 5590/0VYDFF, BIOS 1.11.1 
09/19/2019
[106491.791126] RIP: 0010:__iwl_mvm_mac_stop+0x14f/0x160 [iwlmvm]
[106491.791128] Code: 71 04 00 00 74 0e 42 c7 84 a3 0c 18 00 00 00 00 00 00 eb 
be 44 89 e6 48 c7 c7 f8 a7 48 c1 c6 05 57 71 04 00 01 e8 86 5a a5 df <0f> 0b eb 
d8 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00
[106491.791129] RSP: 0018:adc28161fc20 EFLAGS: 00010282
[106491.791130] RAX:  RBX: 8f3255719e88 RCX: 
0007
[106491.791131] RDX: 0007 RSI: 0092 RDI: 
8f325e419c80
[106491.791131] RBP: adc28161fc38 R08: 0d35 R09: 
0004
[106491.791132] R10:  R11: 0001 R12: 

[106491.791133] R13: 8f325571ad08 R14: 8f3255719e88 R15: 
8f3255718fe0
[106491.791134] FS:  7ffa630b2bc0() GS:8f325e40() 
knlGS:
[106491.791135] CS:  0010 DS:  ES:  CR0: 80050033
[106491.791136] CR2: 55de033475a8 CR3: 0001c7078003 CR4: 
003606f0
[106491.791137] Call Trace:
[106491.791144]  iwl_mvm_mac_stop+0xbb/0xe0 [iwlmvm]
[106491.791160]  drv_stop+0x39/0x110 [mac80211]
[106491.791177]  ieee80211_stop_device+0x46/0x50 [mac80211]
[106491.791190]  ieee80211_do_stop+0x58e/0x830 [mac80211]
[106491.791202]  ieee80211_stop+0x1a/0x20 [mac80211]
[106491.791205]  __dev_close_many+0xa2/0x110
[106491.791207]  dev_close_many+0x85/0x130
[106491.791209]  dev_close.part.0+0x44/0x70
[106491.791211]  dev_close+0x18/0x20
[106491.791225]  cfg80211_shutdown_all_interfaces+0x77/0xd0 [cfg80211]
[106491.791233]  cfg80211_rfkill_set_block+0x26/0x30 [cfg80211]
[106491.791235]  rfkill_set_block+0x9b/0x150
[106491.791237]  rfkill_fop_write+0x136/0x1e0
[106491.791240]  __vfs_write+0x1b/0x40
[106491.791241]  vfs_write+0xb9/0x1a0
[106491.791243]  ksys_write+0xb1/0xe0
[106491.791245]  __x64_sys_write+0x1a/0x20
[106491.791247]  do_syscall_64+0x57/0x1b0
[106491.791250]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[106491.791251] RIP: 0033:0x7ffa646eb27f
[106491.791253] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 19 fd ff ff 48 
8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 4c fd ff ff 48
[106491.791254] RSP: 002b:7fff183ea710 EFLAGS: 0293 ORIG_RAX: 
0001
[106491.791255] RAX: ffda RBX: 55dcc05fdf85 RCX: 

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

[Laurent Bonnaud]

Here is an ACPI dump on a Dell Latitude 5590 with kernel 5.5.3.


** Attachment added: "ACPI dump"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806437/+attachment/5327674/+files/acpi-dump.bin

-- 
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:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

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 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Laurent Bonnaud]

** Tags added: disco eoan

-- 
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:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

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 1785788] Re: NFS breaks after wake from suspend

[Laurent Bonnaud]

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

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

** Also affects: linux (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1552037
   Importance: Unknown
   Status: Unknown

** Bug watch added: bugs.centos.org/ #15218
   https://bugs.centos.org/view.php?id=15218

** Also affects: linux (CentOS) via
   https://bugs.centos.org/view.php?id=15218
   Importance: Unknown
   Status: Unknown

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

Title:
  NFS breaks after wake from suspend

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in CentOS:
  Unknown
Status in linux package in Debian:
  Unknown
Status in linux package in Fedora:
  Unknown

Bug description:
  Hello,

  I am observing all symptoms of debian bug 898060 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898060) on ubuntu bionic 
4.15.0-23-generic x86_64 clients
  with a Centos7 NFS server (3.10.0-693.21.1.el7.x86_64).

  After a wake from suspend the server always logs
  kernel: NFSD: client 2001:638:redacted testing state ID with incorrect client 
ID
  which is not observed with ubuntu 16.04 (kernel 4.4) clients. Sporadically 
after wake from suspend (takes days to weeks to trigger) the server logs are 
flooded with messages of the type
  kernel: RPC request reserved 84 but used 276
  and NFS on the client does not work any more. This also has not been observed 
with our 20 or so ubuntu 16.04 NFS clients in the last two years.

  Rebooting the client appears to stop the log flooding on the server
  and NFS works normally after the reboot. Remark: systemd hangs during
  shutdown, presumably waiting for the NFS mount to stop, the power
  button is the only remaining option.

  I will upgrade to the latest bionic kernel later and try to trigger
  this again.

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

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

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

[Laurent Bonnaud]

I also see fq_codel used as default:

# cat /proc/sys/net/core/default_qdisc
fq_codel

# ip addr
[...]
2: eth0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000


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

Title:
  devel: consider fq_codel as the default qdisc for networking

Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Debian:
  New

Bug description:
  This was raised on the kernel-team@ mailing list, we should look at
  this if other distros are starting to move.

  ===

  Date: Tue, 24 Mar 2015 10:54:37 -0700 
 
  From: Dave Taht  
 
  To: Joseph Salisbury  
 
  Cc: Kernel Team , ubuntu-de...@lists.ubuntu.com 
 
  Subject: Re: Minutes from the Ubuntu Kernel Team meeting, 2015-03-24  
 

 
  I must confess I had hoped ubuntu would adopt fq_codel as the default 
 
  qdisc in this go-around. It is still not quite part of fedora´s   
 
  default either, but is now in arch, (and nearly everyone else 
 
  downstream from systemd), and has long been the default in openwrt,   
 
  and at this point, just requires a single sysctl to enable.   
 

 
  It certainly could use more widespread testing, perhaps in the next release?  
 

 
  d@nuc-client:~$ cat /etc/sysctl.d/10-bufferbloat.conf 
 
  net.core.default_qdisc=fq_codel

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

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

[Kernel-packages] [Bug 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted

[Laurent Bonnaud]

The error messages about the sap-server are not there any longer in Ubuntu 
17.10.
Thanks for the fix!


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

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

Title:
  Sap driver initialization failed, sap-server: Operation not permitted

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez package in Debian:
  New

Bug description:
  Hi,

  here are are messages from the bluetooth daemon:

  $ journalctl -b | grep bluetoothd
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 
initialized
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for 
"Service Changed" characteristic
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed.
  Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted 
(1)

  There are at least 2 errors concerning:
   - handles
   - Sap driver/server

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct  2 09:59:43 2016
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency 
root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:85:DE:57:27:6F  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:1974 acl:0 sco:0 events:132 errors:0
TX bytes:6033 acl:0 sco:0 commands:132 errors:0

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

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

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

[Laurent Bonnaud]

** Package changed: systemd (Debian) => linux (Debian)

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

Title:
  devel: consider fq_codel as the default qdisc for networking

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  New

Bug description:
  This was raised on the kernel-team@ mailing list, we should look at
  this if other distros are starting to move.

  ===

  Date: Tue, 24 Mar 2015 10:54:37 -0700 
 
  From: Dave Taht  
 
  To: Joseph Salisbury  
 
  Cc: Kernel Team , ubuntu-de...@lists.ubuntu.com 
 
  Subject: Re: Minutes from the Ubuntu Kernel Team meeting, 2015-03-24  
 

 
  I must confess I had hoped ubuntu would adopt fq_codel as the default 
 
  qdisc in this go-around. It is still not quite part of fedora´s   
 
  default either, but is now in arch, (and nearly everyone else 
 
  downstream from systemd), and has long been the default in openwrt,   
 
  and at this point, just requires a single sysctl to enable.   
 

 
  It certainly could use more widespread testing, perhaps in the next release?  
 

 
  d@nuc-client:~$ cat /etc/sysctl.d/10-bufferbloat.conf 
 
  net.core.default_qdisc=fq_codel

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

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

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

[Laurent Bonnaud]

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

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

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

Title:
  devel: consider fq_codel as the default qdisc for networking

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Unknown

Bug description:
  This was raised on the kernel-team@ mailing list, we should look at
  this if other distros are starting to move.

  ===

  Date: Tue, 24 Mar 2015 10:54:37 -0700 
 
  From: Dave Taht  
 
  To: Joseph Salisbury  
 
  Cc: Kernel Team , ubuntu-de...@lists.ubuntu.com 
 
  Subject: Re: Minutes from the Ubuntu Kernel Team meeting, 2015-03-24  
 

 
  I must confess I had hoped ubuntu would adopt fq_codel as the default 
 
  qdisc in this go-around. It is still not quite part of fedora´s   
 
  default either, but is now in arch, (and nearly everyone else 
 
  downstream from systemd), and has long been the default in openwrt,   
 
  and at this point, just requires a single sysctl to enable.   
 

 
  It certainly could use more widespread testing, perhaps in the next release?  
 

 
  d@nuc-client:~$ cat /etc/sysctl.d/10-bufferbloat.conf 
 
  net.core.default_qdisc=fq_codel

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

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

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

[Laurent Bonnaud]

** Tags added: artful bionic

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

Title:
  devel: consider fq_codel as the default qdisc for networking

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was raised on the kernel-team@ mailing list, we should look at
  this if other distros are starting to move.

  ===

  Date: Tue, 24 Mar 2015 10:54:37 -0700 
 
  From: Dave Taht  
 
  To: Joseph Salisbury  
 
  Cc: Kernel Team , ubuntu-de...@lists.ubuntu.com 
 
  Subject: Re: Minutes from the Ubuntu Kernel Team meeting, 2015-03-24  
 

 
  I must confess I had hoped ubuntu would adopt fq_codel as the default 
 
  qdisc in this go-around. It is still not quite part of fedora´s   
 
  default either, but is now in arch, (and nearly everyone else 
 
  downstream from systemd), and has long been the default in openwrt,   
 
  and at this point, just requires a single sysctl to enable.   
 

 
  It certainly could use more widespread testing, perhaps in the next release?  
 

 
  d@nuc-client:~$ cat /etc/sysctl.d/10-bufferbloat.conf 
 
  net.core.default_qdisc=fq_codel

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

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

[Kernel-packages] [Bug 1746971] [NEW] Please enable PAGE_POISONING

[Laurent Bonnaud]

Public bug reported:

Hi,

page poising is currently disabled in Ubuntu kernels:

$ grep PAGE_POISON /boot/config-4.13.0-32-generic
# CONFIG_PAGE_POISONING is not set

It is also disabled in mainline kernels:

$ grep PAGE_POISON /boot/config-4.14.16-041416-generic
# CONFIG_PAGE_POISONING is not set

On the contrary, it is enabled in Debian stretch and buster/sid kernels:

# grep PAGE_POISON /boot/config-*
/boot/config-4.9.0-5-amd64:CONFIG_PAGE_POISONING=y
/boot/config-4.9.0-5-amd64:CONFIG_PAGE_POISONING_NO_SANITY=y
/boot/config-4.9.0-5-amd64:# CONFIG_PAGE_POISONING_ZERO is not set

$ grep PAGE_POISON /boot/config-*
/boot/config-4.14.0-3-amd64:CONFIG_PAGE_POISONING=y
/boot/config-4.14.0-3-amd64:CONFIG_PAGE_POISONING_NO_SANITY=y
/boot/config-4.14.0-3-amd64:# CONFIG_PAGE_POISONING_ZERO is not set

It is an interesting kernel hardening feature, so could you please
enable those options in Ubuntu and mainline kernels?

Some background information is here:

  https://outflux.net/blog/archives/2016/09/30/security-things-in-
linux-v4-6/

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-32-generic 4.13.0-32.35
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bonnaudl   3167 F pulseaudio
CurrentDesktop: KDE
Date: Fri Feb  2 09:47:37 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
MachineType: Dell Inc. Latitude E6520
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none 
ecurity=apparmor enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M 
mtrr_chunk_size=128M quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic  N/A
 linux-firmware 1.169.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
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.

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


** Tags: amd64 apport-bug artful

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

Title:
  Please enable PAGE_POISONING

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  page poising is currently disabled in Ubuntu kernels:

  $ grep PAGE_POISON /boot/config-4.13.0-32-generic
  # CONFIG_PAGE_POISONING is not set

  It is also disabled in mainline kernels:

  $ grep PAGE_POISON /boot/config-4.14.16-041416-generic
  # CONFIG_PAGE_POISONING is not set

  On the contrary, it is enabled in Debian stretch and buster/sid
  kernels:

  # grep PAGE_POISON /boot/config-*
  /boot/config-4.9.0-5-amd64:CONFIG_PAGE_POISONING=y
  /boot/config-4.9.0-5-amd64:CONFIG_PAGE_POISONING_NO_SANITY=y
  /boot/config-4.9.0-5-amd64:# CONFIG_PAGE_POISONING_ZERO is not set

  $ grep PAGE_POISON /boot/config-*
  /boot/config-4.14.0-3-amd64:CONFIG_PAGE_POISONING=y
  /boot/config-4.14.0-3-amd64:CONFIG_PAGE_POISONING_NO_SANITY=y
  /boot/config-4.14.0-3-amd64:# CONFIG_PAGE_POISONING_ZERO is not set

  It is an interesting kernel hardening feature, so could you please
  enable those options in Ubuntu and mainline kernels?

  Some background information is here:

https://outflux.net/blog/archives/2016/09/30/security-things-in-
  linux-v4-6/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   3167 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Feb  2 09:47:37 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
  MachineType: Dell Inc. Latitude E6520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none 
ecurity=apparmor enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M 
mtrr_chunk_size=128M quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
 

[Kernel-packages] [Bug 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted

[Laurent Bonnaud]

This bug still exists in zesty:

# journalctl -b | grep bluetoothd
Mar 20 11:29:29 xeelee bluetoothd[1113]: Bluetooth daemon 5.43
Mar 20 11:29:29 xeelee bluetoothd[1113]: Starting SDP server
Mar 20 11:29:29 xeelee bluetoothd[1113]: Bluetooth management interface 1.14 
initialized
Mar 20 11:29:29 xeelee bluetoothd[1113]: Failed to obtain handles for "Service 
Changed" characteristic
Mar 20 11:29:29 xeelee bluetoothd[1113]: Sap driver initialization failed.
Mar 20 11:29:29 xeelee bluetoothd[1113]: sap-server: Operation not permitted (1)
[...]


** Tags added: zesty

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

Title:
  Sap driver initialization failed, sap-server: Operation not permitted

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

Bug description:
  Hi,

  here are are messages from the bluetooth daemon:

  $ journalctl -b | grep bluetoothd
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 
initialized
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for 
"Service Changed" characteristic
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed.
  Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted 
(1)

  There are at least 2 errors concerning:
   - handles
   - Sap driver/server

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct  2 09:59:43 2016
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency 
root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:85:DE:57:27:6F  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:1974 acl:0 sco:0 events:132 errors:0
TX bytes:6033 acl:0 sco:0 commands:132 errors:0

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

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

[Kernel-packages] [Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang

[Laurent Bonnaud]

I have not seen this bug while using mainline kernels from 4.9.1 to
4.9.13 and now 4.10.1.

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

Title:
  kernel messages intel_crtc_wait_for_pending_flips correlate to compiz
  hang

Status in Linux:
  Unknown
Status in System76:
  New
Status in xf86-video-intel:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Debian:
  Confirmed
Status in linux package in Fedora:
  Unknown
Status in linux package in openSUSE:
  Unknown

Bug description:
  I am fairly frequently (maybe once every 2 days) seeing screen
  lockups.  The system is fine, and then screen locks up. mouse is still
  movable and even changes icon based on content under it (ie mouse over
  link changes to pointing hand).  Programs are still running (often
  this occurs during a google hangout, and the hangout, audio and mic
  seem to work fine).

  Today when this happened I had more patience and hit ctrl-alt-f1, and then 
subsequently saw that dmesg had:
  [82218.556025] [ cut here ]
  [82218.556074] WARNING: CPU: 0 PID: 8799 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 
intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]()
  [82218.556095] Modules linked in: xt_conntrack ipt_REJECT overlayfs pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter 
ip_tables x_tables rfcomm bnep binfmt_misc dm_crypt uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core v4l2_common videodev media dm_multipath scsi_dh 
coretemp kvm_intel kvm arc4 joydev iwldvm mac80211 serio_raw btusb bluetooth 
pcmcia 6lowpan_iphc thinkpad_acpi snd_seq_midi snd_seq_midi_event nvram 
snd_hda_codec_conexant snd_hda_codec_generic r852 sm_common lpc_ich nand 
snd_rawmidi nand_ecc nand_bch snd_hda_intel bch nand_ids snd_hda_controller 
snd_hda_codec snd_hwdep mtd snd_seq iwlwifi r592 memstick snd_pcm
  [82218.556112]  yenta_socket pcmcia_rsrc pcmcia_core cfg80211 snd_seq_device 
shpchp snd_timer mei_me mei snd soundcore mac_hid parport_pc ppdev tp_smapi(OE) 
thinkpad_ec(OE) lp parport btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear 
hid_generic usbhid hid psmouse firewire_ohci ahci libahci firewire_core 
sdhci_pci sdhci crc_itu_t i915 wmi e1000e i2c_algo_bit drm_kms_helper video drm 
ptp pps_core pata_acpi [last unloaded: ipmi_msghandler]
  [82218.556114] CPU: 0 PID: 8799 Comm: kworker/0:1 Tainted: GW  OE 
3.16.0-23-generic #30-Ubuntu
  [82218.556115] Hardware name: LENOVO 7417CTO/7417CTO, BIOS 7UET94WW (3.24 ) 
10/17/2012
  [82218.556119] Workqueue: events console_callback
  [82218.556122]  0009 880016a3faf8 8177fcbc 

  [82218.556123]  880016a3fb30 8106fd8d  
880035a5a000
  [82218.556124]  880035948210 880035826800 880035826800 
880016a3fb40
  [82218.556125] Call Trace:
  [82218.556130]  [] dump_stack+0x45/0x56
  [82218.556133]  [] warn_slowpath_common+0x7d/0xa0
  [82218.556135]  [] warn_slowpath_null+0x1a/0x20
  [82218.556153]  [] 
intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]
  [82218.556156]  [] ? prepare_to_wait_event+0x100/0x100
  [82218.556175]  [] intel_crtc_disable_planes+0x33/0x1c0 
[i915]
  [82218.556177]  [] ? __ww_mutex_lock+0x1b/0xb0
  [82218.556196]  [] i9xx_crtc_disable+0x51/0x3f0 [i915]
  [82218.556220]  [] intel_crtc_update_dpms+0x67/0xa0 [i915]
  [82218.556237]  [] intel_connector_dpms+0x59/0x70 [i915]
  [82218.556245]  [] drm_fb_helper_dpms.isra.5+0xc1/0x100 
[drm_kms_helper]
  [82218.556251]  [] drm_fb_helper_blank+0x31/0x90 
[drm_kms_helper]
  [82218.556254]  [] fb_blank+0x57/0xc0
  [82218.556256]  [] fbcon_blank+0xfb/0x300
  [82218.556258]  [] ? __queue_delayed_work+0x182/0x1c0
  [82218.556259]  [] ? try_to_grab_pending+0xa9/0x160
  [82218.556262]  [] ? lock_timer_base.isra.34+0x2b/0x50
  [82218.556264]  [] ? try_to_del_timer_sync+0x4f/0x70
  [82218.556266]  [] do_blank_screen+0x1d3/0x280
  [82218.556267]  [] console_callback+0x68/0x160
  [82218.556269]  [] process_one_work+0x182/0x4e0
  [82218.556270]  [] worker_thread+0x6b/0x6a0
  [82218.556272]  [] ? __schedule+0x39d/0x890
  [82218.556273]  [] ? process_one_work+0x4e0/0x4e0
  [82218.556275]  [] kthread+0xdb/0x100
  [82218.556277]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [82218.556278]  [] ret_from_fork+0x7c/0xb0
  [82218.556280]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [82218.556281] ---[ end trace b9c751133032cf61 ]---

  /var/log/Xorg.0.log had:
  [ 83252.384] (EE) Backtrace:
  [ 83253.063] (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7f80649a0666]
  [ 83253.063] (EE) 1: /usr/bin/X (0x7f80647ea000+0x1ba869) 

[Kernel-packages] [Bug 1486316] Re: lpc_ich: Resource conflict(s) found affecting gpio_ich

[Laurent Bonnaud]

I am still seeing those error messages in mainline kernel 4.10.1.

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

Title:
  lpc_ich: Resource conflict(s) found affecting gpio_ich

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This nearly identical to the following bug:

  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027370). (sorry
  not sure how to make links here)

  however, this is not effecting iTCO_wdt, but is effecting gpio_ich

  ACPI Warning: SystemIO range 0x0828-0x082F conflicts 
with OpRegion 0x0800-0x084F (\PMRG) 
(20150410/utaddress-254)
  [
  ACPI: If an ACPI driver is available for this device, you should use it 
instead of the native driver

  lpc_ich: Resource conflict(s) found affecting gpio_ich

  This error occurs in 15,04 and the latest build of 15.10. i meant to
  post this up with the last report i made but i ended up getting
  distracted. sorry.

  LSB:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  --- 
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   testusr1632 F...m pulseaudio
   /dev/snd/controlC0:  testusr1632 F pulseaudio
   /dev/snd/controlC1:  testusr1632 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=df53ef11-a582-4795-81e6-4666c7ba9eb7
  InstallationDate: Installed on 2015-08-15 (3 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150815.1)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gateway FX6840
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=2244254b-eee5-4fa6-bb16-d4e811b01f42 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.146
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A3
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: FX6840
  dmi.board.vendor: Gateway
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd05/17/2010:svnGateway:pnFX6840:pvr:rvnGateway:rnFX6840:rvr:cvnGateway:ct3:cvr:
  dmi.product.name: FX6840
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1486316] Re: lpc_ich: Resource conflict(s) found affecting gpio_ich

[Laurent Bonnaud]

Axil Therian, could you please tell us the bug number you got when you
reported this upstream?


** Tags added: xenial yakkety

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

Title:
  lpc_ich: Resource conflict(s) found affecting gpio_ich

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This nearly identical to the following bug:

  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027370). (sorry
  not sure how to make links here)

  however, this is not effecting iTCO_wdt, but is effecting gpio_ich

  ACPI Warning: SystemIO range 0x0828-0x082F conflicts 
with OpRegion 0x0800-0x084F (\PMRG) 
(20150410/utaddress-254)
  [
  ACPI: If an ACPI driver is available for this device, you should use it 
instead of the native driver

  lpc_ich: Resource conflict(s) found affecting gpio_ich

  This error occurs in 15,04 and the latest build of 15.10. i meant to
  post this up with the last report i made but i ended up getting
  distracted. sorry.

  LSB:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  --- 
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   testusr1632 F...m pulseaudio
   /dev/snd/controlC0:  testusr1632 F pulseaudio
   /dev/snd/controlC1:  testusr1632 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=df53ef11-a582-4795-81e6-4666c7ba9eb7
  InstallationDate: Installed on 2015-08-15 (3 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150815.1)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gateway FX6840
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=2244254b-eee5-4fa6-bb16-d4e811b01f42 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.146
  RfKill:
   
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A3
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: FX6840
  dmi.board.vendor: Gateway
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd05/17/2010:svnGateway:pnFX6840:pvr:rvnGateway:rnFX6840:rvr:cvnGateway:ct3:cvr:
  dmi.product.name: FX6840
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start

[Laurent Bonnaud]

On Ubuntu 16.10 with this bluez package:

Package: bluez
Version: 5.41-0ubuntu3with 

I no longer see the "Not enough handles to register service" messages.


** Tags added: xenial

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

Title:
  15:10 and 16.04: bluetoothd reports "Not enough handles to register
  service" at start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

-- 
Mailing list: https://launchpad.net/~kernel-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]

I am still seeing this error with the 4.10.1-041001-generic mainline
kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

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 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted

[Laurent Bonnaud]

According to this:

  https://raspberrypi.stackexchange.com/questions/40839/sap-error-on-
bluetooth-service-status

the error messages about SAP can be avoided by starting bluetoothd with
the "--noplugin=sap" option.

Since SAP is probably of little use in Ubuntu and since it does not work
anyway, how about disabling it by default?


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

** Also affects: bluez (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803265
   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/1629632

Title:
  Sap driver initialization failed, sap-server: Operation not permitted

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

Bug description:
  Hi,

  here are are messages from the bluetooth daemon:

  $ journalctl -b | grep bluetoothd
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 
initialized
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for 
"Service Changed" characteristic
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed.
  Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted 
(1)

  There are at least 2 errors concerning:
   - handles
   - Sap driver/server

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct  2 09:59:43 2016
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency 
root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:85:DE:57:27:6F  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:1974 acl:0 sco:0 events:132 errors:0
TX bytes:6033 acl:0 sco:0 commands:132 errors:0

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

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

[Kernel-packages] [Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang

[Laurent Bonnaud]

Here is another data point:
 - kernel: linux-image-4.8.12-040812-generic (Ubuntu mainline kernel)
 - CPU/GPU : Core i7-2640M

This kind of event is quite rare with mainline kernels (I cannot say the
same of Ubuntu kernels and that's why I use mainline kernels).

[231716.438851] [ cut here ]
[231716.438881] WARNING: CPU: 0 PID: 1334 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:3906 
intel_atomic_commit+0x559/0x560 [i915]
[231716.438882] Removing stuck page flip
[231716.438905] Modules linked in: ccm ses enclosure scsi_transport_sas ufs 
qnx4 hfsplus hfs minix ntfs msdos libcrc32c cpuid uas usb_storage nls_iso8859_1 
mmc_block rfcomm cmac bnep dm_crypt dell_wmi sparse_keymap dell_rbtn 
dell_laptop dell_smbios dcdbas dell_smm_hwmon binfmt_misc intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi 
irqbypass btusb crct10dif_pclmul crc32_pclmul snd_hda_codec_idt 
snd_hda_codec_generic ghash_clmulni_intel btrtl btbcm snd_hda_intel aesni_intel 
btintel snd_hda_codec bluetooth snd_hda_core snd_hwdep snd_pcm aes_x86_64 lrw 
glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event snd_rawmidi 
intel_cstate intel_rapl_perf arc4 joydev input_leds serio_raw iwlmvm snd_seq 
mac80211 snd_seq_device snd_timer iwlwifi lpc_ich snd cfg80211
[231716.438917]  soundcore shpchp mac_hid dell_smo8800 mei_me mei tpm_rng 
parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq 
hid_generic usbhid hid i915 i2c_algo_bit psmouse drm_kms_helper syscopyarea 
sysfillrect ahci sysimgblt libahci firewire_ohci sdhci_pci sdhci firewire_core 
crc_itu_t wmi fb_sys_fops drm e1000e ptp fjes video pps_core [last unloaded: 
jfs]
[231716.438919] CPU: 0 PID: 1334 Comm: Xorg Not tainted 4.8.12-040812-generic 
#201612020431
[231716.438919] Hardware name: Dell Inc. Latitude E6520/0NVF5K, BIOS A19 
11/14/2013
[231716.438922]  0086 8f1c6b0f a2e41cd8f878 
b3e12e02
[231716.438923]  a2e41cd8f8c8  a2e41cd8f8b8 
b3a82d9b
[231716.438924]  0f421cd8f898  a2e41ac26000 
a2e423708000
[231716.438924] Call Trace:
[231716.438927]  [] dump_stack+0x63/0x81
[231716.438929]  [] __warn+0xcb/0xf0
[231716.438931]  [] warn_slowpath_fmt+0x5f/0x80
[231716.438932]  [] ? finish_wait+0x55/0x70
[231716.438946]  [] intel_atomic_commit+0x559/0x560 [i915]
[231716.438947]  [] ? wake_atomic_t_function+0x60/0x60
[231716.438960]  [] drm_atomic_commit+0x37/0x60 [drm]
[231716.438968]  [] restore_fbdev_mode+0x14c/0x270 
[drm_kms_helper]
[231716.438972]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x34/0x80 [drm_kms_helper]
[231716.438975]  [] drm_fb_helper_set_par+0x2d/0x50 
[drm_kms_helper]
[231716.438990]  [] intel_fbdev_set_par+0x1a/0x60 [i915]
[231716.438992]  [] ? fb_set_var+0x2f5/0x460
[231716.438993]  [] fb_set_var+0x236/0x460
[231716.438994]  [] ? update_curr+0x66/0x170
[231716.438995]  [] ? __enqueue_entity+0x6c/0x70
[231716.438996]  [] ? enqueue_entity+0x2e8/0x8b0
[231716.438997]  [] fbcon_blank+0x30f/0x350
[231716.438998]  [] ? ttwu_do_activate+0x6f/0x80
[231716.439000]  [] do_unblank_screen+0xd2/0x1a0
[231716.439001]  [] complete_change_console+0x59/0xe0
[231716.439003]  [] vt_ioctl+0x709/0x12b0
[231716.439008]  [] ? drm_dropmaster_ioctl+0x4a/0x70 [drm]
[231716.439014]  [] ? drm_ioctl+0x236/0x4f0 [drm]
[231716.439017]  [] tty_ioctl+0x363/0xc70
[231716.439019]  [] ? handle_mm_fault+0x8a6/0x13c0
[231716.439021]  [] do_vfs_ioctl+0xa3/0x600
[231716.439022]  [] ? __do_page_fault+0x203/0x4d0
[231716.439023]  [] SyS_ioctl+0x79/0x90
[231716.439025]  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
[231716.439026] ---[ end trace 5a1628be00cd83d9 ]---

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

Title:
  kernel messages intel_crtc_wait_for_pending_flips correlate to compiz
  hang

Status in Skylinux:
  Unknown
Status in System76:
  New
Status in xf86-video-intel:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Debian:
  Confirmed
Status in linux package in Fedora:
  Unknown
Status in linux package in openSUSE:
  Unknown

Bug description:
  I am fairly frequently (maybe once every 2 days) seeing screen
  lockups.  The system is fine, and then screen locks up. mouse is still
  movable and even changes icon based on content under it (ie mouse over
  link changes to pointing hand).  Programs are still running (often
  this occurs during a google hangout, and the hangout, audio and mic
  seem to work fine).

  Today when this happened I had more patience and hit ctrl-alt-f1, and then 
subsequently saw that dmesg had:
  [82218.556025] [ cut here ]
  [82218.556074] WARNING: CPU: 0 PID: 8799 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 
intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]()
  

[Kernel-packages] [Bug 1629632] [NEW] Sap driver initialization failed, sap-server: Operation not permitted

[Laurent Bonnaud]

Public bug reported:

Hi,

here are are messages from the bluetooth daemon:

$ journalctl -b | grep bluetoothd
Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41
Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server
Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 
initialized
Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for "Service 
Changed" characteristic
Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed.
Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted (1)

There are at least 2 errors concerning:
 - handles
 - Sap driver/server

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: bluez 5.41-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
Uname: Linux 4.8.0-19-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Oct  2 09:59:43 2016
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency 
root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago)
dmi.bios.date: 03/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: HM77-HT
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: DC:85:DE:57:27:6F  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:1974 acl:0 sco:0 events:132 errors:0
TX bytes:6033 acl:0 sco:0 commands:132 errors:0

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Sap driver initialization failed, sap-server: Operation not permitted

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi,

  here are are messages from the bluetooth daemon:

  $ journalctl -b | grep bluetoothd
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 
initialized
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for 
"Service Changed" characteristic
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed.
  Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted 
(1)

  There are at least 2 errors concerning:
   - handles
   - Sap driver/server

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct  2 09:59:43 2016
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency 
root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:85:DE:57:27:6F  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:1974 acl:0 sco:0 events:132 errors:0
TX 

[Kernel-packages] [Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start

[Laurent Bonnaud]

> All tests produced the "not enough handles" message from bluetoothd.
> Is anyone successfully using bluetooth with these later ubuntu kernels?

On both of my systems I get the "not enough handles" messages but I got BT to 
work for both my use cases:
 - using a BT mouse on a laptop
 - streaming audio from my phone to my HTPC

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

Title:
  15:10: bluetoothd reports "Not enough handles to register service" at
  start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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

[Kernel-packages] [Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start

[Laurent Bonnaud]

This bug still exists in xenial with kernel 4.5:

$ uname -a
Linux xeelee 4.5.0-040500-lowlatency #201603140130 SMP PREEMPT Mon Mar 14 
05:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

$ journalctl |grep bluetoothd
Apr 08 20:24:43 xeelee bluetoothd[929]: Bluetooth daemon 5.37
Apr 08 20:24:43 xeelee bluetoothd[929]: Starting SDP server
Apr 08 20:24:43 xeelee bluetoothd[929]: Bluetooth management interface 1.11 
initialized
Apr 08 20:24:43 xeelee bluetoothd[929]: Failed to obtain handles for "Service 
Changed" characteristic
Apr 08 20:24:43 xeelee bluetoothd[929]: Not enough free handles to register 
service
Apr 08 20:24:43 xeelee bluetoothd[929]: Error adding Link Loss service
Apr 08 20:24:43 xeelee bluetoothd[929]: Not enough free handles to register 
service
Apr 08 20:24:43 xeelee bluetoothd[929]: Not enough free handles to register 
service
Apr 08 20:24:43 xeelee bluetoothd[929]: Not enough free handles to register 
service
Apr 08 20:24:43 xeelee bluetoothd[929]: Current Time Service could not be 
registered
Apr 08 20:24:43 xeelee bluetoothd[929]: gatt-time-server: Input/output error (5)
Apr 08 20:24:43 xeelee bluetoothd[929]: Not enough free handles to register 
service
Apr 08 20:24:43 xeelee bluetoothd[929]: Not enough free handles to register 
service
Apr 08 20:24:43 xeelee bluetoothd[929]: Sap driver initialization failed.
Apr 08 20:24:43 xeelee bluetoothd[929]: sap-server: Operation not permitted (1)
Apr 08 20:24:55 xeelee bluetoothd[929]: Endpoint registered: sender=:1.41 
path=/MediaEndpoint/A2DPSource
Apr 08 20:24:55 xeelee bluetoothd[929]: Endpoint registered: sender=:1.41 
path=/MediaEndpoint/A2DPSink

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

Title:
  15:10: bluetoothd reports "Not enough handles to register service" at
  start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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

[Kernel-packages] [Bug 1380025] Re: linux could use CONFIG_CC_STACKPROTECTOR_STRONG instead of CONFIG_CC_STACKPROTECTOR_REGULAR

[Laurent Bonnaud]

Thank you for the "fix"!

How about enabling CONFIG_CC_STACKPROTECTOR_STRONG also for mainline
builds ?

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

Title:
  linux could use CONFIG_CC_STACKPROTECTOR_STRONG instead of
  CONFIG_CC_STACKPROTECTOR_REGULAR

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  Here is the relevant kernel config:

  $ grep STACKPROTECTOR /boot/config-3.16.0-22-generic 
  CONFIG_HAVE_CC_STACKPROTECTOR=y
  CONFIG_CC_STACKPROTECTOR=y
  # CONFIG_CC_STACKPROTECTOR_NONE is not set
  CONFIG_CC_STACKPROTECTOR_REGULAR=y
  # CONFIG_CC_STACKPROTECTOR_STRONG is not set

  Since linux is built with gcc 4.9 in Ubuntu 14.10, it could use
  CONFIG_CC_STACKPROTECTOR_STRONG instead of
  CONFIG_CC_STACKPROTECTOR_REGULAR.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-22-generic 3.16.0-22.29
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   3741 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 11 10:03:30 2014
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
  IwConfig:
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Latitude E6520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-22-generic N/A
   linux-backports-modules-3.16.0-22-generic  N/A
   linux-firmware 1.135
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1380025/+subscriptions

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

[Kernel-packages] [Bug 1240143] Re: NFS client reports a 'readdir loop' with a corrupt name

[Laurent Bonnaud]

I am closing this bug because it is fixed in recent kernel versions.


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

Title:
  NFS client reports a 'readdir loop' with a corrupt name

Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Debian:
  Fix Released
Status in linux package in Fedora:
  Unknown

Bug description:
  We have an NFS server running on a RedHat system. One particular
  directory contains many, many RPMs (96850). It reports that there is a
  'readdir loop',  and the loop in question contains corrupted names. I
  assume the name corruption is happening on the Linux kernel end, not
  the server end:

  "NFS: directory Development/rpms contains a readdir loop.Please contact your 
server vendor.  The file: foo-bar-11.0flange-12345.AB5.x86_64.rpmmpmpmmT53 has 
duplicate cookie 1110018804"
  "NFS: directory Development/rpms contains a readdir loop.Please contact your 
server vendor.  The file: 
widget-wiggle-11.0-12356.AB5.x86_64.rpmpm.AB5.x86_64.rpm\xm has 
duplicate cookie 353422206"

  Since the corrupted names are never displayed in an 'ls' of the
  directory (even whilst the problem is occurring), I assume that this
  is a presentation problem in the warning message.

  Unfortunately the problem had gone away by the time I tried using
  tcpdump to capture the on-the-wire data.

  jfletcher@gromit:~$ cat /proc/version
  Linux version 3.2.0-29-generic (buildd@allspice) (gcc version 4.6.3 
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012
  jfletcher@gromit:~$ lsb_release -rd
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04

  
  The lspci information would not be useful - the system was running under KVM, 
with a single interface.

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

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

[Kernel-packages] [Bug 1405842] Re: Microcode SW error detected.

[Laurent Bonnaud]

I am closing this bug because it seems to have been fixed in more recent
microcode versions.


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

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

Title:
  Microcode SW error detected.

Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  I just saw this error in the kernel log:

  [171056.176336] iwlwifi :02:00.0: Microcode SW error detected.  
Restarting 0x200.
  [171056.176341] iwlwifi :02:00.0: CSR values: 
   
  [171056.176343] iwlwifi :02:00.0: (2nd byte of CSR_INT_COALESCING is 
CSR_INT_PERIODIC_REG)   
  [171056.176359] iwlwifi :02:00.0:CSR_HW_IF_CONFIG_REG: 0X40489204 
   
  [171056.176373] iwlwifi :02:00.0:  CSR_INT_COALESCING: 0X8040
  [171056.176387] iwlwifi :02:00.0: CSR_INT: 0X
  [171056.176401] iwlwifi :02:00.0:CSR_INT_MASK: 0X
  [171056.176414] iwlwifi :02:00.0:   CSR_FH_INT_STATUS: 0X
  [171056.176428] iwlwifi :02:00.0: CSR_GPIO_IN: 0X
  [171056.176442] iwlwifi :02:00.0:   CSR_RESET: 0X
  [171056.176456] iwlwifi :02:00.0:CSR_GP_CNTRL: 0X080403c5
  [171056.176470] iwlwifi :02:00.0:  CSR_HW_REV: 0X0144
  [171056.176484] iwlwifi :02:00.0:  CSR_EEPROM_REG: 0X
  [171056.176498] iwlwifi :02:00.0:   CSR_EEPROM_GP: 0X8000
  [171056.176512] iwlwifi :02:00.0:  CSR_OTP_GP_REG: 0X803a
  [171056.176526] iwlwifi :02:00.0: CSR_GIO_REG: 0X00080042
  [171056.176540] iwlwifi :02:00.0:CSR_GP_UCODE_REG: 0X
  [171056.176554] iwlwifi :02:00.0:   CSR_GP_DRIVER_REG: 0X
  [171056.176568] iwlwifi :02:00.0:   CSR_UCODE_DRV_GP1: 0X
  [171056.176582] iwlwifi :02:00.0:   CSR_UCODE_DRV_GP2: 0X
  [171056.176596] iwlwifi :02:00.0: CSR_LED_REG: 0X0060
  [171056.176610] iwlwifi :02:00.0:CSR_DRAM_INT_TBL_REG: 0X8821dad1
  [171056.176624] iwlwifi :02:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200
  [171056.176638] iwlwifi :02:00.0: CSR_ANA_PLL_CFG: 0Xd5d5
  [171056.176652] iwlwifi :02:00.0:  CSR_MONITOR_STATUS_REG: 0X3c08019d
  [171056.17] iwlwifi :02:00.0:   CSR_HW_REV_WA_REG: 0X0001001a
  [171056.176680] iwlwifi :02:00.0:CSR_DBG_HPET_MEM_REG: 0X0010
  [171056.176682] iwlwifi :02:00.0: FH register values:
  [171056.176707] iwlwifi :02:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 
0X0c483900
  [171056.176723] iwlwifi :02:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 
0X00c48380
  [171056.176739] iwlwifi :02:00.0:  FH_RSCSR_CHNL0_WPTR: 
0X0050
  [171056.176755] iwlwifi :02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 
0X00801114
  [171056.176771] iwlwifi :02:00.0:  FH_MEM_RSSR_SHARED_CTRL_REG: 
0X00fc
  [171056.176786] iwlwifi :02:00.0:FH_MEM_RSSR_RX_STATUS_REG: 
0X0203
  [171056.176802] iwlwifi :02:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 
0X
  [171056.176817] iwlwifi :02:00.0:FH_TSSR_TX_STATUS_REG: 
0X07ff0001
  [171056.176833] iwlwifi :02:00.0: FH_TSSR_TX_ERROR_REG: 
0X
  [171056.176975] iwlwifi :02:00.0: Start IWL Error Log Dump:
  [171056.176977] iwlwifi :02:00.0: Status: 0x, count: 6
  [171056.176978] iwlwifi :02:00.0: Loaded firmware version: 25.228.9.0
  [171056.176980] iwlwifi :02:00.0: 0x0034 | NMI_INTERRUPT_WDG  
 
  [171056.176982] iwlwifi :02:00.0: 0x00E3 | uPc
  [171056.176984] iwlwifi :02:00.0: 0x | branchlink1
  [171056.176985] iwlwifi :02:00.0: 0x0BA4 | branchlink2
  [171056.176987] iwlwifi :02:00.0: 0x0001626C | interruptlink1
  [171056.176988] iwlwifi :02:00.0: 0x00029676 | interruptlink2
  [171056.176990] iwlwifi :02:00.0: 0x | data1
  [171056.176991] iwlwifi :02:00.0: 0x0002 | data2
  [171056.176992] iwlwifi :02:00.0: 0x02039842 | data3
  [171056.176994] iwlwifi :02:00.0: 0xDE803F2A | beacon time
  [171056.176996] iwlwifi :02:00.0: 0x8DBC10F8 | tsf low
  [171056.176997] iwlwifi :02:00.0: 0x0001 | tsf hi
  [171056.176998] iwlwifi :02:00.0: 0x | time gp1
  [171056.177000] iwlwifi :02:00.0: 0x0BE49F4E | time gp2
  [171056.177001] iwlwifi :02:00.0: 0x | time gp3
  [171056.177003] iwlwifi :02:00.0: 0x000419E4 | uCode version
  [171056.177004] iwlwifi :02:00.0: 

[Kernel-packages] [Bug 1413127] Re: WARNING: CPU: 3 PID: 2121 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 assert_device_not_suspended.isra.8+0x43/0x50 [i915]()

[Laurent Bonnaud]

I am closing this bug because I never saw it again and kernel 3.16 is
very old by now.


** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1413127

Title:
  WARNING: CPU: 3 PID: 2121 at
  /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47
  assert_device_not_suspended.isra.8+0x43/0x50 [i915]()

Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Fedora:
  Unknown

Bug description:
  I got the following warning in the kernel log:

  [82452.464382] [ cut here ]
  [82452.464501] WARNING: CPU: 3 PID: 2121 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]()
  [82452.464505] Device suspended
  [82452.464508] Modules linked in: msr nls_utf8 ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c cpuid ctr ccm dm_crypt btusb dell_wmi 
sparse_keymap dell_laptop dcdbas arc4 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd iwlmvm mac80211 joydev serio_raw rfcomm bnep bluetooth iwlwifi 
snd_hda_codec_hdmi snd_hda_codec_idt 6lowpan_iphc snd_hda_codec_generic 
cfg80211 lpc_ich snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq dell_smo8800 
snd_seq_device snd_timer mei_me binfmt_misc snd mei shpchp soundcore mac_hid 
parport_pc ppdev tpm_rng lp parport btrfs xor raid6_pq hid_generic usbhid hid 
i915
  [82452.464658]  psmouse ahci sdhci_pci sdhci i2c_algo_bit libahci 
drm_kms_helper e1000e firewire_ohci drm firewire_core ptp crc_itu_t pps_core 
wmi video
  [82452.464699] CPU: 3 PID: 2121 Comm: Xorg Not tainted 3.16.0-30-generic 
#40-Ubuntu
  [82452.464703] Hardware name: Dell Inc. Latitude E6520/0NVF5K, BIOS A19 
11/14/2013
  [82452.464707]  0009 880220323a48 8178236b 
880220323a90
  [82452.464726]  880220323a80 8106feed 88021dd6 
000e1180
  [82452.464733]  880221ebb000 88021dd60080 0001 
880220323ae0
  [82452.464740] Call Trace:
  [82452.464767]  [] dump_stack+0x45/0x56
  [82452.464777]  [] warn_slowpath_common+0x7d/0xa0
  [82452.464785]  [] warn_slowpath_fmt+0x4c/0x50
  [82452.464809]  [] ? __ext4_handle_dirty_metadata+0x8b/0x200
  [82452.464862]  [] 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]
  [82452.464924]  [] gen6_read32+0x35/0x110 [i915]
  [82452.464985]  [] intel_lvds_compute_config+0x60/0x170 
[i915]
  [82452.465053]  [] intel_modeset_pipe_config+0x2a4/0xbd0 
[i915]
  [82452.465063]  [] ? jbd2_journal_stop+0x1b0/0x380
  [82452.465130]  [] __intel_set_mode+0x865/0xab0 [i915]
  [82452.465142]  [] ? idr_get_empty_slot+0x1a9/0x3d0
  [82452.465210]  [] intel_set_mode+0x16/0x30 [i915]
  [82452.465265]  [] intel_crtc_set_config+0xa4a/0xda0 [i915]
  [82452.465312]  [] drm_mode_set_config_internal+0x61/0xe0 
[drm]
  [82452.465367]  [] drm_mode_setcrtc+0x283/0x580 [drm]
  [82452.465391]  [] drm_ioctl+0x1df/0x680 [drm]
  [82452.465417]  [] do_vfs_ioctl+0x2c8/0x4a0
  [82452.465424]  [] ? __sb_end_write+0x31/0x60
  [82452.465445]  [] ? vfs_write+0x1b2/0x1f0
  [82452.465451]  [] SyS_ioctl+0x81/0xa0
  [82452.465461]  [] system_call_fastpath+0x1a/0x1f
  [82452.465466] ---[ end trace 8bf278fa292e793e ]---
  [82453.729524] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [83236.362037] [ cut here ]
  [83236.362169] WARNING: CPU: 1 PID: 2121 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]()
  [83236.362176] Device suspended
  [83236.362180] Modules linked in: msr nls_utf8 ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c cpuid ctr ccm dm_crypt btusb dell_wmi 
sparse_keymap dell_laptop dcdbas arc4 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd iwlmvm mac80211 joydev serio_raw rfcomm bnep bluetooth iwlwifi 
snd_hda_codec_hdmi snd_hda_codec_idt 6lowpan_iphc snd_hda_codec_generic 
cfg80211 lpc_ich snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq dell_smo8800 
snd_seq_device snd_timer mei_me binfmt_misc snd mei shpchp soundcore mac_hid 
parport_pc ppdev tpm_rng lp parport btrfs xor raid6_pq hid_generic usbhid hid 
i915
  [83236.362396]  psmouse ahci sdhci_pci sdhci i2c_algo_bit libahci 
drm_kms_helper e1000e firewire_ohci drm firewire_core ptp crc_itu_t pps_core 
wmi video
  [83236.362443] CPU: 1 PID: 2121 Comm: Xorg Tainted: GW 
3.16.0-30-generic #40-Ubuntu
  [83236.362447] Hardware name: Dell 

[Kernel-packages] [Bug 1380025] Re: linux could use CONFIG_CC_STACKPROTECTOR_STRONG instead of CONFIG_CC_STACKPROTECTOR_REGULAR

[Laurent Bonnaud]

This "bug" is still there is wily:

$ grep STACKPROTECTOR /boot/config-4.2.0-13-generic
CONFIG_HAVE_CC_STACKPROTECTOR=y
CONFIG_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR_NONE is not set
CONFIG_CC_STACKPROTECTOR_REGULAR=y
# CONFIG_CC_STACKPROTECTOR_STRONG is not set

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

Title:
  linux could use CONFIG_CC_STACKPROTECTOR_STRONG instead of
  CONFIG_CC_STACKPROTECTOR_REGULAR

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Here is the relevant kernel config:

  $ grep STACKPROTECTOR /boot/config-3.16.0-22-generic 
  CONFIG_HAVE_CC_STACKPROTECTOR=y
  CONFIG_CC_STACKPROTECTOR=y
  # CONFIG_CC_STACKPROTECTOR_NONE is not set
  CONFIG_CC_STACKPROTECTOR_REGULAR=y
  # CONFIG_CC_STACKPROTECTOR_STRONG is not set

  Since linux is built with gcc 4.9 in Ubuntu 14.10, it could use
  CONFIG_CC_STACKPROTECTOR_STRONG instead of
  CONFIG_CC_STACKPROTECTOR_REGULAR.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-22-generic 3.16.0-22.29
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   3741 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 11 10:03:30 2014
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
  IwConfig:
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Latitude E6520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-22-generic N/A
   linux-backports-modules-3.16.0-22-generic  N/A
   linux-firmware 1.135
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1380025/+subscriptions

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

[Kernel-packages] [Bug 1413127] Re: WARNING: CPU: 3 PID: 2121 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 assert_device_not_suspended.isra.8+0x43/0x50 [i915]()

[Laurent Bonnaud]

 Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

It is difficult to say because I have seen only one instance of this
problem.

The same machine is running since a week with kernel 3.19 and the
problem did not show up again.

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

Title:
  WARNING: CPU: 3 PID: 2121 at
  /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47
  assert_device_not_suspended.isra.8+0x43/0x50 [i915]()

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Fedora:
  Unknown

Bug description:
  I got the following warning in the kernel log:

  [82452.464382] [ cut here ]
  [82452.464501] WARNING: CPU: 3 PID: 2121 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]()
  [82452.464505] Device suspended
  [82452.464508] Modules linked in: msr nls_utf8 ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c cpuid ctr ccm dm_crypt btusb dell_wmi 
sparse_keymap dell_laptop dcdbas arc4 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd iwlmvm mac80211 joydev serio_raw rfcomm bnep bluetooth iwlwifi 
snd_hda_codec_hdmi snd_hda_codec_idt 6lowpan_iphc snd_hda_codec_generic 
cfg80211 lpc_ich snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq dell_smo8800 
snd_seq_device snd_timer mei_me binfmt_misc snd mei shpchp soundcore mac_hid 
parport_pc ppdev tpm_rng lp parport btrfs xor raid6_pq hid_generic usbhid hid 
i915
  [82452.464658]  psmouse ahci sdhci_pci sdhci i2c_algo_bit libahci 
drm_kms_helper e1000e firewire_ohci drm firewire_core ptp crc_itu_t pps_core 
wmi video
  [82452.464699] CPU: 3 PID: 2121 Comm: Xorg Not tainted 3.16.0-30-generic 
#40-Ubuntu
  [82452.464703] Hardware name: Dell Inc. Latitude E6520/0NVF5K, BIOS A19 
11/14/2013
  [82452.464707]  0009 880220323a48 8178236b 
880220323a90
  [82452.464726]  880220323a80 8106feed 88021dd6 
000e1180
  [82452.464733]  880221ebb000 88021dd60080 0001 
880220323ae0
  [82452.464740] Call Trace:
  [82452.464767]  [8178236b] dump_stack+0x45/0x56
  [82452.464777]  [8106feed] warn_slowpath_common+0x7d/0xa0
  [82452.464785]  [8106ff5c] warn_slowpath_fmt+0x4c/0x50
  [82452.464809]  [81292f6b] ? __ext4_handle_dirty_metadata+0x8b/0x200
  [82452.464862]  [c02dac13] 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]
  [82452.464924]  [c02dc495] gen6_read32+0x35/0x110 [i915]
  [82452.464985]  [c0319200] intel_lvds_compute_config+0x60/0x170 
[i915]
  [82452.465053]  [c02f2804] intel_modeset_pipe_config+0x2a4/0xbd0 
[i915]
  [82452.465063]  [812ac510] ? jbd2_journal_stop+0x1b0/0x380
  [82452.465130]  [c02f3995] __intel_set_mode+0x865/0xab0 [i915]
  [82452.465142]  [8139cc99] ? idr_get_empty_slot+0x1a9/0x3d0
  [82452.465210]  [c02f6b36] intel_set_mode+0x16/0x30 [i915]
  [82452.465265]  [c02f7bfa] intel_crtc_set_config+0xa4a/0xda0 [i915]
  [82452.465312]  [c01946d1] drm_mode_set_config_internal+0x61/0xe0 
[drm]
  [82452.465367]  [c0198413] drm_mode_setcrtc+0x283/0x580 [drm]
  [82452.465391]  [c0188a4f] drm_ioctl+0x1df/0x680 [drm]
  [82452.465417]  [811f51f8] do_vfs_ioctl+0x2c8/0x4a0
  [82452.465424]  [811e36f1] ? __sb_end_write+0x31/0x60
  [82452.465445]  [811e1262] ? vfs_write+0x1b2/0x1f0
  [82452.465451]  [811f5451] SyS_ioctl+0x81/0xa0
  [82452.465461]  [8178a3ad] system_call_fastpath+0x1a/0x1f
  [82452.465466] ---[ end trace 8bf278fa292e793e ]---
  [82453.729524] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [83236.362037] [ cut here ]
  [83236.362169] WARNING: CPU: 1 PID: 2121 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]()
  [83236.362176] Device suspended
  [83236.362180] Modules linked in: msr nls_utf8 ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c cpuid ctr ccm dm_crypt btusb dell_wmi 
sparse_keymap dell_laptop dcdbas arc4 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd iwlmvm mac80211 joydev serio_raw rfcomm bnep bluetooth iwlwifi 
snd_hda_codec_hdmi snd_hda_codec_idt 6lowpan_iphc snd_hda_codec_generic 
cfg80211 lpc_ich snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event 

[Kernel-packages] [Bug 1413127] [NEW] WARNING: CPU: 3 PID: 2121 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 assert_device_not_suspended.isra.8+0x43/0x50 [i915]()

[Laurent Bonnaud]

Public bug reported:

I got the following warning in the kernel log:

[82452.464382] [ cut here ]
[82452.464501] WARNING: CPU: 3 PID: 2121 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]()
[82452.464505] Device suspended
[82452.464508] Modules linked in: msr nls_utf8 ufs qnx4 hfsplus hfs minix ntfs 
msdos jfs xfs libcrc32c cpuid ctr ccm dm_crypt btusb dell_wmi sparse_keymap 
dell_laptop dcdbas arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd iwlmvm 
mac80211 joydev serio_raw rfcomm bnep bluetooth iwlwifi snd_hda_codec_hdmi 
snd_hda_codec_idt 6lowpan_iphc snd_hda_codec_generic cfg80211 lpc_ich 
snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq dell_smo8800 snd_seq_device snd_timer 
mei_me binfmt_misc snd mei shpchp soundcore mac_hid parport_pc ppdev tpm_rng lp 
parport btrfs xor raid6_pq hid_generic usbhid hid i915
[82452.464658]  psmouse ahci sdhci_pci sdhci i2c_algo_bit libahci 
drm_kms_helper e1000e firewire_ohci drm firewire_core ptp crc_itu_t pps_core 
wmi video
[82452.464699] CPU: 3 PID: 2121 Comm: Xorg Not tainted 3.16.0-30-generic 
#40-Ubuntu
[82452.464703] Hardware name: Dell Inc. Latitude E6520/0NVF5K, BIOS A19 
11/14/2013
[82452.464707]  0009 880220323a48 8178236b 
880220323a90
[82452.464726]  880220323a80 8106feed 88021dd6 
000e1180
[82452.464733]  880221ebb000 88021dd60080 0001 
880220323ae0
[82452.464740] Call Trace:
[82452.464767]  [8178236b] dump_stack+0x45/0x56
[82452.464777]  [8106feed] warn_slowpath_common+0x7d/0xa0
[82452.464785]  [8106ff5c] warn_slowpath_fmt+0x4c/0x50
[82452.464809]  [81292f6b] ? __ext4_handle_dirty_metadata+0x8b/0x200
[82452.464862]  [c02dac13] 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]
[82452.464924]  [c02dc495] gen6_read32+0x35/0x110 [i915]
[82452.464985]  [c0319200] intel_lvds_compute_config+0x60/0x170 [i915]
[82452.465053]  [c02f2804] intel_modeset_pipe_config+0x2a4/0xbd0 
[i915]
[82452.465063]  [812ac510] ? jbd2_journal_stop+0x1b0/0x380
[82452.465130]  [c02f3995] __intel_set_mode+0x865/0xab0 [i915]
[82452.465142]  [8139cc99] ? idr_get_empty_slot+0x1a9/0x3d0
[82452.465210]  [c02f6b36] intel_set_mode+0x16/0x30 [i915]
[82452.465265]  [c02f7bfa] intel_crtc_set_config+0xa4a/0xda0 [i915]
[82452.465312]  [c01946d1] drm_mode_set_config_internal+0x61/0xe0 
[drm]
[82452.465367]  [c0198413] drm_mode_setcrtc+0x283/0x580 [drm]
[82452.465391]  [c0188a4f] drm_ioctl+0x1df/0x680 [drm]
[82452.465417]  [811f51f8] do_vfs_ioctl+0x2c8/0x4a0
[82452.465424]  [811e36f1] ? __sb_end_write+0x31/0x60
[82452.465445]  [811e1262] ? vfs_write+0x1b2/0x1f0
[82452.465451]  [811f5451] SyS_ioctl+0x81/0xa0
[82452.465461]  [8178a3ad] system_call_fastpath+0x1a/0x1f
[82452.465466] ---[ end trace 8bf278fa292e793e ]---
[82453.729524] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[83236.362037] [ cut here ]
[83236.362169] WARNING: CPU: 1 PID: 2121 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]()
[83236.362176] Device suspended
[83236.362180] Modules linked in: msr nls_utf8 ufs qnx4 hfsplus hfs minix ntfs 
msdos jfs xfs libcrc32c cpuid ctr ccm dm_crypt btusb dell_wmi sparse_keymap 
dell_laptop dcdbas arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd iwlmvm 
mac80211 joydev serio_raw rfcomm bnep bluetooth iwlwifi snd_hda_codec_hdmi 
snd_hda_codec_idt 6lowpan_iphc snd_hda_codec_generic cfg80211 lpc_ich 
snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq dell_smo8800 snd_seq_device snd_timer 
mei_me binfmt_misc snd mei shpchp soundcore mac_hid parport_pc ppdev tpm_rng lp 
parport btrfs xor raid6_pq hid_generic usbhid hid i915
[83236.362396]  psmouse ahci sdhci_pci sdhci i2c_algo_bit libahci 
drm_kms_helper e1000e firewire_ohci drm firewire_core ptp crc_itu_t pps_core 
wmi video
[83236.362443] CPU: 1 PID: 2121 Comm: Xorg Tainted: GW 
3.16.0-30-generic #40-Ubuntu
[83236.362447] Hardware name: Dell Inc. Latitude E6520/0NVF5K, BIOS A19 
11/14/2013
[83236.362452]  0009 880220323a48 8178236b 
880220323a90
[83236.362459]  880220323a80 8106feed 88021dd6 
000e1180
[83236.362477]  880221ebb000 88021dd60080 0001 
880220323ae0
[83236.362484] Call Trace:

[Kernel-packages] [Bug 1413127] Re: WARNING: CPU: 3 PID: 2121 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 assert_device_not_suspended.isra.8+0x43/0x50 [i915]()

[Laurent Bonnaud]

Another instance of this bug:

  https://bbs.archlinux.org/viewtopic.php?id=183835


** Bug watch added: Red Hat Bugzilla #1133123
   https://bugzilla.redhat.com/show_bug.cgi?id=1133123

** Also affects: linux (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1133123
   Importance: Unknown
   Status: Unknown

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

Title:
  WARNING: CPU: 3 PID: 2121 at
  /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47
  assert_device_not_suspended.isra.8+0x43/0x50 [i915]()

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Fedora:
  Unknown

Bug description:
  I got the following warning in the kernel log:

  [82452.464382] [ cut here ]
  [82452.464501] WARNING: CPU: 3 PID: 2121 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]()
  [82452.464505] Device suspended
  [82452.464508] Modules linked in: msr nls_utf8 ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c cpuid ctr ccm dm_crypt btusb dell_wmi 
sparse_keymap dell_laptop dcdbas arc4 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd iwlmvm mac80211 joydev serio_raw rfcomm bnep bluetooth iwlwifi 
snd_hda_codec_hdmi snd_hda_codec_idt 6lowpan_iphc snd_hda_codec_generic 
cfg80211 lpc_ich snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq dell_smo8800 
snd_seq_device snd_timer mei_me binfmt_misc snd mei shpchp soundcore mac_hid 
parport_pc ppdev tpm_rng lp parport btrfs xor raid6_pq hid_generic usbhid hid 
i915
  [82452.464658]  psmouse ahci sdhci_pci sdhci i2c_algo_bit libahci 
drm_kms_helper e1000e firewire_ohci drm firewire_core ptp crc_itu_t pps_core 
wmi video
  [82452.464699] CPU: 3 PID: 2121 Comm: Xorg Not tainted 3.16.0-30-generic 
#40-Ubuntu
  [82452.464703] Hardware name: Dell Inc. Latitude E6520/0NVF5K, BIOS A19 
11/14/2013
  [82452.464707]  0009 880220323a48 8178236b 
880220323a90
  [82452.464726]  880220323a80 8106feed 88021dd6 
000e1180
  [82452.464733]  880221ebb000 88021dd60080 0001 
880220323ae0
  [82452.464740] Call Trace:
  [82452.464767]  [8178236b] dump_stack+0x45/0x56
  [82452.464777]  [8106feed] warn_slowpath_common+0x7d/0xa0
  [82452.464785]  [8106ff5c] warn_slowpath_fmt+0x4c/0x50
  [82452.464809]  [81292f6b] ? __ext4_handle_dirty_metadata+0x8b/0x200
  [82452.464862]  [c02dac13] 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]
  [82452.464924]  [c02dc495] gen6_read32+0x35/0x110 [i915]
  [82452.464985]  [c0319200] intel_lvds_compute_config+0x60/0x170 
[i915]
  [82452.465053]  [c02f2804] intel_modeset_pipe_config+0x2a4/0xbd0 
[i915]
  [82452.465063]  [812ac510] ? jbd2_journal_stop+0x1b0/0x380
  [82452.465130]  [c02f3995] __intel_set_mode+0x865/0xab0 [i915]
  [82452.465142]  [8139cc99] ? idr_get_empty_slot+0x1a9/0x3d0
  [82452.465210]  [c02f6b36] intel_set_mode+0x16/0x30 [i915]
  [82452.465265]  [c02f7bfa] intel_crtc_set_config+0xa4a/0xda0 [i915]
  [82452.465312]  [c01946d1] drm_mode_set_config_internal+0x61/0xe0 
[drm]
  [82452.465367]  [c0198413] drm_mode_setcrtc+0x283/0x580 [drm]
  [82452.465391]  [c0188a4f] drm_ioctl+0x1df/0x680 [drm]
  [82452.465417]  [811f51f8] do_vfs_ioctl+0x2c8/0x4a0
  [82452.465424]  [811e36f1] ? __sb_end_write+0x31/0x60
  [82452.465445]  [811e1262] ? vfs_write+0x1b2/0x1f0
  [82452.465451]  [811f5451] SyS_ioctl+0x81/0xa0
  [82452.465461]  [8178a3ad] system_call_fastpath+0x1a/0x1f
  [82452.465466] ---[ end trace 8bf278fa292e793e ]---
  [82453.729524] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [83236.362037] [ cut here ]
  [83236.362169] WARNING: CPU: 1 PID: 2121 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]()
  [83236.362176] Device suspended
  [83236.362180] Modules linked in: msr nls_utf8 ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c cpuid ctr ccm dm_crypt btusb dell_wmi 
sparse_keymap dell_laptop dcdbas arc4 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd iwlmvm mac80211 joydev serio_raw rfcomm bnep bluetooth iwlwifi 
snd_hda_codec_hdmi snd_hda_codec_idt 6lowpan_iphc snd_hda_codec_generic 
cfg80211 lpc_ich snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep 
snd_pcm snd_seq_midi 

[Kernel-packages] [Bug 1405842] Re: Microcode SW error detected.

[Laurent Bonnaud]

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

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

Title:
  Microcode SW error detected.

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I just saw this error in the kernel log:

  [171056.176336] iwlwifi :02:00.0: Microcode SW error detected.  
Restarting 0x200.
  [171056.176341] iwlwifi :02:00.0: CSR values: 
   
  [171056.176343] iwlwifi :02:00.0: (2nd byte of CSR_INT_COALESCING is 
CSR_INT_PERIODIC_REG)   
  [171056.176359] iwlwifi :02:00.0:CSR_HW_IF_CONFIG_REG: 0X40489204 
   
  [171056.176373] iwlwifi :02:00.0:  CSR_INT_COALESCING: 0X8040
  [171056.176387] iwlwifi :02:00.0: CSR_INT: 0X
  [171056.176401] iwlwifi :02:00.0:CSR_INT_MASK: 0X
  [171056.176414] iwlwifi :02:00.0:   CSR_FH_INT_STATUS: 0X
  [171056.176428] iwlwifi :02:00.0: CSR_GPIO_IN: 0X
  [171056.176442] iwlwifi :02:00.0:   CSR_RESET: 0X
  [171056.176456] iwlwifi :02:00.0:CSR_GP_CNTRL: 0X080403c5
  [171056.176470] iwlwifi :02:00.0:  CSR_HW_REV: 0X0144
  [171056.176484] iwlwifi :02:00.0:  CSR_EEPROM_REG: 0X
  [171056.176498] iwlwifi :02:00.0:   CSR_EEPROM_GP: 0X8000
  [171056.176512] iwlwifi :02:00.0:  CSR_OTP_GP_REG: 0X803a
  [171056.176526] iwlwifi :02:00.0: CSR_GIO_REG: 0X00080042
  [171056.176540] iwlwifi :02:00.0:CSR_GP_UCODE_REG: 0X
  [171056.176554] iwlwifi :02:00.0:   CSR_GP_DRIVER_REG: 0X
  [171056.176568] iwlwifi :02:00.0:   CSR_UCODE_DRV_GP1: 0X
  [171056.176582] iwlwifi :02:00.0:   CSR_UCODE_DRV_GP2: 0X
  [171056.176596] iwlwifi :02:00.0: CSR_LED_REG: 0X0060
  [171056.176610] iwlwifi :02:00.0:CSR_DRAM_INT_TBL_REG: 0X8821dad1
  [171056.176624] iwlwifi :02:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200
  [171056.176638] iwlwifi :02:00.0: CSR_ANA_PLL_CFG: 0Xd5d5
  [171056.176652] iwlwifi :02:00.0:  CSR_MONITOR_STATUS_REG: 0X3c08019d
  [171056.17] iwlwifi :02:00.0:   CSR_HW_REV_WA_REG: 0X0001001a
  [171056.176680] iwlwifi :02:00.0:CSR_DBG_HPET_MEM_REG: 0X0010
  [171056.176682] iwlwifi :02:00.0: FH register values:
  [171056.176707] iwlwifi :02:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 
0X0c483900
  [171056.176723] iwlwifi :02:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 
0X00c48380
  [171056.176739] iwlwifi :02:00.0:  FH_RSCSR_CHNL0_WPTR: 
0X0050
  [171056.176755] iwlwifi :02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 
0X00801114
  [171056.176771] iwlwifi :02:00.0:  FH_MEM_RSSR_SHARED_CTRL_REG: 
0X00fc
  [171056.176786] iwlwifi :02:00.0:FH_MEM_RSSR_RX_STATUS_REG: 
0X0203
  [171056.176802] iwlwifi :02:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 
0X
  [171056.176817] iwlwifi :02:00.0:FH_TSSR_TX_STATUS_REG: 
0X07ff0001
  [171056.176833] iwlwifi :02:00.0: FH_TSSR_TX_ERROR_REG: 
0X
  [171056.176975] iwlwifi :02:00.0: Start IWL Error Log Dump:
  [171056.176977] iwlwifi :02:00.0: Status: 0x, count: 6
  [171056.176978] iwlwifi :02:00.0: Loaded firmware version: 25.228.9.0
  [171056.176980] iwlwifi :02:00.0: 0x0034 | NMI_INTERRUPT_WDG  
 
  [171056.176982] iwlwifi :02:00.0: 0x00E3 | uPc
  [171056.176984] iwlwifi :02:00.0: 0x | branchlink1
  [171056.176985] iwlwifi :02:00.0: 0x0BA4 | branchlink2
  [171056.176987] iwlwifi :02:00.0: 0x0001626C | interruptlink1
  [171056.176988] iwlwifi :02:00.0: 0x00029676 | interruptlink2
  [171056.176990] iwlwifi :02:00.0: 0x | data1
  [171056.176991] iwlwifi :02:00.0: 0x0002 | data2
  [171056.176992] iwlwifi :02:00.0: 0x02039842 | data3
  [171056.176994] iwlwifi :02:00.0: 0xDE803F2A | beacon time
  [171056.176996] iwlwifi :02:00.0: 0x8DBC10F8 | tsf low
  [171056.176997] iwlwifi :02:00.0: 0x0001 | tsf hi
  [171056.176998] iwlwifi :02:00.0: 0x | time gp1
  [171056.177000] iwlwifi :02:00.0: 0x0BE49F4E | time gp2
  [171056.177001] iwlwifi :02:00.0: 0x | time gp3
  [171056.177003] iwlwifi :02:00.0: 0x000419E4 | uCode version
  [171056.177004] iwlwifi :02:00.0: 0x0144 | hw version
  [171056.177006] iwlwifi :02:00.0: 0x40489204 | board version
  

[Kernel-packages] [Bug 1405842] Re: Microcode SW error detected.

[Laurent Bonnaud]

 Did this issue start happening after an update/upgrade?

No idea.  I only saw this problem once and I cannot reproduce it.
Therefore I do not know if it occurs rarely or if it occurs with
specific kernel+FW versions.

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

Title:
  Microcode SW error detected.

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  I just saw this error in the kernel log:

  [171056.176336] iwlwifi :02:00.0: Microcode SW error detected.  
Restarting 0x200.
  [171056.176341] iwlwifi :02:00.0: CSR values: 
   
  [171056.176343] iwlwifi :02:00.0: (2nd byte of CSR_INT_COALESCING is 
CSR_INT_PERIODIC_REG)   
  [171056.176359] iwlwifi :02:00.0:CSR_HW_IF_CONFIG_REG: 0X40489204 
   
  [171056.176373] iwlwifi :02:00.0:  CSR_INT_COALESCING: 0X8040
  [171056.176387] iwlwifi :02:00.0: CSR_INT: 0X
  [171056.176401] iwlwifi :02:00.0:CSR_INT_MASK: 0X
  [171056.176414] iwlwifi :02:00.0:   CSR_FH_INT_STATUS: 0X
  [171056.176428] iwlwifi :02:00.0: CSR_GPIO_IN: 0X
  [171056.176442] iwlwifi :02:00.0:   CSR_RESET: 0X
  [171056.176456] iwlwifi :02:00.0:CSR_GP_CNTRL: 0X080403c5
  [171056.176470] iwlwifi :02:00.0:  CSR_HW_REV: 0X0144
  [171056.176484] iwlwifi :02:00.0:  CSR_EEPROM_REG: 0X
  [171056.176498] iwlwifi :02:00.0:   CSR_EEPROM_GP: 0X8000
  [171056.176512] iwlwifi :02:00.0:  CSR_OTP_GP_REG: 0X803a
  [171056.176526] iwlwifi :02:00.0: CSR_GIO_REG: 0X00080042
  [171056.176540] iwlwifi :02:00.0:CSR_GP_UCODE_REG: 0X
  [171056.176554] iwlwifi :02:00.0:   CSR_GP_DRIVER_REG: 0X
  [171056.176568] iwlwifi :02:00.0:   CSR_UCODE_DRV_GP1: 0X
  [171056.176582] iwlwifi :02:00.0:   CSR_UCODE_DRV_GP2: 0X
  [171056.176596] iwlwifi :02:00.0: CSR_LED_REG: 0X0060
  [171056.176610] iwlwifi :02:00.0:CSR_DRAM_INT_TBL_REG: 0X8821dad1
  [171056.176624] iwlwifi :02:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200
  [171056.176638] iwlwifi :02:00.0: CSR_ANA_PLL_CFG: 0Xd5d5
  [171056.176652] iwlwifi :02:00.0:  CSR_MONITOR_STATUS_REG: 0X3c08019d
  [171056.17] iwlwifi :02:00.0:   CSR_HW_REV_WA_REG: 0X0001001a
  [171056.176680] iwlwifi :02:00.0:CSR_DBG_HPET_MEM_REG: 0X0010
  [171056.176682] iwlwifi :02:00.0: FH register values:
  [171056.176707] iwlwifi :02:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 
0X0c483900
  [171056.176723] iwlwifi :02:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 
0X00c48380
  [171056.176739] iwlwifi :02:00.0:  FH_RSCSR_CHNL0_WPTR: 
0X0050
  [171056.176755] iwlwifi :02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 
0X00801114
  [171056.176771] iwlwifi :02:00.0:  FH_MEM_RSSR_SHARED_CTRL_REG: 
0X00fc
  [171056.176786] iwlwifi :02:00.0:FH_MEM_RSSR_RX_STATUS_REG: 
0X0203
  [171056.176802] iwlwifi :02:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 
0X
  [171056.176817] iwlwifi :02:00.0:FH_TSSR_TX_STATUS_REG: 
0X07ff0001
  [171056.176833] iwlwifi :02:00.0: FH_TSSR_TX_ERROR_REG: 
0X
  [171056.176975] iwlwifi :02:00.0: Start IWL Error Log Dump:
  [171056.176977] iwlwifi :02:00.0: Status: 0x, count: 6
  [171056.176978] iwlwifi :02:00.0: Loaded firmware version: 25.228.9.0
  [171056.176980] iwlwifi :02:00.0: 0x0034 | NMI_INTERRUPT_WDG  
 
  [171056.176982] iwlwifi :02:00.0: 0x00E3 | uPc
  [171056.176984] iwlwifi :02:00.0: 0x | branchlink1
  [171056.176985] iwlwifi :02:00.0: 0x0BA4 | branchlink2
  [171056.176987] iwlwifi :02:00.0: 0x0001626C | interruptlink1
  [171056.176988] iwlwifi :02:00.0: 0x00029676 | interruptlink2
  [171056.176990] iwlwifi :02:00.0: 0x | data1
  [171056.176991] iwlwifi :02:00.0: 0x0002 | data2
  [171056.176992] iwlwifi :02:00.0: 0x02039842 | data3
  [171056.176994] iwlwifi :02:00.0: 0xDE803F2A | beacon time
  [171056.176996] iwlwifi :02:00.0: 0x8DBC10F8 | tsf low
  [171056.176997] iwlwifi :02:00.0: 0x0001 | tsf hi
  [171056.176998] iwlwifi :02:00.0: 0x | time gp1
  [171056.177000] iwlwifi :02:00.0: 0x0BE49F4E | time gp2
  [171056.177001] iwlwifi :02:00.0: 0x | time gp3
  [171056.177003] iwlwifi :02:00.0: 0x000419E4 | uCode version
 

[Kernel-packages] [Bug 1405842] [NEW] Microcode SW error detected.

[Laurent Bonnaud]

Public bug reported:

I just saw this error in the kernel log:

[171056.176336] iwlwifi :02:00.0: Microcode SW error detected.  Restarting 
0x200.
[171056.176341] iwlwifi :02:00.0: CSR values:   
 
[171056.176343] iwlwifi :02:00.0: (2nd byte of CSR_INT_COALESCING is 
CSR_INT_PERIODIC_REG)   
[171056.176359] iwlwifi :02:00.0:CSR_HW_IF_CONFIG_REG: 0X40489204   
 
[171056.176373] iwlwifi :02:00.0:  CSR_INT_COALESCING: 0X8040
[171056.176387] iwlwifi :02:00.0: CSR_INT: 0X
[171056.176401] iwlwifi :02:00.0:CSR_INT_MASK: 0X
[171056.176414] iwlwifi :02:00.0:   CSR_FH_INT_STATUS: 0X
[171056.176428] iwlwifi :02:00.0: CSR_GPIO_IN: 0X
[171056.176442] iwlwifi :02:00.0:   CSR_RESET: 0X
[171056.176456] iwlwifi :02:00.0:CSR_GP_CNTRL: 0X080403c5
[171056.176470] iwlwifi :02:00.0:  CSR_HW_REV: 0X0144
[171056.176484] iwlwifi :02:00.0:  CSR_EEPROM_REG: 0X
[171056.176498] iwlwifi :02:00.0:   CSR_EEPROM_GP: 0X8000
[171056.176512] iwlwifi :02:00.0:  CSR_OTP_GP_REG: 0X803a
[171056.176526] iwlwifi :02:00.0: CSR_GIO_REG: 0X00080042
[171056.176540] iwlwifi :02:00.0:CSR_GP_UCODE_REG: 0X
[171056.176554] iwlwifi :02:00.0:   CSR_GP_DRIVER_REG: 0X
[171056.176568] iwlwifi :02:00.0:   CSR_UCODE_DRV_GP1: 0X
[171056.176582] iwlwifi :02:00.0:   CSR_UCODE_DRV_GP2: 0X
[171056.176596] iwlwifi :02:00.0: CSR_LED_REG: 0X0060
[171056.176610] iwlwifi :02:00.0:CSR_DRAM_INT_TBL_REG: 0X8821dad1
[171056.176624] iwlwifi :02:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200
[171056.176638] iwlwifi :02:00.0: CSR_ANA_PLL_CFG: 0Xd5d5
[171056.176652] iwlwifi :02:00.0:  CSR_MONITOR_STATUS_REG: 0X3c08019d
[171056.17] iwlwifi :02:00.0:   CSR_HW_REV_WA_REG: 0X0001001a
[171056.176680] iwlwifi :02:00.0:CSR_DBG_HPET_MEM_REG: 0X0010
[171056.176682] iwlwifi :02:00.0: FH register values:
[171056.176707] iwlwifi :02:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 
0X0c483900
[171056.176723] iwlwifi :02:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 
0X00c48380
[171056.176739] iwlwifi :02:00.0:  FH_RSCSR_CHNL0_WPTR: 
0X0050
[171056.176755] iwlwifi :02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 
0X00801114
[171056.176771] iwlwifi :02:00.0:  FH_MEM_RSSR_SHARED_CTRL_REG: 
0X00fc
[171056.176786] iwlwifi :02:00.0:FH_MEM_RSSR_RX_STATUS_REG: 
0X0203
[171056.176802] iwlwifi :02:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 
0X
[171056.176817] iwlwifi :02:00.0:FH_TSSR_TX_STATUS_REG: 
0X07ff0001
[171056.176833] iwlwifi :02:00.0: FH_TSSR_TX_ERROR_REG: 
0X
[171056.176975] iwlwifi :02:00.0: Start IWL Error Log Dump:
[171056.176977] iwlwifi :02:00.0: Status: 0x, count: 6
[171056.176978] iwlwifi :02:00.0: Loaded firmware version: 25.228.9.0
[171056.176980] iwlwifi :02:00.0: 0x0034 | NMI_INTERRUPT_WDG   
[171056.176982] iwlwifi :02:00.0: 0x00E3 | uPc
[171056.176984] iwlwifi :02:00.0: 0x | branchlink1
[171056.176985] iwlwifi :02:00.0: 0x0BA4 | branchlink2
[171056.176987] iwlwifi :02:00.0: 0x0001626C | interruptlink1
[171056.176988] iwlwifi :02:00.0: 0x00029676 | interruptlink2
[171056.176990] iwlwifi :02:00.0: 0x | data1
[171056.176991] iwlwifi :02:00.0: 0x0002 | data2
[171056.176992] iwlwifi :02:00.0: 0x02039842 | data3
[171056.176994] iwlwifi :02:00.0: 0xDE803F2A | beacon time
[171056.176996] iwlwifi :02:00.0: 0x8DBC10F8 | tsf low
[171056.176997] iwlwifi :02:00.0: 0x0001 | tsf hi
[171056.176998] iwlwifi :02:00.0: 0x | time gp1
[171056.177000] iwlwifi :02:00.0: 0x0BE49F4E | time gp2
[171056.177001] iwlwifi :02:00.0: 0x | time gp3
[171056.177003] iwlwifi :02:00.0: 0x000419E4 | uCode version
[171056.177004] iwlwifi :02:00.0: 0x0144 | hw version
[171056.177006] iwlwifi :02:00.0: 0x40489204 | board version
[171056.177007] iwlwifi :02:00.0: 0x1041001C | hcmd
[171056.177009] iwlwifi :02:00.0: 0x26F63002 | isr0
[171056.177010] iwlwifi :02:00.0: 0x11806000 | isr1
[171056.177012] iwlwifi :02:00.0: 0x001A | isr2
[171056.177013] iwlwifi :02:00.0: 0x40417CC2 | isr3
[171056.177015] iwlwifi :02:00.0: 0x | isr4
[171056.177016] iwlwifi :02:00.0: 0x10804112 | isr_pref
[171056.177018] iwlwifi :02:00.0: 0x | wait_event
[171056.177020] 

[Kernel-packages] [Bug 1401624] Re: kernel WARNINGs when disabling WiFi with RF kill switch on Intel chip

[Laurent Bonnaud]

 the kernel warnings do not happen either.

I spoke too soon.  I saw those warnings again  with kernel 3.16.0-29.39.
Therefore this bug cannot be reproduced at any time.

Dec 21 10:06:44 vougeot kernel: [  340.419664] iwlwifi :02:00.0: RF_KILL 
bit toggled to disable radio.
Dec 21 10:06:44 vougeot kernel: [  340.431512] [ cut here 
]
Dec 21 10:06:44 vougeot kernel: [  340.431585] WARNING: CPU: 3 PID: 94 at 
/build/buildd/linux-3.16.0/net/wireless/core.c:949 
cfg80211_netdev_notifier_call+0x5b9/0x630 [cfg80211]()
Dec 21 10:06:44 vougeot kernel: [  340.431593] Modules linked in: hid_generic 
hidp hid ctr ccm dm_crypt btusb dell_wmi sparse_keymap snd_hda_codec_hdmi 
rfcomm bnep arc4 snd_hda_codec_idt snd_hda_codec_generic dell_laptop dcdbas 
bluetooth 6lowpan_iphc snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
crct10dif_pclmul crc32_pclmul snd_pcm ghash_clmulni_intel iwlmvm mac80211 
snd_seq_midi snd_seq_midi_event snd_rawmidi aesni_intel snd_seq aes_x86_64 lrw 
gf128mul iwlwifi glue_helper ablk_helper cryptd joydev binfmt_misc serio_raw 
cfg80211 snd_seq_device snd_timer lpc_ich snd shpchp soundcore dell_smo8800 
mei_me mei mac_hid parport_pc ppdev tpm_rng lp parport btrfs xor raid6_pq i915 
psmouse firewire_ohci ahci i2c_algo_bit libahci e1000e drm_kms_helper drm 
sdhci_pci firewire_core sdhci ptp crc_itu_t pps_core wmi video
Dec 21 10:06:44 vougeot kernel: [  340.431790] CPU: 3 PID: 94 Comm: kworker/3:1 
Not tainted 3.16.0-29-generic #39-Ubuntu
Dec 21 10:06:44 vougeot kernel: [  340.431797] Hardware name: Dell Inc. 
Latitude E6520/0NVF5K, BIOS A19 11/14/2013
Dec 21 10:06:44 vougeot kernel: [  340.431832] Workqueue: events 
cfg80211_rfkill_sync_work [cfg80211]
Dec 21 10:06:44 vougeot kernel: [  340.431839]  0009 
88021e5e7c28 8178218a 
Dec 21 10:06:44 vougeot kernel: [  340.431850]  88021e5e7c60 
8106fedd 88021d5268d0 880220bf0260
Dec 21 10:06:44 vougeot kernel: [  340.431865]  0002 
88021d526000 880220bf 88021e5e7c70
Dec 21 10:06:44 vougeot kernel: [  340.431876] Call Trace:
Dec 21 10:06:44 vougeot kernel: [  340.431899]  [8178218a] 
dump_stack+0x45/0x56
Dec 21 10:06:44 vougeot kernel: [  340.431913]  [8106fedd] 
warn_slowpath_common+0x7d/0xa0
Dec 21 10:06:44 vougeot kernel: [  340.431924]  [8106ffba] 
warn_slowpath_null+0x1a/0x20
Dec 21 10:06:44 vougeot kernel: [  340.431960]  [c0456629] 
cfg80211_netdev_notifier_call+0x5b9/0x630 [cfg80211]
Dec 21 10:06:44 vougeot kernel: [  340.431979]  [810b92d4] ? 
__wake_up+0x44/0x50
Dec 21 10:06:44 vougeot kernel: [  340.431992]  [8166977a] ? 
sock_def_error_report+0x3a/0x60
Dec 21 10:06:44 vougeot kernel: [  340.432006]  [8109972d] 
notifier_call_chain+0x4d/0x70
Dec 21 10:06:44 vougeot kernel: [  340.432022]  [81099856] 
raw_notifier_call_chain+0x16/0x20
Dec 21 10:06:44 vougeot kernel: [  340.432035]  [8167b755] 
call_netdevice_notifiers_info+0x35/0x60
Dec 21 10:06:44 vougeot kernel: [  340.432046]  [8167baf8] 
dev_close_many+0xc8/0x120
Dec 21 10:06:44 vougeot kernel: [  340.432063]  [8167dcc6] 
dev_close.part.71+0x36/0x50
Dec 21 10:06:44 vougeot kernel: [  340.432073]  [8167dd01] 
dev_close+0x21/0x30
Dec 21 10:06:44 vougeot kernel: [  340.432108]  [c04558e5] 
cfg80211_shutdown_all_interfaces+0x45/0xc0 [cfg80211]
Dec 21 10:06:44 vougeot kernel: [  340.432142]  [c045598b] 
cfg80211_rfkill_sync_work+0x2b/0x40 [cfg80211]
Dec 21 10:06:44 vougeot kernel: [  340.432153]  [8108da32] 
process_one_work+0x182/0x4e0
Dec 21 10:06:44 vougeot kernel: [  340.432162]  [8108ddfb] 
worker_thread+0x6b/0x6a0
Dec 21 10:06:44 vougeot kernel: [  340.432178]  [81784e0d] ? 
__schedule+0x39d/0x890
Dec 21 10:06:44 vougeot kernel: [  340.432187]  [8108dd90] ? 
process_one_work+0x4e0/0x4e0
Dec 21 10:06:44 vougeot kernel: [  340.432199]  [81094c6b] 
kthread+0xdb/0x100
Dec 21 10:06:44 vougeot kernel: [  340.432210]  [81094b90] ? 
kthread_create_on_node+0x1c0/0x1c0
Dec 21 10:06:44 vougeot kernel: [  340.432228]  [8178a0fc] 
ret_from_fork+0x7c/0xb0
Dec 21 10:06:44 vougeot kernel: [  340.432239]  [81094b90] ? 
kthread_create_on_node+0x1c0/0x1c0
Dec 21 10:06:44 vougeot kernel: [  340.432246] ---[ end trace 4b8b4bc277e5e82a 
]---
Dec 21 10:06:44 vougeot kernel: [  340.432259] [ cut here 
]
Dec 21 10:06:44 vougeot kernel: [  340.432302] WARNING: CPU: 3 PID: 94 at 
/build/buildd/linux-3.16.0/net/mac80211/driver-ops.h:12 
ieee80211_request_sched_scan_stop+0x155/0x170 [mac80211]()
Dec 21 10:06:44 vougeot kernel: [  340.432313] wlan1:  Failed 
check-sdata-in-driver check, flags: 0x4
Dec 21 10:06:44 vougeot kernel: [  340.432317] Modules linked in: hid_generic 
hidp hid ctr ccm dm_crypt btusb dell_wmi 

[Kernel-packages] [Bug 1401624] Re: kernel WARNINGs when disabling WiFi with RF kill switch on Intel chip

[Laurent Bonnaud]

 Did this issue occur in a previous version of Ubuntu, or is this a new
issue?

I did not use this WiFi controller with a previous Ubuntu version.

 Would it be possible for you to test the latest upstream kernel? Refer to 
 https://wiki.ubuntu.com/KernelMainlineBuilds . 
 Please test the latest v3.18 kernel[0].

The kernel warnings do not happen with this kernel version:

ii  linux-image-3.18.0-031800-generic
3.18.0-031800.201412071935   amd64Linux kernel
image for version 3.18.0 on 64 bit x86 SMP

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

Title:
  kernel WARNINGs when disabling WiFi with RF kill switch on Intel chip

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have a laptop with this WiFi controller:

  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)
  Subsystem: Intel Corporation Dual Band Wireless-AC 7260
  Flags: bus master, fast devsel, latency 0, IRQ 47
  Memory at e2d0 (64-bit, non-prefetchable) [size=8K]
  Capabilities: access denied
  Kernel driver in use: iwlwifi

  I switched WiFi off with the RF kill switch and got those errors:

  [19011.796623] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio.
  [19011.797807] [ cut here ]
  [19011.797848] WARNING: CPU: 1 PID: 6870 at 
/build/buildd/linux-3.16.0/net/wireless/core.c:949 
cfg80211_netdev_notifier_call+0x5b9/0x630 [cfg80211]()
  [19011.797853] Modules linked in: ses enclosure uas usb_storage dm_crypt 
btusb arc4 dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel iwlmvm kvm mac80211 dell_laptop dcdbas 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd iwlwifi snd_hda_codec_hdmi joydev 
snd_hda_codec_idt serio_raw snd_hda_codec_generic bnep cfg80211 lpc_ich 
dell_smo8800 rfcomm bluetooth 6lowpan_iphc snd_hda_intel snd_hda_controller 
snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer snd mei_me mac_hid shpchp mei soundcore 
binfmt_misc parport_pc ppdev tpm_rng lp parport btrfs xor raid6_pq hid_generic 
usbhid hid i915 firewire_ohci i2c_algo_bit sdhci_pci sdhci psmouse firewire_core
  [19011.797964]  ahci e1000e libahci drm_kms_helper drm ptp crc_itu_t pps_core 
wmi video
  [19011.797980] CPU: 1 PID: 6870 Comm: kworker/1:1 Not tainted 
3.16.0-28-generic #37-Ubuntu
  [19011.797983] Hardware name: Dell Inc. Latitude E6520/0NVF5K, BIOS A19 
11/14/2013
  [19011.797999] Workqueue: events cfg80211_rfkill_sync_work [cfg80211]
  [19011.798003]  0009 8801b3c47c28 81781e6a 

  [19011.798008]  8801b3c47c60 8106fedd 88022136a8d0 
880035adc260
  [19011.798013]  0002 88022136a000 880035adc000 
8801b3c47c70
  [19011.798018] Call Trace:
  [19011.798030]  [81781e6a] dump_stack+0x45/0x56
  [19011.798038]  [8106fedd] warn_slowpath_common+0x7d/0xa0
  [19011.798044]  [8106ffba] warn_slowpath_null+0x1a/0x20
  [19011.798060]  [c052f629] 
cfg80211_netdev_notifier_call+0x5b9/0x630 [cfg80211]
  [19011.798068]  [8167acab] ? __dev_remove_pack+0x8b/0xb0
  [19011.798075]  [81761cbc] ? __unregister_prot_hook+0xcc/0xd0
  [19011.798082]  [8109972d] notifier_call_chain+0x4d/0x70
  [19011.798087]  [81099856] raw_notifier_call_chain+0x16/0x20
  [19011.798093]  [8167b4d5] call_netdevice_notifiers_info+0x35/0x60
  [19011.798099]  [8167b878] dev_close_many+0xc8/0x120
  [19011.798105]  [8167da46] dev_close.part.71+0x36/0x50
  [19011.798110]  [8167da81] dev_close+0x21/0x30
  [19011.798125]  [c052e8e5] 
cfg80211_shutdown_all_interfaces+0x45/0xc0 [cfg80211]
  [19011.798140]  [c052e98b] cfg80211_rfkill_sync_work+0x2b/0x40 
[cfg80211]
  [19011.798146]  [8108da32] process_one_work+0x182/0x4e0
  [19011.798151]  [8108ddfb] worker_thread+0x6b/0x6a0
  [19011.798156]  [8108dd90] ? process_one_work+0x4e0/0x4e0
  [19011.798162]  [81094c6b] kthread+0xdb/0x100
  [19011.798168]  [81094b90] ? kthread_create_on_node+0x1c0/0x1c0
  [19011.798175]  [81789dfc] ret_from_fork+0x7c/0xb0
  [19011.798181]  [81094b90] ? kthread_create_on_node+0x1c0/0x1c0
  [19011.798184] ---[ end trace 9074ade8075c79de ]---
  [19011.798187] [ cut here ]
  [19011.798210] WARNING: CPU: 1 PID: 6870 at 
/build/buildd/linux-3.16.0/net/mac80211/driver-ops.h:12 
ieee80211_request_sched_scan_stop+0x155/0x170 [mac80211]()
  [19011.798213] wlan1:  Failed check-sdata-in-driver check, flags: 0x0
  [19011.798214] Modules linked in: ses enclosure uas usb_storage dm_crypt 
btusb arc4 dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal 

[Kernel-packages] [Bug 1401624] Re: kernel WARNINGs when disabling WiFi with RF kill switch on Intel chip

[Laurent Bonnaud]

With this kernel:

ii  linux-image-extra-3.16.0-29-generic
3.16.0-29.39 amd64Linux kernel
extra modules for version 3.16.0 on 64 bit x86 SMP

and this updated firmware:

ii  linux-firmware  1.138.1
all  Firmware for Linux kernel drivers

the kernel warnings do not happen either.


** Changed in: linux (Ubuntu)
   Status: Incomplete = 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/1401624

Title:
  kernel WARNINGs when disabling WiFi with RF kill switch on Intel chip

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have a laptop with this WiFi controller:

  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)
  Subsystem: Intel Corporation Dual Band Wireless-AC 7260
  Flags: bus master, fast devsel, latency 0, IRQ 47
  Memory at e2d0 (64-bit, non-prefetchable) [size=8K]
  Capabilities: access denied
  Kernel driver in use: iwlwifi

  I switched WiFi off with the RF kill switch and got those errors:

  [19011.796623] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio.
  [19011.797807] [ cut here ]
  [19011.797848] WARNING: CPU: 1 PID: 6870 at 
/build/buildd/linux-3.16.0/net/wireless/core.c:949 
cfg80211_netdev_notifier_call+0x5b9/0x630 [cfg80211]()
  [19011.797853] Modules linked in: ses enclosure uas usb_storage dm_crypt 
btusb arc4 dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel iwlmvm kvm mac80211 dell_laptop dcdbas 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd iwlwifi snd_hda_codec_hdmi joydev 
snd_hda_codec_idt serio_raw snd_hda_codec_generic bnep cfg80211 lpc_ich 
dell_smo8800 rfcomm bluetooth 6lowpan_iphc snd_hda_intel snd_hda_controller 
snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer snd mei_me mac_hid shpchp mei soundcore 
binfmt_misc parport_pc ppdev tpm_rng lp parport btrfs xor raid6_pq hid_generic 
usbhid hid i915 firewire_ohci i2c_algo_bit sdhci_pci sdhci psmouse firewire_core
  [19011.797964]  ahci e1000e libahci drm_kms_helper drm ptp crc_itu_t pps_core 
wmi video
  [19011.797980] CPU: 1 PID: 6870 Comm: kworker/1:1 Not tainted 
3.16.0-28-generic #37-Ubuntu
  [19011.797983] Hardware name: Dell Inc. Latitude E6520/0NVF5K, BIOS A19 
11/14/2013
  [19011.797999] Workqueue: events cfg80211_rfkill_sync_work [cfg80211]
  [19011.798003]  0009 8801b3c47c28 81781e6a 

  [19011.798008]  8801b3c47c60 8106fedd 88022136a8d0 
880035adc260
  [19011.798013]  0002 88022136a000 880035adc000 
8801b3c47c70
  [19011.798018] Call Trace:
  [19011.798030]  [81781e6a] dump_stack+0x45/0x56
  [19011.798038]  [8106fedd] warn_slowpath_common+0x7d/0xa0
  [19011.798044]  [8106ffba] warn_slowpath_null+0x1a/0x20
  [19011.798060]  [c052f629] 
cfg80211_netdev_notifier_call+0x5b9/0x630 [cfg80211]
  [19011.798068]  [8167acab] ? __dev_remove_pack+0x8b/0xb0
  [19011.798075]  [81761cbc] ? __unregister_prot_hook+0xcc/0xd0
  [19011.798082]  [8109972d] notifier_call_chain+0x4d/0x70
  [19011.798087]  [81099856] raw_notifier_call_chain+0x16/0x20
  [19011.798093]  [8167b4d5] call_netdevice_notifiers_info+0x35/0x60
  [19011.798099]  [8167b878] dev_close_many+0xc8/0x120
  [19011.798105]  [8167da46] dev_close.part.71+0x36/0x50
  [19011.798110]  [8167da81] dev_close+0x21/0x30
  [19011.798125]  [c052e8e5] 
cfg80211_shutdown_all_interfaces+0x45/0xc0 [cfg80211]
  [19011.798140]  [c052e98b] cfg80211_rfkill_sync_work+0x2b/0x40 
[cfg80211]
  [19011.798146]  [8108da32] process_one_work+0x182/0x4e0
  [19011.798151]  [8108ddfb] worker_thread+0x6b/0x6a0
  [19011.798156]  [8108dd90] ? process_one_work+0x4e0/0x4e0
  [19011.798162]  [81094c6b] kthread+0xdb/0x100
  [19011.798168]  [81094b90] ? kthread_create_on_node+0x1c0/0x1c0
  [19011.798175]  [81789dfc] ret_from_fork+0x7c/0xb0
  [19011.798181]  [81094b90] ? kthread_create_on_node+0x1c0/0x1c0
  [19011.798184] ---[ end trace 9074ade8075c79de ]---
  [19011.798187] [ cut here ]
  [19011.798210] WARNING: CPU: 1 PID: 6870 at 
/build/buildd/linux-3.16.0/net/mac80211/driver-ops.h:12 
ieee80211_request_sched_scan_stop+0x155/0x170 [mac80211]()
  [19011.798213] wlan1:  Failed check-sdata-in-driver check, flags: 0x0
  [19011.798214] Modules linked in: ses enclosure uas usb_storage dm_crypt 
btusb arc4 dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel iwlmvm kvm mac80211 dell_laptop dcdbas 

[Kernel-packages] [Bug 1401624] [NEW] kernel WARNINGs when disabling WiFi with RF kill switch on Intel chip

[Laurent Bonnaud]

Public bug reported:

I have a laptop with this WiFi controller:

02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260
Flags: bus master, fast devsel, latency 0, IRQ 47
Memory at e2d0 (64-bit, non-prefetchable) [size=8K]
Capabilities: access denied
Kernel driver in use: iwlwifi

I switched WiFi off with the RF kill switch and got those errors:

[19011.796623] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio.
[19011.797807] [ cut here ]
[19011.797848] WARNING: CPU: 1 PID: 6870 at 
/build/buildd/linux-3.16.0/net/wireless/core.c:949 
cfg80211_netdev_notifier_call+0x5b9/0x630 [cfg80211]()
[19011.797853] Modules linked in: ses enclosure uas usb_storage dm_crypt btusb 
arc4 dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel iwlmvm kvm mac80211 dell_laptop dcdbas crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd iwlwifi snd_hda_codec_hdmi joydev 
snd_hda_codec_idt serio_raw snd_hda_codec_generic bnep cfg80211 lpc_ich 
dell_smo8800 rfcomm bluetooth 6lowpan_iphc snd_hda_intel snd_hda_controller 
snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer snd mei_me mac_hid shpchp mei soundcore 
binfmt_misc parport_pc ppdev tpm_rng lp parport btrfs xor raid6_pq hid_generic 
usbhid hid i915 firewire_ohci i2c_algo_bit sdhci_pci sdhci psmouse firewire_core
[19011.797964]  ahci e1000e libahci drm_kms_helper drm ptp crc_itu_t pps_core 
wmi video
[19011.797980] CPU: 1 PID: 6870 Comm: kworker/1:1 Not tainted 3.16.0-28-generic 
#37-Ubuntu
[19011.797983] Hardware name: Dell Inc. Latitude E6520/0NVF5K, BIOS A19 
11/14/2013
[19011.797999] Workqueue: events cfg80211_rfkill_sync_work [cfg80211]
[19011.798003]  0009 8801b3c47c28 81781e6a 

[19011.798008]  8801b3c47c60 8106fedd 88022136a8d0 
880035adc260
[19011.798013]  0002 88022136a000 880035adc000 
8801b3c47c70
[19011.798018] Call Trace:
[19011.798030]  [81781e6a] dump_stack+0x45/0x56
[19011.798038]  [8106fedd] warn_slowpath_common+0x7d/0xa0
[19011.798044]  [8106ffba] warn_slowpath_null+0x1a/0x20
[19011.798060]  [c052f629] cfg80211_netdev_notifier_call+0x5b9/0x630 
[cfg80211]
[19011.798068]  [8167acab] ? __dev_remove_pack+0x8b/0xb0
[19011.798075]  [81761cbc] ? __unregister_prot_hook+0xcc/0xd0
[19011.798082]  [8109972d] notifier_call_chain+0x4d/0x70
[19011.798087]  [81099856] raw_notifier_call_chain+0x16/0x20
[19011.798093]  [8167b4d5] call_netdevice_notifiers_info+0x35/0x60
[19011.798099]  [8167b878] dev_close_many+0xc8/0x120
[19011.798105]  [8167da46] dev_close.part.71+0x36/0x50
[19011.798110]  [8167da81] dev_close+0x21/0x30
[19011.798125]  [c052e8e5] cfg80211_shutdown_all_interfaces+0x45/0xc0 
[cfg80211]
[19011.798140]  [c052e98b] cfg80211_rfkill_sync_work+0x2b/0x40 
[cfg80211]
[19011.798146]  [8108da32] process_one_work+0x182/0x4e0
[19011.798151]  [8108ddfb] worker_thread+0x6b/0x6a0
[19011.798156]  [8108dd90] ? process_one_work+0x4e0/0x4e0
[19011.798162]  [81094c6b] kthread+0xdb/0x100
[19011.798168]  [81094b90] ? kthread_create_on_node+0x1c0/0x1c0
[19011.798175]  [81789dfc] ret_from_fork+0x7c/0xb0
[19011.798181]  [81094b90] ? kthread_create_on_node+0x1c0/0x1c0
[19011.798184] ---[ end trace 9074ade8075c79de ]---
[19011.798187] [ cut here ]
[19011.798210] WARNING: CPU: 1 PID: 6870 at 
/build/buildd/linux-3.16.0/net/mac80211/driver-ops.h:12 
ieee80211_request_sched_scan_stop+0x155/0x170 [mac80211]()
[19011.798213] wlan1:  Failed check-sdata-in-driver check, flags: 0x0
[19011.798214] Modules linked in: ses enclosure uas usb_storage dm_crypt btusb 
arc4 dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel iwlmvm kvm mac80211 dell_laptop dcdbas crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd iwlwifi snd_hda_codec_hdmi joydev 
snd_hda_codec_idt serio_raw snd_hda_codec_generic bnep cfg80211 lpc_ich 
dell_smo8800 rfcomm bluetooth 6lowpan_iphc snd_hda_intel snd_hda_controller 
snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer snd mei_me mac_hid shpchp mei soundcore 
binfmt_misc parport_pc ppdev tpm_rng lp parport btrfs xor raid6_pq hid_generic 
usbhid hid i915 firewire_ohci i2c_algo_bit sdhci_pci sdhci psmouse firewire_core
[19011.798283]  ahci e1000e libahci drm_kms_helper drm ptp crc_itu_t pps_core 
wmi video
[19011.798295] CPU: 1 PID: 6870 Comm: kworker/1:1 Tainted: GW 
3.16.0-28-generic #37-Ubuntu
[19011.798298] Hardware name: 

[Kernel-packages] [Bug 1380025] [NEW] linux could use CONFIG_CC_STACKPROTECTOR_STRONG instead of CONFIG_CC_STACKPROTECTOR_REGULAR

[Laurent Bonnaud]

Public bug reported:

Here is the relevant kernel config:

$ grep STACKPROTECTOR /boot/config-3.16.0-22-generic 
CONFIG_HAVE_CC_STACKPROTECTOR=y
CONFIG_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR_NONE is not set
CONFIG_CC_STACKPROTECTOR_REGULAR=y
# CONFIG_CC_STACKPROTECTOR_STRONG is not set

Since linux is built with gcc 4.9 in Ubuntu 14.10, it could use
CONFIG_CC_STACKPROTECTOR_STRONG instead of
CONFIG_CC_STACKPROTECTOR_REGULAR.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-22-generic 3.16.0-22.29
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bonnaudl   3741 F pulseaudio
CurrentDesktop: KDE
Date: Sat Oct 11 10:03:30 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
IwConfig:
 eth1  no wireless extensions.
 
 lono wireless extensions.
MachineType: Dell Inc. Latitude E6520
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-22-generic N/A
 linux-backports-modules-3.16.0-22-generic  N/A
 linux-firmware 1.135
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
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.

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


** Tags: amd64 apport-bug utopic

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

Title:
  linux could use CONFIG_CC_STACKPROTECTOR_STRONG instead of
  CONFIG_CC_STACKPROTECTOR_REGULAR

Status in “linux” package in Ubuntu:
  New

Bug description:
  Here is the relevant kernel config:

  $ grep STACKPROTECTOR /boot/config-3.16.0-22-generic 
  CONFIG_HAVE_CC_STACKPROTECTOR=y
  CONFIG_CC_STACKPROTECTOR=y
  # CONFIG_CC_STACKPROTECTOR_NONE is not set
  CONFIG_CC_STACKPROTECTOR_REGULAR=y
  # CONFIG_CC_STACKPROTECTOR_STRONG is not set

  Since linux is built with gcc 4.9 in Ubuntu 14.10, it could use
  CONFIG_CC_STACKPROTECTOR_STRONG instead of
  CONFIG_CC_STACKPROTECTOR_REGULAR.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-22-generic 3.16.0-22.29
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   3741 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 11 10:03:30 2014
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
  IwConfig:
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Latitude E6520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-22-generic N/A
   linux-backports-modules-3.16.0-22-generic  N/A
   linux-firmware 1.135
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1380025/+subscriptions

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

[Kernel-packages] [Bug 1240143] Re: NFS client reports a 'readdir loop' with a corrupt name

[Laurent Bonnaud]

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

** Also affects: linux (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714974
   Importance: Unknown
   Status: Unknown

** Bug watch added: Red Hat Bugzilla #739222
   https://bugzilla.redhat.com/show_bug.cgi?id=739222

** Also affects: linux (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=739222
   Importance: Unknown
   Status: Unknown

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

Title:
  NFS client reports a 'readdir loop' with a corrupt name

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” package in Debian:
  Unknown
Status in “linux” package in Fedora:
  Unknown

Bug description:
  We have an NFS server running on a RedHat system. One particular
  directory contains many, many RPMs (96850). It reports that there is a
  'readdir loop',  and the loop in question contains corrupted names. I
  assume the name corruption is happening on the Linux kernel end, not
  the server end:

  NFS: directory Development/rpms contains a readdir loop.Please contact your 
server vendor.  The file: foo-bar-11.0flange-12345.AB5.x86_64.rpmmpmpmmT53 has 
duplicate cookie 1110018804
  NFS: directory Development/rpms contains a readdir loop.Please contact your 
server vendor.  The file: 
widget-wiggle-11.0-12356.AB5.x86_64.rpmpm.AB5.x86_64.rpm\xm has 
duplicate cookie 353422206

  Since the corrupted names are never displayed in an 'ls' of the
  directory (even whilst the problem is occurring), I assume that this
  is a presentation problem in the warning message.

  Unfortunately the problem had gone away by the time I tried using
  tcpdump to capture the on-the-wire data.

  jfletcher@gromit:~$ cat /proc/version
  Linux version 3.2.0-29-generic (buildd@allspice) (gcc version 4.6.3 
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012
  jfletcher@gromit:~$ lsb_release -rd
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04

  
  The lspci information would not be useful - the system was running under KVM, 
with a single interface.

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

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

[Kernel-packages] [Bug 661306] Re: dangling symlinks in linux-doc package

[Laurent Bonnaud]

The bug is still there in utopic and getting worse:

$ symlinks -r /usr/share/doc/linux-doc/ | grep dangling | wc
159 636   22178

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

Title:
  dangling symlinks in linux-doc package

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The linux-doc package contains many symlinks that refer to the build
  process and are not present on an installed system.  For example:

  lrwxrwxrwx 1 root root 67 Oct  5 04:03 /usr/share/doc/linux-
  doc/html/audio.xml -
  /build/buildd/linux-3.5.0/Documentation/DocBook/media/dvb/audio.xml

  And there are many of them:

  $ symlinks -r /usr/share/doc/linux-doc/ | grep dangling | wc
  151 604   20939

  This is with the latest package available in quantal:

  Package: linux-doc
  Version: 3.5.0-17.27

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

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

[Kernel-packages] [Bug 1264346] Re: [Dell Latitude E6520] After suspend, machine very slow with ondemand governor

[Laurent Bonnaud]

I cannot reproduce the problem with trusty, therefore I am going to
close this bug...

** Changed in: linux (Ubuntu)
   Status: Incomplete = 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/1264346

Title:
  [Dell Latitude E6520] After suspend, machine very slow with ondemand
  governor

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  After several suspend/resume cycles and several days of uptime, using the 
ondemand governor the system is very slow to answer some inputs. The text 
output pauses for several seconds while I am typing this text. Trying to scroll 
a firefox window takes several seconds. Switching tabs in firefox takes several 
seconds:
  cat /sys/devices/system/cpu/c*/cpufreq/scaling_governor
  ondemand
  ondemand
  ondemand
  ondemand

  WORKAROUND: Setting the governor to performance fixes this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-15-generic 3.11.0-15.23
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   2373 F pulseaudio
  Date: Thu Dec 26 18:17:23 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
  InstallationDate: Installed on 2013-04-27 (243 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-01 (86 days ago)
  dmi.bios.date: 02/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  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.:bvrA12:bd02/28/2012: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/1264346/+subscriptions

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

[Kernel-packages] [Bug 661306] Re: dangling symlinks in linux-doc package

[Laurent Bonnaud]

The bug is still there in trusty:

$ symlinks -r /usr/share/doc/linux-doc/ | grep dangling | wc
156 624   21778

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

Title:
  dangling symlinks in linux-doc package

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The linux-doc package contains many symlinks that refer to the build
  process and are not present on an installed system.  For example:

  lrwxrwxrwx 1 root root 67 Oct  5 04:03 /usr/share/doc/linux-
  doc/html/audio.xml -
  /build/buildd/linux-3.5.0/Documentation/DocBook/media/dvb/audio.xml

  And there are many of them:

  $ symlinks -r /usr/share/doc/linux-doc/ | grep dangling | wc
  151 604   20939

  This is with the latest package available in quantal:

  Package: linux-doc
  Version: 3.5.0-17.27

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

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

[Kernel-packages] [Bug 1264346] Re: [Dell Latitude E6520] After suspend, machine very slow with ondemand governor

[Laurent Bonnaud]

 The slowdown doesn't always happen, but it does appear to happen after
sometimes resuming from standby.

In my case I suspect that the problem might be caused by a non-
compatible power adapter (I am using several ones).  Since I reported
the problem I changed this power adapter and did not see the problem
again.  Do you use a non-Dell or non-compatible Dell power adapter ?

 I've not known whether to blame it on the DE I was using (Cinnamon) or
some other component.

The DE should have nothing to do with it.  This is clearly a kernel/BIOS
problem.

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

Title:
  [Dell Latitude E6520] After suspend, machine very slow with ondemand
  governor

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After several suspend/resume cycles and several days of uptime, using the 
ondemand governor the system is very slow to answer some inputs. The text 
output pauses for several seconds while I am typing this text. Trying to scroll 
a firefox window takes several seconds. Switching tabs in firefox takes several 
seconds:
  cat /sys/devices/system/cpu/c*/cpufreq/scaling_governor
  ondemand
  ondemand
  ondemand
  ondemand

  WORKAROUND: Setting the governor to performance fixes this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-15-generic 3.11.0-15.23
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   2373 F pulseaudio
  Date: Thu Dec 26 18:17:23 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
  InstallationDate: Installed on 2013-04-27 (243 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-01 (86 days ago)
  dmi.bios.date: 02/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  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.:bvrA12:bd02/28/2012: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/1264346/+subscriptions

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

[Kernel-packages] [Bug 1264346] Re: [Dell Latitude E6520] After suspend, machine very slow with ondemand governor

[Laurent Bonnaud]

 Could you please confirm this issue exists with the latest development
release of Ubuntu?

I am using this system as my main computing platform and therefore I
cannot do tests that span several days.

 It will allow additional upstream developers to examine the issue.

Unfortunately my kernel is tainted (because it has a Wifi adapter that
requires a non-free driver) and therefore I am afraid that upstream
kernel developers will not consider this bug.  I am in the process of
replacing this Wifi adapter but it will take time...

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

Title:
  [Dell Latitude E6520] After suspend, machine very slow with ondemand
  governor

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After several suspend/resume cycles and several days of uptime, using the 
ondemand governor the system is very slow to answer some inputs. The text 
output pauses for several seconds while I am typing this text. Trying to scroll 
a firefox window takes several seconds. Switching tabs in firefox takes several 
seconds:
  cat /sys/devices/system/cpu/c*/cpufreq/scaling_governor
  ondemand
  ondemand
  ondemand
  ondemand

  WORKAROUND: Setting the governor to performance fixes this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-15-generic 3.11.0-15.23
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   2373 F pulseaudio
  Date: Thu Dec 26 18:17:23 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
  InstallationDate: Installed on 2013-04-27 (243 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-01 (86 days ago)
  dmi.bios.date: 02/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  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.:bvrA12:bd02/28/2012: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/1264346/+subscriptions

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

[Kernel-packages] [Bug 1264346] Re: [Dell Latitude E6520] After suspend, machine very slow with ondemand governor

[Laurent Bonnaud]

Since my initial report I updated the BIOS of this laptop:

$  sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date
A19
11/14/2013

and today (after 8 days of uptime and perhaps 20 suspend/resume cycles)
the bug reappeared:

# /usr/lib/checkbox/bin/frequency_governors_test
2014-01-23 12:09:52 INFO System Capabilites:
2014-01-23 12:09:52 INFO -
2014-01-23 12:09:52 INFO System has 4 cpus
2014-01-23 12:09:52 INFO Supported CPU Frequencies: 
2014-01-23 12:09:52 INFO 2801 MHz
2014-01-23 12:09:52 INFO 2800 MHz
2014-01-23 12:09:52 INFO 2600 MHz
2014-01-23 12:09:52 INFO 2400 MHz
2014-01-23 12:09:52 INFO 2200 MHz
2014-01-23 12:09:52 INFO 2000 MHz
2014-01-23 12:09:52 INFO 1800 MHz
2014-01-23 12:09:52 INFO 1600 MHz
2014-01-23 12:09:52 INFO 1400 MHz
2014-01-23 12:09:52 INFO 1200 MHz
2014-01-23 12:09:52 INFO 1000 MHz
2014-01-23 12:09:52 INFO 800 MHz
2014-01-23 12:09:52 INFO Supported Governors: 
2014-01-23 12:09:52 INFO conservative
2014-01-23 12:09:52 INFO ondemand
2014-01-23 12:09:52 INFO userspace
2014-01-23 12:09:52 INFO powersave
2014-01-23 12:09:52 INFO performance
2014-01-23 12:09:52 INFO Current governors:
2014-01-23 12:09:52 INFO cpu0: ondemand
2014-01-23 12:09:52 INFO cpu1: ondemand
2014-01-23 12:09:52 INFO cpu2: ondemand
2014-01-23 12:09:52 INFO cpu3: ondemand
2014-01-23 12:09:52 INFO Beginning Frequency Governors Testing
2014-01-23 12:09:52 INFO Userspace Governor Test:
2014-01-23 12:09:52 INFO -
2014-01-23 12:09:52 INFO Setting governor to userspace
2014-01-23 12:10:22 INFO Setting CPU frequency to 800 MHz
2014-01-23 12:10:22 INFO Running CPU load test...
2014-01-23 12:10:22 INFO pid 4285's current affinity list: 0-3
2014-01-23 12:10:22 INFO pid 4285's new affinity list: 0
2014-01-23 12:10:23 INFO Minimum frequency load test time: 0.25
2014-01-23 12:10:23 INFO Setting CPU frequency to 2801 MHz
2014-01-23 12:10:23 INFO Running CPU load test...
2014-01-23 12:10:23 INFO pid 4285's current affinity list: 0
2014-01-23 12:10:23 INFO pid 4285's new affinity list: 0
2014-01-23 12:10:23 INFO Maximum frequency load test time: 0.05
2014-01-23 12:10:23 INFO Found ida flag, increasing expected speedup by 8.0%
2014-01-23 12:10:23 INFO CPU Frequency Speed Up: 3.81
2014-01-23 12:10:23 INFO Measured Speed Up: 5.00
2014-01-23 12:10:23 INFO Percentage Difference 31.4%
2014-01-23 12:10:23 ERRORMeasured speedup vs expected speedup is 31.4% and 
is not within 10.0% margin.
2014-01-23 12:10:23 INFO On Demand Governor Test:
2014-01-23 12:10:23 INFO -
2014-01-23 12:10:23 INFO Setting governor to ondemand
2014-01-23 12:10:23 INFO Waiting 5 seconds...
2014-01-23 12:10:28 INFO Done.
2014-01-23 12:10:28 INFO Running CPU load test...
2014-01-23 12:10:28 INFO pid 4285's current affinity list: 0
2014-01-23 12:10:28 INFO pid 4285's new affinity list: 0
2014-01-23 12:10:28 INFO On Demand load test time: 0.24
2014-01-23 12:10:28 INFO Percentage Difference vs. maximum frequency: 380.0%
2014-01-23 12:10:28 ERROROn demand performance vs maximum of 380.0% is not 
within 10.0% margin
2014-01-23 12:10:28 INFO Waiting 5 seconds...
2014-01-23 12:10:33 INFO Done.
2014-01-23 12:10:33 INFO Performance Governor Test:
2014-01-23 12:10:33 INFO -
2014-01-23 12:10:33 INFO Setting governor to performance
2014-01-23 12:10:33 INFO Running CPU load test...
2014-01-23 12:10:33 INFO pid 4285's current affinity list: 0
2014-01-23 12:10:33 INFO pid 4285's new affinity list: 0
2014-01-23 12:10:33 INFO Performance load test time: 0.05
2014-01-23 12:10:33 INFO Percentage Difference vs. maximum frequency: 0.0%
2014-01-23 12:10:33 INFO Conservative Governor Test:
2014-01-23 12:10:33 INFO -
2014-01-23 12:10:33 INFO Setting governor to conservative
2014-01-23 12:10:33 INFO Waiting 10 seconds...
2014-01-23 12:10:43 INFO Done.
2014-01-23 12:10:43 INFO Running CPU load test...
2014-01-23 12:10:43 INFO pid 4285's current affinity list: 0
2014-01-23 12:10:43 INFO pid 4285's new affinity list: 0
2014-01-23 12:10:44 INFO Conservative load test time: 0.24
2014-01-23 12:10:44 INFO Percentage Difference vs. minimum frequency: 4.0%
2014-01-23 12:10:44 INFO Restoring original governor to ondemand


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

Title:
  [Dell 

[Kernel-packages] [Bug 1264346] Re: [Dell Latitude E6520] After suspend, machine very slow with ondemand governor

[Laurent Bonnaud]

I changed the bug description to state the difficulty of reproducing
this bug.


** Description changed:

- After a suspend/resume using the ondemand governor the system is very slow to 
answer some inputs. The text output pauses for several seconds while I am 
typing this text. Trying to scroll a firefox window takes several seconds. 
Switching tabs in firefox takes several seconds:
+ After several suspend/resume cycles and several days of uptime, using the 
ondemand governor the system is very slow to answer some inputs. The text 
output pauses for several seconds while I am typing this text. Trying to scroll 
a firefox window takes several seconds. Switching tabs in firefox takes several 
seconds:
  cat /sys/devices/system/cpu/c*/cpufreq/scaling_governor
  ondemand
  ondemand
  ondemand
  ondemand
  
  WORKAROUND: Setting the governor to performance fixes this problem.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-15-generic 3.11.0-15.23
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   2373 F pulseaudio
  Date: Thu Dec 26 18:17:23 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
  InstallationDate: Installed on 2013-04-27 (243 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-01 (86 days ago)
  dmi.bios.date: 02/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  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.:bvrA12:bd02/28/2012:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

Title:
  [Dell Latitude E6520] After suspend, machine very slow with ondemand
  governor

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After several suspend/resume cycles and several days of uptime, using the 
ondemand governor the system is very slow to answer some inputs. The text 
output pauses for several seconds while I am typing this text. Trying to scroll 
a firefox window takes several seconds. Switching tabs in firefox takes several 
seconds:
  cat /sys/devices/system/cpu/c*/cpufreq/scaling_governor
  ondemand
  ondemand
  ondemand
  ondemand

  WORKAROUND: Setting the governor to performance fixes this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-15-generic 3.11.0-15.23
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   2373 F pulseaudio
  Date: Thu Dec 26 18:17:23 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
  InstallationDate: Installed on 2013-04-27 (243 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-01 (86 days ago)
  dmi.bios.date: 02/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  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.:bvrA12:bd02/28/2012: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:

[Kernel-packages] [Bug 1264346] Re: machine very slow with ondemand governor

[Laurent Bonnaud]

Running frequency_governors_test sheds some light on this bug because it
exposes this error:

ERROROn demand performance vs maximum of 380.0% is not within 10.0%
margin

# /usr/lib/checkbox/bin/frequency_governors_test
2013-12-26 18:15:54 INFO System Capabilites:
2013-12-26 18:15:54 INFO -
2013-12-26 18:15:54 INFO System has 4 cpus
2013-12-26 18:15:54 INFO Supported CPU Frequencies: 
2013-12-26 18:15:54 INFO 2801 MHz
2013-12-26 18:15:54 INFO 2800 MHz
2013-12-26 18:15:54 INFO 2600 MHz
2013-12-26 18:15:54 INFO 2400 MHz
2013-12-26 18:15:54 INFO 2200 MHz
2013-12-26 18:15:54 INFO 2000 MHz
2013-12-26 18:15:54 INFO 1800 MHz
2013-12-26 18:15:54 INFO 1600 MHz
2013-12-26 18:15:54 INFO 1400 MHz
2013-12-26 18:15:54 INFO 1200 MHz
2013-12-26 18:15:54 INFO 1000 MHz
2013-12-26 18:15:54 INFO 800 MHz
2013-12-26 18:15:54 INFO Supported Governors: 
2013-12-26 18:15:54 INFO conservative
2013-12-26 18:15:54 INFO ondemand
2013-12-26 18:15:54 INFO userspace
2013-12-26 18:15:54 INFO powersave
2013-12-26 18:15:54 INFO performance
2013-12-26 18:15:54 INFO Current governors:
2013-12-26 18:15:54 INFO cpu0: conservative
2013-12-26 18:15:54 INFO cpu1: conservative
2013-12-26 18:15:54 INFO cpu2: conservative
2013-12-26 18:15:54 INFO cpu3: conservative
2013-12-26 18:15:54 INFO Beginning Frequency Governors Testing
2013-12-26 18:15:54 INFO Userspace Governor Test:
2013-12-26 18:15:54 INFO -
2013-12-26 18:15:54 INFO Setting governor to userspace
2013-12-26 18:16:25 INFO Setting CPU frequency to 800 MHz
2013-12-26 18:16:25 INFO Running CPU load test...
2013-12-26 18:16:25 INFO pid 4613's current affinity list: 0-3
2013-12-26 18:16:25 INFO pid 4613's new affinity list: 0
2013-12-26 18:16:25 INFO Minimum frequency load test time: 0.23
2013-12-26 18:16:25 INFO Setting CPU frequency to 2801 MHz
2013-12-26 18:16:25 INFO Running CPU load test...
2013-12-26 18:16:25 INFO pid 4613's current affinity list: 0
2013-12-26 18:16:25 INFO pid 4613's new affinity list: 0
2013-12-26 18:16:25 INFO Maximum frequency load test time: 0.05
2013-12-26 18:16:25 INFO Found ida flag, increasing expected speedup by 8.0%
2013-12-26 18:16:25 INFO CPU Frequency Speed Up: 3.81
2013-12-26 18:16:25 INFO Measured Speed Up: 4.60
2013-12-26 18:16:25 INFO Percentage Difference 20.9%
2013-12-26 18:16:25 ERRORMeasured speedup vs expected speedup is 20.9% and 
is not within 10.0% margin.
2013-12-26 18:16:25 INFO On Demand Governor Test:
2013-12-26 18:16:25 INFO -
2013-12-26 18:16:25 INFO Setting governor to ondemand
2013-12-26 18:16:25 INFO Waiting 5 seconds...
2013-12-26 18:16:30 INFO Done.
2013-12-26 18:16:30 INFO Running CPU load test...
2013-12-26 18:16:30 INFO pid 4613's current affinity list: 0
2013-12-26 18:16:30 INFO pid 4613's new affinity list: 0
2013-12-26 18:16:31 INFO On Demand load test time: 0.24
2013-12-26 18:16:31 INFO Percentage Difference vs. maximum frequency: 380.0%
2013-12-26 18:16:31 ERROROn demand performance vs maximum of 380.0% is not 
within 10.0% margin
2013-12-26 18:16:31 INFO Waiting 5 seconds...
2013-12-26 18:16:36 INFO Done.
2013-12-26 18:16:36 INFO Performance Governor Test:
2013-12-26 18:16:36 INFO -
2013-12-26 18:16:36 INFO Setting governor to performance
2013-12-26 18:16:36 INFO Running CPU load test...
2013-12-26 18:16:36 INFO pid 4613's current affinity list: 0
2013-12-26 18:16:36 INFO pid 4613's new affinity list: 0
2013-12-26 18:16:36 INFO Performance load test time: 0.05
2013-12-26 18:16:36 INFO Percentage Difference vs. maximum frequency: 0.0%
2013-12-26 18:16:36 INFO Conservative Governor Test:
2013-12-26 18:16:36 INFO -
2013-12-26 18:16:36 INFO Setting governor to conservative
2013-12-26 18:16:36 INFO Waiting 10 seconds...
2013-12-26 18:16:46 INFO Done.
2013-12-26 18:16:46 INFO Running CPU load test...
2013-12-26 18:16:46 INFO pid 4613's current affinity list: 0
2013-12-26 18:16:46 INFO pid 4613's new affinity list: 0
2013-12-26 18:16:47 ERRORCould not repeat load test times within 5.0%
2013-12-26 18:16:47 ERRORNo Conservative load test time available.
2013-12-26 18:16:47 ERRORNot enough timing data to calculate speed 
differences.
2013-12-26 18:16:47 INFO Restoring original governor to conservative

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

Title:
  machine very slow with ondemand 

[Kernel-packages] [Bug 1264346] Re: machine very slow with ondemand governor

[Laurent Bonnaud]

This bug is similar to bug #326149 but I preferred to report a new one because 
this other bug:
 - is closed
 - concerns a very old kernel
 - concerns a very different processor

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

Title:
  machine very slow with ondemand governor

Status in “linux” package in Ubuntu:
  New

Bug description:
  On my laptop with this CPU:

  model name  : Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz

  I am using the ondemand governor:

  $ cat /sys/devices/system/cpu/c*/cpufreq/scaling_governor 
  ondemand
  ondemand
  ondemand
  ondemand

  and the system is very slow to answer some inputs:
   - the text output pauses for several seconds while I am typing this text
   - trying to scroll a firefox window takes several seconds
   - switching tabs in firefox takes several seconds
   - ...

  Setting the governor to performance fixes this problem.

  Note that this bug does not reveal itself immediately after boot.  It
  takes a suspend/resume to show up.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-15-generic 3.11.0-15.23
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   2373 F pulseaudio
  Date: Thu Dec 26 18:17:23 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
  InstallationDate: Installed on 2013-04-27 (243 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-01 (86 days ago)
  dmi.bios.date: 02/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  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.:bvrA12:bd02/28/2012: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/1264346/+subscriptions

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

[Kernel-packages] [Bug 1264346] [NEW] machine very slow with ondemand governor

[Laurent Bonnaud]

Public bug reported:

On my laptop with this CPU:

model name  : Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz

I am using the ondemand governor:

$ cat /sys/devices/system/cpu/c*/cpufreq/scaling_governor 
ondemand
ondemand
ondemand
ondemand

and the system is very slow to answer some inputs:
 - the text output pauses for several seconds while I am typing this text
 - trying to scroll a firefox window takes several seconds
 - switching tabs in firefox takes several seconds
 - ...

Setting the governor to performance fixes this problem.

Note that this bug does not reveal itself immediately after boot.  It
takes a suspend/resume to show up.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-15-generic 3.11.0-15.23
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bonnaudl   2373 F pulseaudio
Date: Thu Dec 26 18:17:23 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
InstallationDate: Installed on 2013-04-27 (243 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MachineType: Dell Inc. Latitude E6520
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-15-generic N/A
 linux-backports-modules-3.11.0-15-generic  N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-10-01 (86 days ago)
dmi.bios.date: 02/28/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
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.:bvrA12:bd02/28/2012:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug package-from-proposed saucy third-party-packages

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

Title:
  machine very slow with ondemand governor

Status in “linux” package in Ubuntu:
  New

Bug description:
  On my laptop with this CPU:

  model name  : Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz

  I am using the ondemand governor:

  $ cat /sys/devices/system/cpu/c*/cpufreq/scaling_governor 
  ondemand
  ondemand
  ondemand
  ondemand

  and the system is very slow to answer some inputs:
   - the text output pauses for several seconds while I am typing this text
   - trying to scroll a firefox window takes several seconds
   - switching tabs in firefox takes several seconds
   - ...

  Setting the governor to performance fixes this problem.

  Note that this bug does not reveal itself immediately after boot.  It
  takes a suspend/resume to show up.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-15-generic 3.11.0-15.23
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   2373 F pulseaudio
  Date: Thu Dec 26 18:17:23 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
  InstallationDate: Installed on 2013-04-27 (243 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Dell Inc. Latitude E6520
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-01 (86 days ago)
  dmi.bios.date: 02/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  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.:bvrA12:bd02/28/2012: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/1264346/+subscriptions

-- 
Mailing list: