[Kernel-packages] [Bug 2036428] Re: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1

[Sven Mohr]

I can confirm that the bug related to Intel AX201 Bluetooth not being
available has been fixed with the latest release.

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

Title:
  Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1

Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  After upgrading linux-firmware to 20230915.gitdfa11466-0ubuntu1, my
  Intel AX201 Bluetooth controller is not available post-reboot.

  The device itself shows up here:

  $ lsusb | grep -i blue
  Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth

  But running e.g. `dmesg | grep -i bluetooth` returns no matches, and
  bluetoothctl finds no controllers.

  Reverting to the 20230323.gitbcdcfbcf-0ubuntu1.6 package restores full
  functionality.

  n.b. Possible duplicate of LP:2036348 - I am not in a position to
  confirm those symptoms yet, but will update later.

  Running mantic pre-release on amd64:

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

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


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

[Kernel-packages] [Bug 2019855] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-

[Sven Broemer]

Public bug reported:

This bug occured while upgrade to lunar lobster. 
parallels@ubuntu-linux-20-04-desktop:~$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.04
Release:23.04
parallels@ubuntu-linux-20-04-desktop:~$ cat version.log 
Ubuntu 5.19.0-42.43-generic 5.19.17

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
Uname: Linux 5.19.0-42-generic aarch64
NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg
ApportVersion: 2.26.1-0ubuntu2
Architecture: arm64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  parallels   2242 F wireplumber
 /dev/snd/seq:parallels   2235 F pipewire
CasperMD5CheckResult: pass
Date: Tue May 16 13:14:14 2023
ErrorMessage: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2021-03-13 (794 days ago)
InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release arm64 
(20210201.2)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
Lspci-vt:
 -[:00]-+-01.0  Intel Corporation 82801I (ICH9 Family) HD Audio Controller
+-02.0  Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 
EHCI Controller
+-03.0  NEC Corporation uPD720200 USB 3.0 Host Controller
+-09.0  Parallels, Inc. Virtual Machine Communication Interface
\-0a.0  Red Hat, Inc. Virtio GPU
MachineType: Parallels International GmbH. Parallels ARM Virtual Machine
ProcFB: 0 virtio_gpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=732910d6-ddae-4a95-ab9e-9f5c9edc555a ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
RfKill:
 
SourcePackage: linux
Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to lunar on 2023-05-16 (0 days ago)
acpidump:
 
dmi.bios.date: Fri, 10 Feb 2023 10:16:42
dmi.bios.release: 0.1
dmi.bios.vendor: Parallels International GmbH.
dmi.bios.version: 18.2.0 (53488)
dmi.board.asset.tag: None
dmi.board.name: Parallels ARM Virtual Platform
dmi.board.vendor: Parallels ARM Virtual Machine
dmi.board.version: 0.1
dmi.chassis.type: 2
dmi.chassis.vendor: Parallels International GmbH.
dmi.modalias: 
dmi:bvnParallelsInternationalGmbH.:bvr18.2.0(53488):bdFri,10Feb2023101642:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM:
dmi.product.family: Parallels VM
dmi.product.name: Parallels ARM Virtual Machine
dmi.product.sku: Parallels_ARM_VM
dmi.product.version: 0.1
dmi.sys.vendor: Parallels International GmbH.
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


** Tags: apport-package arm64 lunar

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/2019855/+attachment/5673325/+files/lspci-vnvn.log

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: »installiertes post-installation-Skript des Paketes
  linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1
  zurück

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug occured while upgrade to lunar lobster. 
  parallels@ubuntu-linux-20-04-desktop:~$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04
  parallels@ubuntu-linux-20-04-desktop:~$ cat version.log 
  Ubuntu 5.19.0-42.43-generic 5.19.17

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
  Uname: Linux 5.19.0-42-generic aarch64
  NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  parallels   2242 F wireplumber
   /dev/snd/seq:parallels   2235 F pipewire
  CasperMD5CheckResult: pass
  Date: Tue May 16 13:14:14 2023
  ErrorMessage: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
  

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

[Kernel-packages] [Bug 2018773] IwConfig.txt

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

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

[Sven Fuelster]

apport information

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
    sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:    sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version: 8.04
  dmi.sys.vendor: Razer

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


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

[Kernel-packages] [Bug 2018773] Re: Ubuntu 23.04 does not suspend laptop on lid close

[Sven Fuelster]

apport information

** Tags added: apport-collected

** Description changed:

- Razer Blade 15, 2022 model, no suspend on lid close, causing the system
- to overheat until system freeze, no safety shutdown either
+ Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.26.1-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  sven   2004 F pipewire
+   sven   2007 F wireplumber
+  /dev/snd/controlC0:  sven   2007 F wireplumber
+  /dev/snd/seq:sven   2004 F pipewire
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.04
+ InstallationDate: Installed on 2023-04-23 (15 days ago)
+ InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
+ MachineType: Razer Blade 15 (2022) - RZ09-0421
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/zsh
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
+ RelatedPackageVersions:
+  linux-restricted-modules-6.2.0-20-generic N/A
+  linux-backports-modules-6.2.0-20-generic  N/A
+  linux-firmware20230323.gitbcdcfbcf-0ubuntu1
+ Tags:  lunar
+ Uname: Linux 6.2.0-20-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sudo users
+ _MarkForUpload: True
+ dmi.bios.date: 02/11/2022
+ dmi.bios.release: 1.7
+ dmi.bios.vendor: Razer
+ dmi.bios.version: 1.07
+ dmi.board.name: CH580
+ dmi.board.vendor: Razer
+ dmi.board.version: 4
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Razer
+ dmi.ec.firmware.release: 1.1
+ dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
+ dmi.product.family: 1A58201B Razer Blade
+ dmi.product.name: Blade 15 (2022) - RZ09-0421
+ dmi.product.sku: RZ09-0421PGF3
+ dmi.product.version: 8.04
+ dmi.sys.vendor: Razer

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

Title:
  Ubuntu 23.04 does not suspend laptop on lid close

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Razer Blade 15, 2022 model, no suspend on lid close, causing the system to 
overheat until system freeze, no safety shutdown either
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sven   2004 F pipewire
sven   2007 F wireplumber
   /dev/snd/controlC0:  sven   2007 F wireplumber
   /dev/snd/seq:sven   2004 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-04-23 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Razer Blade 15 (2022) - RZ09-0421
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 1.7
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.07
  dmi.board.name: CH580
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnRazer:bvr1.07:bd02/11/2022:br1.7:efr1.1:svnRazer:pnBlade15(2022)-RZ09-0421:pvr8.04:rvnRazer:rnCH580:rvr4:cvnRazer:ct10:cvr:skuRZ09-0421PGF3:
  dmi.product.family: 1A58201B Razer Blade
  dmi.product.name: Blade 15 (2022) - RZ09-0421
  dmi.product.sku: RZ09-0421PGF3
  dmi.product.version

[Kernel-packages] [Bug 2008774] Re: Ubuntu 22.04 not waking up after second suspend

[Sven Schultschik]

I have an Lenovo T16 AMD Ryzen 7 6850U and the amdgpu-install fixed the
balck screen suspend bug, but since then my CPU usage is much higher in
idle and the fan is permanently running.

I'm currently limited to Ubuntu 22.04 and have to wait for the next LTS
version.

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

Title:
  Ubuntu 22.04 not waking up after second suspend

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

Bug description:
  After the first suspend it wakes up just fine - it's the second
  suspend after which the screen stays blank and keyboard doesn't react
  (although the power LED starts glowing). It happens if I close the
  laptop's lid or do a manual suspend via the system menu. It happens
  only recently (I think after some kernel update, but I'm not sure
  about this) - before it worked fine for month (since I installed
  Ubuntu).

  I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the
  only OS (if that's important).

  What I tried:

  * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896)
  * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896)
  * I looked through the logs in /var/log but couldn't find anything obvious to 
me (but I'm not a Linux guru).

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

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


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

[Kernel-packages] [Bug 2017227] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Un

[Sven Jäger]

Removing dkms, changing the kernel, and reinstalling it worked. Thank
you.

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: »installiertes post-installation-Skript des Paketes
  linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1
  zurück

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I got an error message during updating from Ubuntu 22.10 to 23.04

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaeger 2885 F wireplumber
   /dev/snd/seq:jaeger 2882 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Apr 21 11:52:56 2023
  ErrorMessage: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2022-12-06 (135 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Latitude 5530
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago)
  dmi.bios.date: 03/17/2023
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0C6CYC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd03/17/2023:br1.12:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn0C6CYC:rvrA00:cvnDellInc.:ct10:cvr:sku0B06:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5530
  dmi.product.sku: 0B06
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


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

[Kernel-packages] [Bug 2017227] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Un

[Sven Jäger]

** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017227/+attachment/5670548/+files/make.log

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: »installiertes post-installation-Skript des Paketes
  linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1
  zurück

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I got an error message during updating from Ubuntu 22.10 to 23.04

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaeger 2885 F wireplumber
   /dev/snd/seq:jaeger 2882 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Apr 21 11:52:56 2023
  ErrorMessage: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2022-12-06 (135 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Latitude 5530
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago)
  dmi.bios.date: 03/17/2023
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0C6CYC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd03/17/2023:br1.12:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn0C6CYC:rvrA00:cvnDellInc.:ct10:cvr:sku0B06:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5530
  dmi.product.sku: 0B06
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


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

[Kernel-packages] [Bug 1994516] Re: Kernels after 5.16 cannot execute x32-ABI binaries

[Sven Hartrumpf]

Hi Dimitri.

Thanks for your long answer where you explain the Ubuntu view. It is a
pity that x32 was dropped from its kernel, but I can understand the
reasoning ... I hope x32 will gain some momentum elsewhere.

It would be really helpful if at least the existing x32 support in
Ubuntu (I mean x32 packages, gcc/clang archs) would be maintained.

Greetings
Sven

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 2017227] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-

[Sven Jäger]

Public bug reported:

I got an error message during updating from Ubuntu 22.10 to 23.04

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jaeger 2885 F wireplumber
 /dev/snd/seq:jaeger 2882 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri Apr 21 11:52:56 2023
ErrorMessage: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2022-12-06 (135 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Dell Inc. Latitude 5530
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu16
SourcePackage: linux
Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago)
dmi.bios.date: 03/17/2023
dmi.bios.release: 1.12
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.0
dmi.board.name: 0C6CYC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd03/17/2023:br1.12:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn0C6CYC:rvrA00:cvnDellInc.:ct10:cvr:sku0B06:
dmi.product.family: Latitude
dmi.product.name: Latitude 5530
dmi.product.sku: 0B06
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


** Tags: amd64 apport-package lunar

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: »installiertes post-installation-Skript des Paketes
  linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1
  zurück

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I got an error message during updating from Ubuntu 22.10 to 23.04

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaeger 2885 F wireplumber
   /dev/snd/seq:jaeger 2882 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Apr 21 11:52:56 2023
  ErrorMessage: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2022-12-06 (135 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Latitude 5530
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago)
  dmi.bios.date: 03/17/2023
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0C6CYC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd03/17/2023:br1.12:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn0C6CYC:rvrA00:cvnDellInc.:ct10:cvr:sku0B06:
  dmi.product.family: Latitude
  

[Kernel-packages] [Bug 1994516] Re: Kernels after 5.16 cannot execute x32-ABI binaries

[Sven Hartrumpf]

Yes, in my initial message, I described this Debian approach.

So, has Ubuntu decided to not follow this approach and give up the X32 ABI for 
its kernels?
Would be a pity.

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 1994516] Re: Kernels after 5.16 cannot execute x32-ABI binaries

[Sven Hartrumpf]

Thanks for checking this bug, @doko. Do the added tags means that it
will be fixed for 22.10 and 23.04?

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 1994516] Re: Kernels after 5.16 cannot execute x32-ABI binaries

[Sven Hartrumpf]

This bug even affects 22.04 LTS if using HWE because linux-generic-
hwe-22.04 does not support the X32 ABI.

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18

[Sven Kieske]

The above comment might not be correct, because it turned out one of the
micron nvme devices had a defect and was not recognized by any hardware
at all, even when not hot swapping.

There is a chance that this is related to the bios/firmware combination
on this supermicro model.

I will test this again with a known working micron nvme and the
following scenarios:

- hotswap intel -> micron
- hotswap micron -> micron

both will first be tested on the linux-generic-hwe-18.04
5.4.0.135.152~18 kernel.

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

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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

[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18

[Sven Kieske]

I was finally able to test this with the mainline kernel:

6.1.10-060110-generic #202302060840

taken from: https://kernel.ubuntu.com/~kernel-
ppa/mainline/v6.1.10/amd64/linux-image-
unsigned-6.1.10-060110-generic_6.1.10-060110.202302060840_amd64.deb

and it works!

this is specific about hot swap.

i suspect the following commits are missing from the HWE kernel in
18.04. to make this work:

2baa85d6927d11b8d946da2e4ad00dddca5b8da2
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2baa85d6927d11b8d946da2e4ad00dddca5b8da2)

and 85ae3970a0e393cbb07ec30ac99d82cfd6c3f922
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=85ae3970a0e393cbb07ec30ac99d82cfd6c3f922)

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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

[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

[Sven Kieske]

okay, it seems that both acpi_pci_hotplug and pci_hotplug are enabled
for this kernel:

grep "CONFIG_HOTPLUG_PCI_ACPI=" /boot/config-`uname -r`
CONFIG_HOTPLUG_PCI_ACPI=y
grep "CONFIG_HOTPLUG_PCI=" /boot/config-`uname -r`
CONFIG_HOTPLUG_PCI=y

but still, hotplug is not working.

the current situation is: I unplugged a correctly recognized Intel NVME
and switched it for a Micron NVME, there is also a second intel nvme
still installed.

nvme list shows the intel nvme which remained in the system:

nvme list
Node SN   Model
Namespace Usage  Format   FW Rev  
   
- --  
/dev/nvme0n1 PHLN130100QJ1P6AGN   INTEL SSDPE2KE016T8  
1   1.60  TB /   1.60  TB512   B +  0 B   VDV10184

but when I look into /sys/, I still find shadows of the other intel
nvme, which just got plugged out:

find /sys/devices | egrep "nvme[0-9][0-9]?$"
/sys/devices/pci:40/:40:01.1/:41:00.0/nvme/nvme0
/sys/devices/virtual/nvme-subsystem/nvme-subsys1/nvme1
/sys/devices/virtual/nvme-subsystem/nvme-subsys0/nvme0

also, nvme list-subsys, throws an error. I suppose because that old
subsystem nvme-subsys1 does no longer exist, but is still referenced:

nvme list-subsys
free(): double free detected in tcache 2
Aborted

googling the above error leads me to this bug report:
https://github.com/linux-nvme/nvme-cli/issues/1707

when rescanning the pci bus via:

echo 1 > /sys/bus/pci/rescan

I get the following messages in dmesg:

[Wed Feb  8 10:20:49 2023] pci :c3:00.0: PCI bridge to [bus c4]
[Wed Feb  8 10:20:49 2023] pci :c3:00.0:   bridge window [io  0xf000-0x]
[Wed Feb  8 10:20:49 2023] pci :c3:00.0:   bridge window [mem 
0xb800-0xb90f]
[Wed Feb  8 10:20:49 2023] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
[Wed Feb  8 10:20:49 2023] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
[Wed Feb  8 10:20:49 2023] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
[Wed Feb  8 10:20:49 2023] pcieport :40:01.1: BAR 13: failed to assign [io  
size 0x1000]
[Wed Feb  8 10:20:49 2023] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
[Wed Feb  8 10:20:49 2023] pcieport :40:01.2: BAR 13: failed to assign [io  
size 0x1000]
[Wed Feb  8 10:20:49 2023] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
[Wed Feb  8 10:20:49 2023] pcieport :40:01.2: BAR 13: failed to assign [io  
size 0x1000]
[Wed Feb  8 10:20:49 2023] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
[Wed Feb  8 10:20:49 2023] pcieport :40:01.1: BAR 13: failed to assign [io  
size 0x1000]

as already stated in the original bug report.

how can I get rid of the now defunct nvme subsystem? anything else I
could try?

** Bug watch added: github.com/linux-nvme/nvme-cli/issues #1707
   https://github.com/linux-nvme/nvme-cli/issues/1707

** Summary changed:

- pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18
+ pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, 

[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

[Sven Kieske]

as already stated above I did provide log files manually, as apport-
collect is not installed on this system.

I'm happy to provide further logfiles to debug this issue.

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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

[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

[Sven Kieske]

my vendor told me this should work with updated bios and firmware, which
it does not.

in fact, I can't even find the pci hotplug kernel module, neither
loaded, nor present under /lib/modules/*.

so could you please reopen, so we can double check I'm not missing
anything from the ubuntu side?

currently I have upgraded to the official 18.04 HWE Kernel
5.4.0-135-generic #152

when I e.g. grep for hotplug on a fedora test laptop I get:

grep -i hotplug /lib/modules/6.1.8-100.fc36.x86_64/modules.builtin
kernel/drivers/pci/hotplug/shpchp.ko
kernel/drivers/pci/hotplug/acpiphp.ko


but the ubuntu system returns:

root@ceph-osd01:~# grep -i hotplug 
/lib/modules/5.4.0-135-generic/modules.builtin
root@ceph-osd01:~# 


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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

Status in linux package in Ubuntu:
  New

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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

[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

[Sven Kieske]

Our vendor told us that this is a generic problem with the following
supermicro board/system and many nvme ssd devices:

Board: H12SSW-NT

Servertype: Supermicro AS -1114S-WTRT
https://www.supermicro.com/Aplus/system/1U/1114/AS-1114S-WTRT.cfm

so it seems this is not kernel related, afaik.

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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

[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

[Sven Kieske]

I wasn't able to test this just yet as I have limited time for debugging
this and it is a production system, so I need to prepare maintenance
etc. so it might take some time.

Do you have any information if this is supposed to work on this kernel?

I saw some patches afaik from 2017~2019 which addressed problems in this
area, but I don't know yet if they made it to the ubuntu kernel.

I will report back if a newer kernel fixes this. We are only using
offical HWE Kernels from Ubuntu LTS releases at the moment though.

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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

[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages

[Sven Kieske]

so, we seem to have a dependency problem here, no?

for reference, this is fixed by:

apt install linux-tools-common

but why was "linux-tools-common" not installed as a part of "linux-
tools-generic-hwe-18.04"?

this is the dependency chain:

root@ceph-osd03:~# apt-cache depends linux-tools-generic-hwe-18.04
linux-tools-generic-hwe-18.04
  Depends: linux-tools-5.4.0-132-generic
root@ceph-osd03:~# apt-cache depends linux-tools-5.4.0-132-generic
linux-tools-5.4.0-132-generic
  Depends: linux-hwe-5.4-tools-5.4.0-132
root@ceph-osd03:~# apt-cache depends linux-hwe-5.4-tools-5.4.0-132
linux-hwe-5.4-tools-5.4.0-132
  Depends: libc6
  Depends: libcap2
  Depends: libdw1
  Depends: libelf1
  Depends: liblzma5
  Depends: libnuma1
  Depends: libpci3
  Depends: libslang2
  Depends: libssl1.1
  Depends: libudev1
  Depends: libunwind8
  Depends: zlib1g
  Depends: linux-hwe-5.4-tools-common
root@ceph-osd03:~# apt-cache depends linux-hwe-5.4-tools-common
linux-hwe-5.4-tools-common
  Depends: lsb-release
root@ceph-osd03:~# dpkg -S linux-hwe-5.4-tools-common
linux-hwe-5.4-tools-common: /usr/share/doc/linux-hwe-5.4-tools-common
linux-hwe-5.4-tools-common: /usr/share/doc/linux-hwe-5.4-tools-common/copyright
linux-hwe-5.4-tools-common: 
/usr/share/doc/linux-hwe-5.4-tools-common/changelog.Debian.gz

nothing installs /usr/bin/cpupower (that is, "linux-tools-common").

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

Title:
  HWE kernels do not ship linux-tools packages

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Invalid

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

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


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

[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages

[Sven Kieske]

** Changed in: linux-meta-hwe-5.4 (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  HWE kernels do not ship linux-tools packages

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Invalid

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

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


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

[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages

[Sven Kieske]

also:

 cpupower --help
bash: cpupower: command not found

type cpupower
-su: type: cpupower: not found

command cpupower
-su: cpupower: command not found


/usr/lib/linux-hwe-5.4-tools-5.4.0-132/cpupower
Usage:  cpupower [-d|--debug] [-c|--cpu cpulist ]  []
Supported commands are:
frequency-info
frequency-set
idle-info
idle-set
set
info
monitor
help

Not all commands can make use of the -c cpulist option.

Use 'cpupower help ' for getting help for above commands.

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

Title:
  HWE kernels do not ship linux-tools packages

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Confirmed

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

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


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

[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages

[Sven Kieske]

I'm sorry, but can you show me your $PATH?

According to: https://packages.ubuntu.com/bionic-updates/amd64/linux-
tools-5.4.0-132-generic/filelist

cpupower get's installed into the following path:

/usr/lib/linux-tools/5.4.0-132-generic/cpupower

which seems to be a symlink, according to my system, to:

ls -lashin /usr/lib/linux-tools/5.4.0-132-generic/cpupower
2546080 0 lrwxrwxrwx 1 0 0 44 Oct 24 15:52 
/usr/lib/linux-tools/5.4.0-132-generic/cpupower -> 
../../linux-hwe-5.4-tools-5.4.0-132/cpupower

ls -lashin /usr/lib/linux-hwe-5.4-tools-5.4.0-132/cpupower 
2546021 292K -rwxr-xr-x 1 0 0 290K Oct 24 15:52 
/usr/lib/linux-hwe-5.4-tools-5.4.0-132/cpupower

but if I'm not terribly mistaken /usr/lib/ is on no default $PATH, see
this system:

echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

or also these answers, neither contain /usr/lib/ in $PATH?

https://askubuntu.com/questions/386629/what-are-the-default-path-values

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

Title:
  HWE kernels do not ship linux-tools packages

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Confirmed

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

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


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

[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

[Sven Kieske]

apport-collect is not installed on this system.

I added some manually collected logs. If you need further debug data,
please specify what exactly you need and I will try to provide it.

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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

[Kernel-packages] [Bug 1998224] [NEW] pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

[Sven Kieske]

Public bug reported:

situation: ubuntu 18.04 server install on a supermicro x64 host.

hot plug NVME ssd into NVME U.2 HotSwap Slot.

problem: hot plug does not work/ nvme is not recognised.

how to test:

echo 1 > /sys/bus/pci/rescan

dmesg output:

[Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
[Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
[Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io  
size 0x1000]

Kernel Version:

5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux

hardware information: tried with micron and intel NVME, e.g:

INTEL SSDPE2KE016T8

after a reboot, the NVME is recognized, so there is no hardware problem.

if you need additional debug information, feel free to ask.

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

** Attachment added: "lspci Output"
   
https://bugs.launchpad.net/bugs/1998224/+attachment/5633192/+files/lspci-vnvn.log

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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

[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

[Sven Kieske]

** Attachment added: "Kernel Version"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+attachment/5633193/+files/version.log

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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

[Kernel-packages] [Bug 1994516] Re: Kernels after 5.16 cannot execute x32-ABI binaries

[Sven Hartrumpf]

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 1994516] ProcEnviron.txt

[Sven Hartrumpf]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1994516/+attachment/5626990/+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/1994516

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

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

[Sven Hartrumpf]

apport information

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 1994516] Re: Kernels after 5.16 cannot execute x32-ABI binaries

[Sven Hartrumpf]

apport information

** Tags added: apport-collected

** Description changed:

  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:
  
  cannot execute binary file: Exec format error
  
  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.
  
  So, the following approach (e.g. Debian) looks more appropriate:
  
  1. Include the x32-relevant code, but disable its use on standard boots:
  
  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y
  
  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option
  
  syscall.x32=y
  
  to enable x32 binaries.
  
- This could be a good compromise between kernel complexity and resource
- efficiency.
+ This could be a good compromise between kernel complexity and resource 
efficiency.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.23.1-0ubuntu3
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2022-10-24 (1 days ago)
+ InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
+ IwConfig:
+  lono wireless extensions.
+  
+  eno1  no wireless extensions.
+ MachineType: ASUS System Product Name
+ Package: linux (not installed)
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
+ RelatedPackageVersions:
+  linux-restricted-modules-5.19.0-23-generic N/A
+  linux-backports-modules-5.19.0-23-generic  N/A
+  linux-firmware 20220923.gitf09bebf3-0ubuntu1
+ RfKill:
+  
+ Tags:  kinetic
+ Uname: Linux 5.19.0-23-generic x86_64
+ UnreportableReason: This report is about a package that is not installed.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: sudo
+ WifiSyslog:
+  
+ _MarkForUpload: False
+ dmi.bios.date: 10/13/2022
+ dmi.bios.release: 8.5
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 0805
+ dmi.board.asset.tag: Default string
+ dmi.board.name: PRIME B650-PLUS
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: System Product Name
+ dmi.product.sku: SKU
+ dmi.product.version: System Version
+ dmi.sys.vendor: ASUS

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 

[Kernel-packages] [Bug 1994516] [NEW] Kernels after 5.16 cannot execute x32-ABI binaries

[Sven Hartrumpf]

Public bug reported:

The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
kernel 5.17 and higher (amd64). x32 binaries are now reporting:

cannot execute binary file: Exec format error

The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
intensive tasks) because it saves CPU time and critical resources like
energy.

So, the following approach (e.g. Debian) looks more appropriate:

1. Include the x32-relevant code, but disable its use on standard boots:

CONFIG_X86_X32=y
CONFIG_X86_X32_DISABLED=y

2. Users that must run x32 binaries can easily add the GRUB cmdline
option

syscall.x32=y

to enable x32 binaries.

This could be a good compromise between kernel complexity and resource
efficiency.

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


** Tags: kinetic x32 x32-abi

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource
  efficiency.

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


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

[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Sven Kieske]

> I am not sure I would still call it a regression and it is certainly
an annoying, but it can be workarounded.

it worked before, now it doesn't without manual intervention, that's the
basic definition of a regression, no?

after all, there are _always_ workarounds for regressions, so I would
not consider it appropriate to call a regression not-a-regression
because there is some workaround available.

we are currently affected by this and need to figure out if the
workaround is even an acceptable solution, because in a cloud
environment you can't/don't want to manually patch libvirt xml for
dozens of machines.

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

Title:
  [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

Status in libvirt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in libvirt source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in qemu source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * CPU definitions are added to libvirt as these CPUs are known
     and added to qemu for execution.
     And due to that over time some are considered missing in
     former releases.

   * To really benefit from the new features of these chips
     they have to be known, therefore new type additions done by
     upstream should be backported if they generally apply and do
     not depend on SRU-critical changes.

   * This backports three upstream fixes that just add definitions
     (no control flow changes)

  [Test Case]

   * Check if it has an EPYC-Rome entry in
     /usr/share/libvirt/cpu_map/index.xml and the file included
     there exists.

   * Define a guest like:
     
   EPYC-Rome
     
     You can only "really" start this on a system with the
     matching HW. But even on others it will change from:
   error: internal error: Unknown CPU model EPYC-Rome
     to being unable to start for some features missing.

   * libvirt probes a system if a named cpu can be used, after the
     fix this should include EPYC-Rome
     $ virsh domcapabilities | grep EPYC
    EPYC-IBPB
    EPYC

  [Regression Potential]

   * Usually these type additions are safe unless they add control flow
     changes (e.g. to handle yet unknown types of registers or such) but
     that isn't the case here.
     A regression if any is to be expected on systems that are close to the
     newly added type(s). Those will after the update be detected as such
     if e.g. host-model is used. If then running on a mixed cluster of
     updated/non-updated systems migrations will only work if the target is
     updated as well.

  [Other Info]

   * This is the first build since glibc 2.32 arrived in groovy, hence we
     need to be careful of the fix done for bug 1892826.
 It has to be checked if the linking is fine after the rebuild.
 The workload still works in groovy despite 2.32 being present (I'd ahve 
 expected it doesn't), so we will keep the revert as-is for now.
 To be sure that adds two tests that shall be done:
     - check the linking to point to libtirpc instead of glibc
   $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep 
GLOBAL
   Was pointing to glibc, does it still and if so does it work (see 
   below)?
     - run the autopkgtest cases as the LXC tests would trigger an issue if
   there is one

  

  ## Qemu SRU ##

  [Impact]

   * CPU definitions are added to qemu as these CPUs are known.
     And due to that over time are missing in former releases.

   * To really benefit from the new features of these chips
     they have to be known, therefore new type additions done by
     upstream should be backported if they generally apply and do
     not depend on SRU-critical changes.

   * This backports two upstream fixes that just add definitions (no
     control flow changes)

  [Test Case]

   * Probe qemu for the known CPU types (works on all HW)
     $ qemu-system-x86_64 -cpu ? | grep EPYC
     Focal without fix:
     x86 EPYC  (alias configured by machine type)
     x86 EPYC-IBPB (alias of EPYC-v2)
     x86 EPYC-v1   AMD EPYC Processor
     x86 EPYC-v2   AMD EPYC Processor (with IBPB)
     Focal with fix also adds:
     x86 EPYC-Rome (alias configured by machine type)
     x86 EPYC-Rome-v1  AMD EPYC-Rome Processor
     x86 EPYC-v3   AMD EPYC Processor

   * Given such HW is available start a KVM guest using those new types
     Since we don't have libvirt support (yet) do so directly in qemu
     commandline like (bootloader is enough)
     $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm 
-nographic
     $ qemu-system-x86_64 -cpu EPYC-v3 -machine 

[Kernel-packages] [Bug 1898909] Re: Installing hwe linux-tools does not provide /usr/bin wrappers

[Sven Kieske]

any update on this?

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

Title:
  Installing hwe linux-tools does not provide /usr/bin wrappers

Status in linux-hwe-5.4 package in Ubuntu:
  Invalid
Status in linux-hwe-5.8 package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 source package in Bionic:
  In Progress
Status in linux-hwe-5.8 source package in Bionic:
  Invalid
Status in linux-hwe-5.4 source package in Focal:
  Invalid
Status in linux-hwe-5.8 source package in Focal:
  Confirmed

Bug description:
  I have a test script that requires /usr/bin/cpupower. Before calling
  it, I 'apt install linux-tools-$(uname -r)' to make sure it is
  available. For GA kernels, this works fine as there is a dependency
  chain on linux-tools-common which provides them. For HWE (tested on
  bionic), this does not work because linux-tools-5.4.0-48-generic
  doesn't depend on linux-tools-common. There is a linux-hwe-5.4-tools-
  common package, but it is empty, and also not a dependency of linux-
  tools-5.4.0-48-generic.

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


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

[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages

[Sven Kieske]

so, this is very weird.

We used to install binary "cpupower" from linux-tools via this package
for the hwe kernel:

linux-tools-generic-hwe-18.04

but this seems to have changed somewhere in between, the file list on
packages.ubuntu.com

only lists:

/usr/share/doc/linux-tools-generic-hwe-18.04/changelog.gz
/usr/share/doc/linux-tools-generic-hwe-18.04/copyright

see, e.g.:
https://packages.ubuntu.com/bionic-updates/amd64/linux-tools-generic-hwe-18.04/filelist
linked from:
https://packages.ubuntu.com/bionic-updates/linux-tools-generic-hwe-18.04

I believe this is, because it's a meta/virtual package?

nevertheless I found how to install "cpupower" it seems it moved to the
following package (adjust kernel subversion as needed):

https://packages.ubuntu.com/bionic-updates/linux-hwe-5.4-tools-5.4.0-80

but this is also strange for several reasons:

first, afaik you need to install the version for your specific installed
kernel, but the package name leads to bad sed-magic in install scripts
like:

apt install linux-hwe-5.4-tools-$(uname -r | sed 's#-generic$##')

this is obviously bad, but I could live with that.

what is really really weird though, is the installation path of the
cpupower binary:

root@server:~# /usr/lib/linux-hwe-5.4-tools-5.4.0-104/cpupower --help
Usage:  cpupower [-d|--debug] [-c|--cpu cpulist ]  []
Supported commands are:
frequency-info
frequency-set
idle-info
idle-set
set
info
monitor
help

Not all commands can make use of the -c cpulist option.

Use 'cpupower help ' for getting help for above commands.


root@server:~# type cpupower
-su: type: cpupower: not found


it is not installed in $PATH at all, which is really contracdicting the 
upstream makefile, imho?

see:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/power/cpupower/Makefile


am I holding it wrong? is there another package which installs cpupower in the 
correct path?

why was the packaging changed, mid release? This breaks every workflow
around the provided tools.

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

Title:
  HWE kernels do not ship linux-tools packages

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Confirmed

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

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


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

[Kernel-packages] [Bug 1956748] [NEW] Long loading time on boot (black screen with blinking stripe)

[Sven]

Public bug reported:

Since I installed 5.13.0-23 the boot time increased by 1 or 2 minutes. This is 
after the boot icon of linux mint. A black screen appears and the logon screen 
will be visible after a while. This is also with the previous versions of this 
kernel. 
5.11* is ok for me.

Problemdevice: Asus FX505DU

version.log output: Ubuntu 5.13.0-23.23~20.04.2-generic 5.13.19

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

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1956748/+attachment/5552394/+files/lspci-vnvn.log

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

Title:
  Long loading time on boot (black screen with blinking stripe)

Status in linux package in Ubuntu:
  New

Bug description:
  Since I installed 5.13.0-23 the boot time increased by 1 or 2 minutes. This 
is after the boot icon of linux mint. A black screen appears and the logon 
screen will be visible after a while. This is also with the previous versions 
of this kernel. 
  5.11* is ok for me.

  Problemdevice: Asus FX505DU

  version.log output: Ubuntu 5.13.0-23.23~20.04.2-generic 5.13.19

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


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

[Kernel-packages] [Bug 1948687] [NEW] Trackpad not detected by kernel

[Sven Serneels]

Public bug reported:

Upon upgrade from Ubuntu 21.04 to 21.10, the kernel stopped detecting the 
trackpad. 
Trackpad does not appear in xinput list nor in cat /proc/bus/input/devices, cf. 
attachment. 
Hardware: Dell Precision 5520. Trackpad should be Synaptics.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-20-generic 5.13.0-20.20
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sven   2598 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 25 11:30:29 2021
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
HibernationDevice: RESUME=UUID=3b49383e-b32b-4f9c-a86f-e0632885f818
InstallationDate: Installed on 2017-04-25 (1644 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5520
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=e5250e21-4f90-4388-b91c-6d1b56038303 ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_default=deep quiet splash i8042.nopnp vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-20-generic N/A
 linux-backports-modules-5.13.0-20-generic  N/A
 linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-10-25 (0 days ago)
dmi.bios.date: 08/10/2021
dmi.bios.release: 1.24
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.24.0
dmi.board.name: 0GPNW9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd08/10/2021:br1.24:svnDellInc.:pnPrecision5520:pvr:sku07BF:rvnDellInc.:rn0GPNW9:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.

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


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

** Attachment added: "output from cat /proc/bus/input/devices"
   https://bugs.launchpad.net/bugs/1948687/+attachment/5535906/+files/devices

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

Title:
  Trackpad not detected by kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Upon upgrade from Ubuntu 21.04 to 21.10, the kernel stopped detecting the 
trackpad. 
  Trackpad does not appear in xinput list nor in cat /proc/bus/input/devices, 
cf. attachment. 
  Hardware: Dell Precision 5520. Trackpad should be Synaptics.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sven   2598 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 11:30:29 2021
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=3b49383e-b32b-4f9c-a86f-e0632885f818
  InstallationDate: Installed on 2017-04-25 (1644 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=e5250e21-4f90-4388-b91c-6d1b56038303 ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_d

[Kernel-packages] [Bug 1948687] Re: Trackpad not detected by kernel

[Sven Serneels]

** Attachment added: "output from cat /proc/bus/input/devices"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948687/+attachment/5535926/+files/devices

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

Title:
  Trackpad not detected by kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Upon upgrade from Ubuntu 21.04 to 21.10, the kernel stopped detecting the 
trackpad. 
  Trackpad does not appear in xinput list nor in cat /proc/bus/input/devices, 
cf. attachment. 
  Hardware: Dell Precision 5520. Trackpad should be Synaptics.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sven   2598 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 11:30:29 2021
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=3b49383e-b32b-4f9c-a86f-e0632885f818
  InstallationDate: Installed on 2017-04-25 (1644 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=e5250e21-4f90-4388-b91c-6d1b56038303 ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_default=deep quiet splash i8042.nopnp vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-25 (0 days ago)
  dmi.bios.date: 08/10/2021
  dmi.bios.release: 1.24
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.24.0
  dmi.board.name: 0GPNW9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd08/10/2021:br1.24:svnDellInc.:pnPrecision5520:pvr:sku07BF:rvnDellInc.:rn0GPNW9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1761557] Re: Qualcom QCA6174 - regdomain: 0x5f

[Sven Hartrumpf]

The bug fix is almost 3 years old. Can anybody apply it?

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1754601] Re: openconnect has trouble maintaining a VPN connection

[Sven N.]

I have a similar issue with a Pulse Secure VPN
After some time and usually after one or more hex dumps were displayed, I get 
the following


SSL read error: Error in the pull function.; reconnecting.
SSL negotiation with ...
Connected to HTTPS on ...
Got HTTP response: HTTP/1.1 101 Switching Protocols

After that the VPN isn't working anymore and I neet to reconnect.


OpenConnect version v8.05-1
Using GnuTLS. Features present: TPMv2, PKCS#11, RSA software token, HOTP 
software token, TOTP software token, Yubikey OATH, System keys, DTLS, ESP
Supported protocols: anyconnect (default), nc, gp, pulse

This version is included in Ubuntu 20.04.

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

Title:
  openconnect has trouble maintaining a VPN connection

Status in linux package in Ubuntu:
  Triaged
Status in openconnect package in Ubuntu:
  Confirmed

Bug description:
  Some time after upgrading to Bionic, I have found that openconnect has
  some trouble keeping a VPN connection open to our company VPN.  Since
  openconnect in Bionic seems to be based on the same upstream release
  as in Artful I assume that the problem is more likely to be in the
  kernel, and the timing of when it started could fit the kernel upgrade
  from 4.13 to 4.15..  I regularly see this in the output:

  SSL read error: Error in the pull function.; reconnecting.
  SSL negotiation with 
  SSL connection failure: The operation timed out
  sleep 10s, remaining timeout 300s
  SSL negotiation with 
  SSL connection failure: The operation timed out
  sleep 20s, remaining timeout 290
  ...

  Interestingly I just now saw it recover from that problem for the
  first time I am aware of.

  I know that it would make sense to test it with the old kernel, and I
  will try that some time (I don't reboot that often, and am not always
  on VPN).  In the mean time, I am creating this report in the hope that
  it will ring some bell with someone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 10:25:56 2018
  InstallationDate: Installed on 2017-10-24 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: openconnect
  UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago)
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1608 F pulseaudio
   /dev/snd/controlC1:  michael1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d
  InstallationDate: Installed on 2017-10-24 (149 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Latitude E7440
  Package: openconnect 7.08-3
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  wayland-session bionic wayland-session
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0WK2DM
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  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/1754601/+subscriptions

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

[Kernel-packages] [Bug 1805670] Re: 18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues ex. suspend, touchpad

[Sven Gehr]

Hi@all,

same Problem on Ubuntu 20.04

- HP ZBook Studio G5
- BIOS 01.12.00 Rev.A
- Kernel: 5.4.0-52

with best
sven

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

Title:
  18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues
  ex. suspend, touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Some background information:
  I have a new Ubuntu 18.04 installation that did not go too well.
  The Live-USB installation would hang with ACPi related errors.
  I finally installed (barring a GRUB install error) using the acpi=off kernel 
flag.
  I also tested with acpi=force and no acpi settings (only worked after the 
last kernel update).
  I report here with
  - no changes in the kernel parameters
  - no changes in BIOS except of graphics set to hybrid (Nvidia + Intel) 
otherwise I could not get it to work

  I am following the indications here:
  https://wiki.ubuntu.com/DebuggingACPI

  So here is the initial information I have (kernel version, kernel
  parameters, ACPI errors):

  ..

  uname -a
  Linux gandalf 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=82d8b6b9-1f12-4651--3639a6b76683 ro quiet splash vt.handoff=1

  dmesg | grep -i acpi | grep -i error
  [0.00] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup 
failure, AE_NOT_FOUND (20170831/dswload-210)
  [0.00] ACPI Error: 1 table load failures, 19 successful 
(20170831/tbxfload-246)
  [0.164845] ACPI Error: Field [CAP1] at bit offset/length 64/32 exceeds 
size of target Buffer (64 bits) (20170831/dsopcode-235)
  [0.164874] ACPI Error: Method parse/execution failed \_SB._OSC, 
AE_AML_BUFFER_LIMIT (20170831/psparse-550)
  [3.528032] ACPI Error: Method parse/execution failed 
\_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550)
  [3.528042] ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103)
  [3.529831] ACPI Error: Method parse/execution failed 
\_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550)
  [3.529840] ACPI Error: Method execution failed \_SB.PCI0.SPI2.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103)
  [4.610629] ACPI Error: Method parse/execution failed \_TZ.GETP, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.610635] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.611513] ACPI Error: Method parse/execution failed \_TZ.GETP, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.611518] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [8.206279] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
85bce4f4 (20170831/exresop-593)
  [8.206309] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.206315] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.210629] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
352a9487 (20170831/exresop-593)
  [8.210660] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.210666] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.214527] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
88ce12bb (20170831/exresop-593)
  [8.214555] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.214562] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.231122] ACPI Error: Attempt to CreateField of length zero 
(20170831/dsopcode-168)
  [8.231147] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPI, 
AE_AML_OPERAND_VALUE (20170831/psparse-550)
  [8.231154] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_VALUE (20170831/psparse-550)

  ..

  I have also added the following outputs:

  sudo lspci -vvnn >> report.txt

  sudo dmidecode > dmidecode.txt

  The kern.log after a suspend and resume.

  

  Some weird behavior I have noticed:

  . The Live-USB pendrive allowed me to use the touchpad when testing and 
installing Ubuntu
  . The current kernel does not allow me to use the touchpad
  . After I resume, the touchpad can be used
  . I cannot resume with the builtin At keyboard or touchpad
  . The dock (via Thunderbolt) gives me access to a mouse and keyboard that I 
use to resume
  . I hav

[Kernel-packages] [Bug 1885397] [NEW] Touchpad not detected

[Sven Lauenroth]

Public bug reported:

Touchpad (with microsoft precision drivers) can't recognize by linux. No
touchpad manufacture can't be identified

Laptop: Lenovo IdeaPad 5 15IIL05.

Occurence: Direct after installing ubuntu.

Thank you for your support.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-39-generic 5.4.0-39.43
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 27 23:29:48 2020
InstallationDate: Installed on 2020-06-27 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 81YK
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=6673529c-7bec-4811-99fa-d7f1f6492f6b ro i8042.reset quit splash 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-39-generic N/A
 linux-backports-modules-5.4.0-39-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/10/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: DPCN41WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 5 15IIL05
dmi.modalias: 
dmi:bvnLENOVO:bvrDPCN41WW:bd04/10/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05:
dmi.product.family: IdeaPad 5 15IIL05
dmi.product.name: 81YK
dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05
dmi.product.version: IdeaPad 5 15IIL05
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  New

Bug description:
  Touchpad (with microsoft precision drivers) can't recognize by linux.
  No touchpad manufacture can't be identified

  Laptop: Lenovo IdeaPad 5 15IIL05.

  Occurence: Direct after installing ubuntu.

  Thank you for your support.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-39-generic 5.4.0-39.43
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 27 23:29:48 2020
  InstallationDate: Installed on 2020-06-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=6673529c-7bec-4811-99fa-d7f1f6492f6b ro i8042.reset quit splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-39-generic N/A
   linux-backports-modules-5.4.0-39-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN41WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDPCN41WW:bd04/10/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05:
  dmi.product.family: IdeaPad 5 15IIL05
  dmi.product.name: 81YK
  dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05
  dmi.product.version: IdeaPad 5 15IIL05
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1836308] Re: Unhide Nvidia HDA audio controller

[Sven Schrecker]

keep constantly getting these messages (in syslog) when keyboard and
mouse lag (could be that the whole screen lags):

nouveau :01:00.0: Enabling HDA controller
ACPI: \_SB_.PCI0.PEG0.VID_: failed to evaluate _DSM

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

Title:
  Unhide Nvidia HDA audio controller

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Nvidia HDA audio controller comes with Nvidia graphics cannot be found
  by PCI subsystem.

  [Fix]
  Write bit 25 at graphics' config space offset 0x488 to enable the HDA
  controller.

  [Test]
  Nvidia HDA controller is not listed under lspci.
  After applying the fix lspci can find Nvidia HDA controller.

  [Regression Potential]
  Low. This fix doesn't bring any functional change other then exposing
  HDA controller at hardware level.

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

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

[Kernel-packages] [Bug 1854620] Re: Kernel crash on RasPi 3B+ (ARM64)

[Sven]

 
05c3 ffcf6dc32198
  [Sa Nov 30 06:25:03 2019] bbe0: ffcf6dc2e910 ffcf6dc2e920 
ff8723e05fd8 dead0200
  [Sa Nov 30 06:25:03 2019] bc00: dead0100 dead0200 
ffcf6dc2e8a8 dead0100
  [Sa Nov 30 06:25:03 2019] bc20: ffcf6e98be80 ff8009e0bc80 
ff87231f6b84 ff8009e0bc80
  [Sa Nov 30 06:25:03 2019] bc40: ff87231f6b38 8145 
ff8009e0bc80 ff87231f6b84
  [Sa Nov 30 06:25:03 2019] bc60: 007f ffcf6dc2e910 
ff8009e0bc80 ff87231f6b38
  [Sa Nov 30 06:25:03 2019] [] unlink_anon_vmas+0x160/0x1e8
  [Sa Nov 30 06:25:03 2019] [] free_pgtables+0x8c/0x100
  [Sa Nov 30 06:25:03 2019] [] exit_mmap+0xb8/0x160
  [Sa Nov 30 06:25:03 2019] [] mmput+0x60/0xf0
  [Sa Nov 30 06:25:03 2019] [] do_exit+0x264/0xa28
  [Sa Nov 30 06:25:03 2019] [] do_group_exit+0x3c/0xa0
  [Sa Nov 30 06:25:03 2019] [] __wake_up_parent+0x0/0x40
  [Sa Nov 30 06:25:03 2019] Exception stack(0xff8009e0bec0 to 
0xff8009e0c000)
  [Sa Nov 30 06:25:03 2019] bec0:   
 007f944c8700
  [Sa Nov 30 06:25:03 2019] bee0: 0020  
 
  [Sa Nov 30 06:25:03 2019] bf00: 005e 00558f6629e0 
0101010101010101 
  [Sa Nov 30 06:25:03 2019] bf20:   
007f9458e308 007f94580e08
  [Sa Nov 30 06:25:03 2019] bf40: 007f945b22a8 007f946fd060 
05c3 0008
  [Sa Nov 30 06:25:03 2019] bf60: 0008 007f946ccbd0 
 007f946cf000
  [Sa Nov 30 06:25:03 2019] bf80: 007f946d05a0 007f948127a0 
0008 
  [Sa Nov 30 06:25:03 2019] bfa0: 007f946d4000 007fdb8a25d0 
007f945b1f24 007fdb8a25d0
  [Sa Nov 30 06:25:03 2019] bfc0: 007f9461faec 6000 
 005e
  [Sa Nov 30 06:25:03 2019] bfe0:   
 
  [Sa Nov 30 06:25:03 2019] [] el0_svc_naked+0x34/0x38
  [Sa Nov 30 06:25:03 2019] Code: a9410a63 aa1303e1 f9000462 f94006c0 
(f943) 
  [Sa Nov 30 06:25:03 2019] ---[ end trace 8632f8ac4089d051 ]---
  [Sa Nov 30 06:25:03 2019] Fixing recursive fault but reboot is needed!

  
  Can somebody interpret this error message and give me a hint where to search 
further.
  Or is this a known (and maybe fixed) error?

  Sorry, but I cannot give the other information (as stated in the reporting 
guidlines) on
  the Ubuntu Rasperry Version, because they are not available...

  
  Regards
  Sven
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: arm64
  DistroRelease: Ubuntu 18.04
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.14.66-chainsx-cxcore+ aarch64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1854620] Re: Kernel crash on RasPi 3B+ (ARM64)

[Sven]

910 
ff8009e0bc80 ff87231f6b38
  [Sa Nov 30 06:25:03 2019] [] unlink_anon_vmas+0x160/0x1e8
  [Sa Nov 30 06:25:03 2019] [] free_pgtables+0x8c/0x100
  [Sa Nov 30 06:25:03 2019] [] exit_mmap+0xb8/0x160
  [Sa Nov 30 06:25:03 2019] [] mmput+0x60/0xf0
  [Sa Nov 30 06:25:03 2019] [] do_exit+0x264/0xa28
  [Sa Nov 30 06:25:03 2019] [] do_group_exit+0x3c/0xa0
  [Sa Nov 30 06:25:03 2019] [] __wake_up_parent+0x0/0x40
  [Sa Nov 30 06:25:03 2019] Exception stack(0xff8009e0bec0 to 
0xff8009e0c000)
  [Sa Nov 30 06:25:03 2019] bec0:   
 007f944c8700
  [Sa Nov 30 06:25:03 2019] bee0: 0020  
 
  [Sa Nov 30 06:25:03 2019] bf00: 005e 00558f6629e0 
0101010101010101 
  [Sa Nov 30 06:25:03 2019] bf20:   
007f9458e308 007f94580e08
  [Sa Nov 30 06:25:03 2019] bf40: 007f945b22a8 007f946fd060 
05c3 0008
  [Sa Nov 30 06:25:03 2019] bf60: 0008 007f946ccbd0 
 007f946cf000
  [Sa Nov 30 06:25:03 2019] bf80: 007f946d05a0 007f948127a0 
0008 
  [Sa Nov 30 06:25:03 2019] bfa0: 007f946d4000 007fdb8a25d0 
007f945b1f24 007fdb8a25d0
  [Sa Nov 30 06:25:03 2019] bfc0: 007f9461faec 6000 
 005e
  [Sa Nov 30 06:25:03 2019] bfe0:   
 
  [Sa Nov 30 06:25:03 2019] [] el0_svc_naked+0x34/0x38
  [Sa Nov 30 06:25:03 2019] Code: a9410a63 aa1303e1 f9000462 f94006c0 
(f943) 
  [Sa Nov 30 06:25:03 2019] ---[ end trace 8632f8ac4089d051 ]---
  [Sa Nov 30 06:25:03 2019] Fixing recursive fault but reboot is needed!

  
  Can somebody interpret this error message and give me a hint where to search 
further.
  Or is this a known (and maybe fixed) error?

  Sorry, but I cannot give the other information (as stated in the reporting 
guidlines) on
  the Ubuntu Rasperry Version, because they are not available...

  
  Regards
  Sven
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: arm64
  DistroRelease: Ubuntu 18.04
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.14.66-chainsx-cxcore+ aarch64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1854620] Re: Kernel crash on RasPi 3B+ (ARM64)

[Sven]

  [Sa Nov 30 06:25:03 2019] [] do_exit+0x264/0xa28
  [Sa Nov 30 06:25:03 2019] [] do_group_exit+0x3c/0xa0
  [Sa Nov 30 06:25:03 2019] [] __wake_up_parent+0x0/0x40
  [Sa Nov 30 06:25:03 2019] Exception stack(0xff8009e0bec0 to 
0xff8009e0c000)
  [Sa Nov 30 06:25:03 2019] bec0:   
 007f944c8700
  [Sa Nov 30 06:25:03 2019] bee0: 0020  
 
  [Sa Nov 30 06:25:03 2019] bf00: 005e 00558f6629e0 
0101010101010101 
  [Sa Nov 30 06:25:03 2019] bf20:   
007f9458e308 007f94580e08
  [Sa Nov 30 06:25:03 2019] bf40: 007f945b22a8 007f946fd060 
05c3 0008
  [Sa Nov 30 06:25:03 2019] bf60: 0008 007f946ccbd0 
 007f946cf000
  [Sa Nov 30 06:25:03 2019] bf80: 007f946d05a0 007f948127a0 
0008 
  [Sa Nov 30 06:25:03 2019] bfa0: 007f946d4000 007fdb8a25d0 
007f945b1f24 007fdb8a25d0
  [Sa Nov 30 06:25:03 2019] bfc0: 007f9461faec 6000 
 005e
  [Sa Nov 30 06:25:03 2019] bfe0:   
 
  [Sa Nov 30 06:25:03 2019] [] el0_svc_naked+0x34/0x38
  [Sa Nov 30 06:25:03 2019] Code: a9410a63 aa1303e1 f9000462 f94006c0 
(f943) 
  [Sa Nov 30 06:25:03 2019] ---[ end trace 8632f8ac4089d051 ]---
  [Sa Nov 30 06:25:03 2019] Fixing recursive fault but reboot is needed!
  
  
  Can somebody interpret this error message and give me a hint where to search 
further.
  Or is this a known (and maybe fixed) error?
  
  Sorry, but I cannot give the other information (as stated in the reporting 
guidlines) on
  the Ubuntu Rasperry Version, because they are not available...
  
  
  Regards
  Sven
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.9
+ Architecture: arm64
+ DistroRelease: Ubuntu 18.04
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
+ Tags:  bionic
+ Uname: Linux 4.14.66-chainsx-cxcore+ aarch64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

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

Title:
  Kernel crash on RasPi 3B+ (ARM64)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  Im running a Raspberry Pi 3B+ with Ubuntu 18.04.3 LTS (on ARM64). No swap 
space configured.
  My Kernel is: Linux ubuntu 4.14.66-chainsx-cxcore+ #2 SMP PREEMPT Sun Aug 26 
03:37:14 EDT 2018 aarch64 aarch64 aarch64 GNU/Linux

  I'm experiencing a kernel crash after some runtime.

  My first crash issued the following message:

  
  [Do Nov 28 14:46:09 2019] Linux version 4.14.66-chainsx-cxcore+ 
(r...@myhost.nopad.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18)) #2 SMP 
PREEMPT Sun Aug 26 03:37:14 EDT 2018
  [Do Nov 28 14:46:09 2019] Boot CPU: AArch64 Processor [410fd034]
  [...]
  [Fr Nov 29 20:21:20 2019] Unable to handle kernel paging request at virtual 
address 7b1fca9f2b3ece
  [Fr Nov 29 20:21:20 2019] Mem abort info:
  [Fr Nov 29 20:21:20 2019]   Exception class = DABT (current EL), IL = 32 bits

  After enabling some more debug messages, I got:

  [Sa Nov 30 06:25:03 2019] Unable to handle kernel paging request at virtual 
address ffce6dc2e920
  [Sa Nov 30 06:25:03 2019] Mem abort info:
  [Sa Nov 30 06:25:03 2019]   Exception class = DABT (current EL), IL = 32 bits
  [Sa Nov 30 06:25:03 2019]   SET = 0, FnV = 0
  [Sa Nov 30 06:25:03 2019]   EA = 0, S1PTW = 0
  [Sa Nov 30 06:25:03 2019] Data abort info:
  [Sa Nov 30 06:25:03 2019]   ISV = 0, ISS = 0x0045
  [Sa Nov 30 06:25:03 2019]   CM = 0, WnR = 1
  [Sa Nov 30 06:25:03 2019] swapper pgtable: 4k pages, 39-bit VAs, pgd = 
ff8723e2f000
  [Sa Nov 30 06:25:03 2019] [ffce6dc2e920] *pgd=, 
*pud=
  [Sa Nov 30 06:25:03 2019] Internal error: Oops: 9645 [#1] PREEMPT SMP
  [Sa Nov 30 06:25:03 2019] Modules linked in: brcmfmac brcmutil cfg80211 
rfkill snd_bcm2835(C) snd_pcm snd_timer snd sdhci_iproc w1_gpio vchiq(C) wire 
cn hwmon uio_pdrv_genirq uio sch_fq_codel ip_tables x_tables ipv6
  [Sa Nov 30 06:25:03 2019] CPU: 1 PID: 800 Comm: apache2 Tainted: G C  
4.14.66-chainsx-cxcore+ #2
  [Sa Nov 30 06:25:03 2019] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 
(DT)
  [Sa Nov 30 06:25:03 2019] task: ffcf6e98be80 task.stack: ff8009e08000
  [Sa Nov 30 06:25:03 2019] PC is at unlink_anon_vmas+0x160/0x1e8
  [Sa Nov 30 06:25:03 2019] LR is at unlink

[Kernel-packages] [Bug 1854620] [NEW] Kernel crash on RasPi 3B+ (ARM64)

[Sven]

(0xff8009e0bec0 to 
0xff8009e0c000)
[Sa Nov 30 06:25:03 2019] bec0:   
 007f944c8700
[Sa Nov 30 06:25:03 2019] bee0: 0020  
 
[Sa Nov 30 06:25:03 2019] bf00: 005e 00558f6629e0 
0101010101010101 
[Sa Nov 30 06:25:03 2019] bf20:   
007f9458e308 007f94580e08
[Sa Nov 30 06:25:03 2019] bf40: 007f945b22a8 007f946fd060 
05c3 0008
[Sa Nov 30 06:25:03 2019] bf60: 0008 007f946ccbd0 
 007f946cf000
[Sa Nov 30 06:25:03 2019] bf80: 007f946d05a0 007f948127a0 
0008 
[Sa Nov 30 06:25:03 2019] bfa0: 007f946d4000 007fdb8a25d0 
007f945b1f24 007fdb8a25d0
[Sa Nov 30 06:25:03 2019] bfc0: 007f9461faec 6000 
 005e
[Sa Nov 30 06:25:03 2019] bfe0:   
 
[Sa Nov 30 06:25:03 2019] [] el0_svc_naked+0x34/0x38
[Sa Nov 30 06:25:03 2019] Code: a9410a63 aa1303e1 f9000462 f94006c0 (f943) 
[Sa Nov 30 06:25:03 2019] ---[ end trace 8632f8ac4089d051 ]---
[Sa Nov 30 06:25:03 2019] Fixing recursive fault but reboot is needed!


Can somebody interpret this error message and give me a hint where to search 
further.
Or is this a known (and maybe fixed) error?

Sorry, but I cannot give the other information (as stated in the reporting 
guidlines) on
the Ubuntu Rasperry Version, because they are not available...


Regards
Sven

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

Title:
  Kernel crash on RasPi 3B+ (ARM64)

Status in linux package in Ubuntu:
  New

Bug description:
  
  Im running a Raspberry Pi 3B+ with Ubuntu 18.04.3 LTS (on ARM64). No swap 
space configured.
  My Kernel is: Linux ubuntu 4.14.66-chainsx-cxcore+ #2 SMP PREEMPT Sun Aug 26 
03:37:14 EDT 2018 aarch64 aarch64 aarch64 GNU/Linux

  I'm experiencing a kernel crash after some runtime.

  My first crash issued the following message:

  
  [Do Nov 28 14:46:09 2019] Linux version 4.14.66-chainsx-cxcore+ 
(r...@myhost.nopad.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18)) #2 SMP 
PREEMPT Sun Aug 26 03:37:14 EDT 2018
  [Do Nov 28 14:46:09 2019] Boot CPU: AArch64 Processor [410fd034]
  [...]
  [Fr Nov 29 20:21:20 2019] Unable to handle kernel paging request at virtual 
address 7b1fca9f2b3ece
  [Fr Nov 29 20:21:20 2019] Mem abort info:
  [Fr Nov 29 20:21:20 2019]   Exception class = DABT (current EL), IL = 32 bits

  After enabling some more debug messages, I got:

  [Sa Nov 30 06:25:03 2019] Unable to handle kernel paging request at virtual 
address ffce6dc2e920
  [Sa Nov 30 06:25:03 2019] Mem abort info:
  [Sa Nov 30 06:25:03 2019]   Exception class = DABT (current EL), IL = 32 bits
  [Sa Nov 30 06:25:03 2019]   SET = 0, FnV = 0
  [Sa Nov 30 06:25:03 2019]   EA = 0, S1PTW = 0
  [Sa Nov 30 06:25:03 2019] Data abort info:
  [Sa Nov 30 06:25:03 2019]   ISV = 0, ISS = 0x0045
  [Sa Nov 30 06:25:03 2019]   CM = 0, WnR = 1
  [Sa Nov 30 06:25:03 2019] swapper pgtable: 4k pages, 39-bit VAs, pgd = 
ff8723e2f000
  [Sa Nov 30 06:25:03 2019] [ffce6dc2e920] *pgd=, 
*pud=
  [Sa Nov 30 06:25:03 2019] Internal error: Oops: 9645 [#1] PREEMPT SMP
  [Sa Nov 30 06:25:03 2019] Modules linked in: brcmfmac brcmutil cfg80211 
rfkill snd_bcm2835(C) snd_pcm snd_timer snd sdhci_iproc w1_gpio vchiq(C) wire 
cn hwmon uio_pdrv_genirq uio sch_fq_codel ip_tables x_tables ipv6
  [Sa Nov 30 06:25:03 2019] CPU: 1 PID: 800 Comm: apache2 Tainted: G C  
4.14.66-chainsx-cxcore+ #2
  [Sa Nov 30 06:25:03 2019] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 
(DT)
  [Sa Nov 30 06:25:03 2019] task: ffcf6e98be80 task.stack: ff8009e08000
  [Sa Nov 30 06:25:03 2019] PC is at unlink_anon_vmas+0x160/0x1e8
  [Sa Nov 30 06:25:03 2019] LR is at unlink_anon_vmas+0x1ac/0x1e8
  [Sa Nov 30 06:25:03 2019] pc : [] lr : [] 
pstate: 8145
  [Sa Nov 30 06:25:03 2019] sp : ff8009e0bc80
  [Sa Nov 30 06:25:03 2019] x29: ff8009e0bc80 x28: ffcf6e98be80 
  [Sa Nov 30 06:25:03 2019] x27: dead0100 x26: ffcf6dc2e8a8 
  [Sa Nov 30 06:25:03 2019] x25: dead0200 x24: dead0100 
  [Sa Nov 30 06:25:03 2019] x23: dead0200 x22: ff8723e05fd8 
  [Sa Nov 30 06:25:03 2019] x21: ffcf6dc2e920 x20: ffcf6dc2e910 
  [Sa Nov 30 06:25:03 2019] x19: ffcf6dc32198 x18: 05c3 
  [Sa Nov 30 06:25:03 2019] x17: 007f946fd060 x16:  
  [Sa Nov 30 06:25:03 2019] x15:  x14: fff0c000 
  [Sa Nov 30 06:25:03 2019] x13: 07f91c00 x12: dead0100 
  [Sa Nov 30 06:25:03 2019] x11

[Kernel-packages] [Bug 1815064] Re: udev 237 incorrectly reporting serials for scsi devices

[Sven Wiltink]

Due to the nature of the machine and the firewalls in place I will not
be able to run the apport-collect command. The information I have
provided should be enough to discuss the issue

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

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

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

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

Title:
  udev 237 incorrectly reporting serials for scsi devices

Status in udev package in Ubuntu:
  Confirmed

Bug description:
  system info:
  Kernel: Ubuntu 4.15.0-29.31-generic 4.15.18
  Package: udev 237-3ubuntu10.3
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  We've been running into the issue where lblk -O outputs the wwn
  instead of the serial for scsi devices. After some debugging I've come
  to the conclusing that /lib/udev/scsi_id is the underlying cause. It
  outputs the wwn of a disk in the ID_SERIAL_SHORT field, but does also
  export the actual serial in a separate field (ID_SCSI_SERIAL).

  sample output during udevadm test:
  IMPORT 'scsi_id --export --whitelisted -d /dev/sdas' 
/lib/udev/rules.d/60-persistent-storage.rules:50
  starting 'scsi_id --export --whitelisted -d /dev/sdas'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_SCSI=1'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_VENDOR=HGST'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_VENDOR_ENC=HGST\x20\x20\x20\x20'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_MODEL=HUS726060ALS640'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_MODEL_ENC=HUS726060ALS640\x20'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_REVISION=A280'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_TYPE=disk'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_SERIAL=35000cca232ab84ac'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_SERIAL_SHORT=5000cca232ab84ac'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_WWN=0x5000cca232ab84ac'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_WWN_WITH_EXTENSION=0x5000cca232ab84ac'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_SCSI_SERIAL=
1EK1A65J'

  ata devices to not have this issue because they use ata_id:
  IMPORT 'ata_id --export /dev/sdad' 
/lib/udev/rules.d/60-persistent-storage.rules:38
  starting 'ata_id --export /dev/sdad'
  'ata_id --export /dev/sdad'(out) 'ID_ATA=1'
  'ata_id --export /dev/sdad'(out) 'ID_TYPE=disk'
  'ata_id --export /dev/sdad'(out) 'ID_BUS=ata'
  'ata_id --export /dev/sdad'(out) 'ID_MODEL=HGST_HDN726060ALE614'
  'ata_id --export /dev/sdad'(out) 
'ID_MODEL_ENC=HGST\x20HDN726060ALE614\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20'
  'ata_id --export /dev/sdad'(out) 'ID_REVISION=APGNW7JH'
  'ata_id --export /dev/sdad'(out) 'ID_SERIAL=HGST_HDN726060ALE614_NAHTWX0X'
  'ata_id --export /dev/sdad'(out) 'ID_SERIAL_SHORT=NAHTWX0X'
  
  'ata_id --export /dev/sdad'(out) 'ID_WWN=0x5000cca242d96928'
  'ata_id --export /dev/sdad'(out) 'ID_WWN_WITH_EXTENSION=0x5000cca242d96928'


  I am unsure if the fix should be in udev or lsblk, but I wanted to
  bring it up for discussion because the serial not being displayed
  properly.

  Kind regards,
  Sven Wiltink

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

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

[Kernel-packages] [Bug 1815064] [NEW] udev 237 incorrectly reporting serials for scsi devices

[Sven Wiltink]

Public bug reported:

system info:
Kernel: Ubuntu 4.15.0-29.31-generic 4.15.18
Package: udev 237-3ubuntu10.3
Description:Ubuntu 18.04.1 LTS
Release:18.04

We've been running into the issue where lblk -O outputs the wwn instead
of the serial for scsi devices. After some debugging I've come to the
conclusing that /lib/udev/scsi_id is the underlying cause. It outputs
the wwn of a disk in the ID_SERIAL_SHORT field, but does also export the
actual serial in a separate field (ID_SCSI_SERIAL).

sample output during udevadm test:
IMPORT 'scsi_id --export --whitelisted -d /dev/sdas' 
/lib/udev/rules.d/60-persistent-storage.rules:50
starting 'scsi_id --export --whitelisted -d /dev/sdas'
'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_SCSI=1'
'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_VENDOR=HGST'
'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_VENDOR_ENC=HGST\x20\x20\x20\x20'
'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_MODEL=HUS726060ALS640'
'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_MODEL_ENC=HUS726060ALS640\x20'
'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_REVISION=A280'
'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_TYPE=disk'
'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_SERIAL=35000cca232ab84ac'
'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_SERIAL_SHORT=5000cca232ab84ac'
'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_WWN=0x5000cca232ab84ac'
'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_WWN_WITH_EXTENSION=0x5000cca232ab84ac'
'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_SCSI_SERIAL=
1EK1A65J'

ata devices to not have this issue because they use ata_id:
IMPORT 'ata_id --export /dev/sdad' 
/lib/udev/rules.d/60-persistent-storage.rules:38
starting 'ata_id --export /dev/sdad'
'ata_id --export /dev/sdad'(out) 'ID_ATA=1'
'ata_id --export /dev/sdad'(out) 'ID_TYPE=disk'
'ata_id --export /dev/sdad'(out) 'ID_BUS=ata'
'ata_id --export /dev/sdad'(out) 'ID_MODEL=HGST_HDN726060ALE614'
'ata_id --export /dev/sdad'(out) 
'ID_MODEL_ENC=HGST\x20HDN726060ALE614\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20'
'ata_id --export /dev/sdad'(out) 'ID_REVISION=APGNW7JH'
'ata_id --export /dev/sdad'(out) 'ID_SERIAL=HGST_HDN726060ALE614_NAHTWX0X'
'ata_id --export /dev/sdad'(out) 'ID_SERIAL_SHORT=NAHTWX0X'

'ata_id --export /dev/sdad'(out) 'ID_WWN=0x5000cca242d96928'
'ata_id --export /dev/sdad'(out) 'ID_WWN_WITH_EXTENSION=0x5000cca242d96928'


I am unsure if the fix should be in udev or lsblk, but I wanted to bring
it up for discussion because the serial not being displayed properly.

Kind regards,
Sven Wiltink

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


** Tags: 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/1815064

Title:
  udev 237 incorrectly reporting serials for scsi devices

Status in udev package in Ubuntu:
  Confirmed

Bug description:
  system info:
  Kernel: Ubuntu 4.15.0-29.31-generic 4.15.18
  Package: udev 237-3ubuntu10.3
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  We've been running into the issue where lblk -O outputs the wwn
  instead of the serial for scsi devices. After some debugging I've come
  to the conclusing that /lib/udev/scsi_id is the underlying cause. It
  outputs the wwn of a disk in the ID_SERIAL_SHORT field, but does also
  export the actual serial in a separate field (ID_SCSI_SERIAL).

  sample output during udevadm test:
  IMPORT 'scsi_id --export --whitelisted -d /dev/sdas' 
/lib/udev/rules.d/60-persistent-storage.rules:50
  starting 'scsi_id --export --whitelisted -d /dev/sdas'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_SCSI=1'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_VENDOR=HGST'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_VENDOR_ENC=HGST\x20\x20\x20\x20'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_MODEL=HUS726060ALS640'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_MODEL_ENC=HUS726060ALS640\x20'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_REVISION=A280'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_TYPE=disk'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_SERIAL=35000cca232ab84ac'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_SERIAL_SHORT=5000cca232ab84ac'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_WWN=0x5000cca232ab84ac'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 
'ID_WWN_WITH_EXTENSION=0x5000cca232ab84ac'
  'scsi_id --export --whitelisted -d /dev/sdas'(out) 'ID_SCSI_SERIAL=
1EK1A65J'

  ata devices to not have this issue because they use ata_id:
  IMPORT 'ata_id --export /dev/sdad' 
/lib/udev/rules.d/60-persistent-storage.rules:38
  starting 'ata_id --export /dev/sdad'
  'ata_id --export /dev/sdad'(out) 'ID_ATA=1

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Sven Meyer]

I am running Lubuntu 18.04 with the kernel from @kaihengfeng

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Sven Meyer]

I have a Yepo 737A and just installed the modified kernel

Kai-Heng Feng (kaihengfeng) wrote on 2018-05-24:#162
Of course. Here's the Kernel:
https://people.canonical.com/~khfeng/lp1728244-testing/

Touchpad is working great! Mouse movement works, corners for left and
right click worked.

I attached (after boot) an external USB-mouse: that one is working great
as well, no problems, no problems with mouse pad while external mouse is
attached, no lag or what so ever.

Great work, thanks a lot. That makes the finally a great cheap Linux
computer.

btw: If you remove the bottom cover and remove the thread for the M.2 SATA SSD, 
then it even fits the larger (chewing gum sized) SSDs 2280. I insulated the 
metal and fixed the SSD with some tape.
If you really want to do it properly then you add some thermal 1 mm laver on 
top so that it touches SSD and metal cover.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

[Sven Killig]

Sorry, I meant
> And I'm not sure if I got the right
nvm_usb_0302.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/1766825

Title:
  Bluetooth issues with Dell XPS 13 (9370)

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have the following problem with my Bluetooth module on my new Dell
  XPS 13 (9370) with Ubuntu preinstalled.

  The bluetooth module gets disabled for some reason. The bluetooth
  devices (keyboard and mouse) just stop working in the middle of the
  work, the Bluetooth indicator goes away and the module is also gone in
  the rfkill list.

  To get it back working I need to reboot the machine, start the BIOS,
  disable the Bluetooth module and re-enable it or I have to turn the
  machine completely off and on again. After that, the bluetooth module
  is available again. That's pretty annoying.

  My syslog when this happens:

  Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB 
disconnect, device number 3
  Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 
22
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch 
Status.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root.
  Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 
21
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSource
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSink
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 
12120 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 
12133 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross 

[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

[Sven Killig]

Would be nice if someone from Qualcomm could have a look at it; just now
an update of the linux-firmware Ubuntu package overwrote my fix again.

And I'm not sure if I got the right ramps_0x0302_48.dfu
The Windows driver has these:
sonic@sonic-XPS-13-9370:/opt/Bluetooth_driver$ md5sum ramps*302*
067fb95e8501bad2683df07d23539e7d  ramps_0x0302_48.dfu
1028210a03cb116e8c482eb9cd263d39  ramps_0x0302_48_NFA354A_10db.dfu
4b8012ca0a04e8061da510d3a5186852  ramps_TF_0x0302_48.dfu
4b8012ca0a04e8061da510d3a5186852  ramps_TF_0x0302_48_NFA435_10dbm.dfu
No idea what all these pre- and suffixes mean...

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

Title:
  Bluetooth issues with Dell XPS 13 (9370)

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have the following problem with my Bluetooth module on my new Dell
  XPS 13 (9370) with Ubuntu preinstalled.

  The bluetooth module gets disabled for some reason. The bluetooth
  devices (keyboard and mouse) just stop working in the middle of the
  work, the Bluetooth indicator goes away and the module is also gone in
  the rfkill list.

  To get it back working I need to reboot the machine, start the BIOS,
  disable the Bluetooth module and re-enable it or I have to turn the
  machine completely off and on again. After that, the bluetooth module
  is available again. That's pretty annoying.

  My syslog when this happens:

  Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB 
disconnect, device number 3
  Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 
22
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch 
Status.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root.
  Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 
21
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSource
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSink
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 
12120 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: 

[Kernel-packages] [Bug 1741934] Re: Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI fix)

[Sven Ehret]

when will this be in the main repositories?

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

Title:
  Kernel trace with xenial 4.4  (4.4.0-108.131, Candidate kernels for
  PTI fix)

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel trace shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22340 (Dell Vostro 5468)
  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel trace message.

  [Actual Result]

  Kernel trace message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: [   37.701961] Stack:
  Jan  9 00:33:33 201606-22365 kernel: [   

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Sven Jacobsen]

Step 8 of the updated description on top of the page has solved this
issue on a Lenovo Yoga 300 (Ubuntu 17.10) and a Ideapad 100-14IBY
(Ubuntu 16.04LTS). Thanks to everybody. Hats off, true piece of master
work. I am sorry, if I have written something too emotional.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Sven Jacobsen]

Steps of #308 did not work for Lenovo Yoga 300-11IBY and Lenovo ideapad
100-14IBY. No BIOS changes possible, no installation media is detected.
Another bug in my case?

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Sven Jacobsen]

#294 did not work for me. Nothing has changed, my BIOS is done, thanks
to "Whoever-ruined-my-hardware". Is there really no solution around? Do
I have to run a corrupted system? How long will it work? Happy users of
other tried and trusted distros have started to make jokes. That
hurts...

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Sven Jacobsen]

Lenovo Yoga 300-11IBY affected after Ubuntu 17.10 installation. Horrible 
situation, no more installation possible. Now the system works, but if an 
update will break something, the whole machine will be unusable. 
Interesting enough: another machine, Lenovo ideapad 100-14IBY, running on Bodhi 
Linux 4, based on Ubuntu 16.04 LTS, is also affected.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1672782] Re: Graphics trouble after hibernation or Sleep

[Sven Neuhaus]

Is there any hope of a fix in a supported 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/1672782

Title:
  Graphics trouble after hibernation or Sleep

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

Bug description:
  Edges around windows get pixelated

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  abhilash   2353 F pulseaudio
   /dev/snd/controlC0:  abhilash   2353 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar 14 11:52:03 2017
  HibernationDevice: RESUME=UUID=e086eed9-3076-4bc3-b94b-8674e530b351
  InstallationDate: Installed on 2016-12-28 (75 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20378
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=2e21e919-a77e-41b5-889c-9339d654e040 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN30WW(V1.13)
  dmi.board.asset.tag: 31900058Std
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: 31900058Std
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN30WW(V1.13):bd07/16/2014:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Sven Hartrumpf]

Hi.

The relevant line in the kern.log of the affected server
(4.10.0-21-generic) was:

kernel BUG at /build/linux-
lz1RHE/linux-4.10.0/include/linux/swapops.h:129!

I switched to the 4.11 mainline kernel:
Linux 4.11.2-041102-generic #201705201036 SMP Sat May 20 14:38:21 UTC 2017 
x86_64 x86_64 x86_64

I hope this is a valid work-around ...

Sven

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in linux-hwe-edge source package in Zesty:
  Fix Committed

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Sven]

+1, experiencing this since I've upgraded from 16.10 to 17.04, every few
hours the system freezes. Really annoying ...

kernel: [ 4075.895491] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
kernel: [ 4075.895523] invalid opcode:  [#2] 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/1674838

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1619277] Re: Can't build kernel-package

[Sven]

Can't do apport-collect, because of headless server.

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

Title:
  Can't build kernel-package

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I tried to build a kernel package 4.4.0-36.55 on Ubuntu 16.04 64bit. I
  used the Ubuntu sources:

  #make-kpkg --append-to-version=-test-01 --initrd kernel_image

  I got this output and error:

  Kernel: arch/x86/boot/bzImage is ready  (#4)
  make[1]: Leaving directory '/usr/src/linux-source-4.4.0/linux-source-4.4.0'
  /usr/bin/make -j6 EXTRAVERSION=-test-01  ARCH=x86_64 \
   modules
  make[1]: Entering directory '/usr/src/linux-source-4.4.0/linux-source-4.4.0'
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CHK include/generated/timeconst.h
CHK include/generated/bounds.h
CHK include/generated/asm-offsets.h
CALLscripts/checksyscalls.sh
GZIPkernel/config_data.gz
CHK kernel/config_data.h
Building modules, stage 2.
MODPOST 289 modules
  ERROR: "drm_release" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_pool_populate" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_tt_fini" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_crtc_helper_set_config" [ubuntu/vbox/vboxvideo/vboxvideo.ko] 
undefined!
  ERROR: "drm_compat_ioctl" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_helper_resume_force_mode" [ubuntu/vbox/vboxvideo/vboxvideo.ko] 
undefined!
  ERROR: "ttm_bo_move_memcpy" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_mode_config_cleanup" [ubuntu/vbox/vboxvideo/vboxvideo.ko] 
undefined!
  ERROR: "drm_mode_config_reset" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_pci_exit" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_mode_destroy" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_bo_validate" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_bo_init" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_cvt_mode" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_helper_probe_single_connector_modes" 
[ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_global_item_ref" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_kms_helper_hotplug_event" [ubuntu/vbox/vboxvideo/vboxvideo.ko] 
undefined!
  ERROR: "drm_encoder_init" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_object_property_set_value" [ubuntu/vbox/vboxvideo/vboxvideo.ko] 
undefined!
  ERROR: "drm_pci_set_busid" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_connector_cleanup" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_mem_global_init" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_helper_connector_dpms" [ubuntu/vbox/vboxvideo/vboxvideo.ko] 
undefined!
  ERROR: "ttm_mem_global_release" [ubuntu/vbox/vboxvideo/vboxvideo.ko] 
undefined!
  ERROR: "drm_mode_connector_attach_encoder" 
[ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_irq_install" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_bo_unref" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_bo_add_to_lru" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_helper_mode_fill_fb_struct" [ubuntu/vbox/vboxvideo/vboxvideo.ko] 
undefined!
  ERROR: "drm_object_attach_property" [ubuntu/vbox/vboxvideo/vboxvideo.ko] 
undefined!
  ERROR: "drm_put_dev" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_gem_handle_create" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_gem_dumb_destroy" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_bo_kmap" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_tt_init" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_gem_object_release" [ubuntu/vbox/vboxvideo/vboxvideo.ko] 
undefined!
  ERROR: "drm_read" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_bo_dma_acc_size" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_bo_init_mm" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_bo_device_init" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_err" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_connector_init" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_kms_helper_poll_enable" [ubuntu/vbox/vboxvideo/vboxvideo.ko] 
undefined!
  ERROR: "drm_mode_connector_update_edid_property" 
[ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_gem_object_free" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_ioctl" [ubuntu/vbox/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_framebuffer_unregister_private" 

[Kernel-packages] [Bug 1580482] Re: Virtualbox guest additions isn't working properly in Ubuntu 16.04

[Sven]

I think, this bug is related to #1619277.

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

Title:
  Virtualbox guest additions isn't working properly in Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Incomplete

Bug description:
  ## Symptoms ##
  * OpenGL processing offloading is not supported(3D hardware acceleration is 
enabled in VM settings and is available on Intel Graphics host)
  * VBoxClient warns about "Failed to connect to the ViratualBox kernel 
service, rc=VERR_ACCESS_DENIED"(refer attached screenshot)

  You may checkout the screen record for what exactly this issue is about:
  https://www.youtube.com/watch?v=aB1sb3D4Q9g

  ## Workarounds ##
  Install VirtualBox provided guest additions iso from the menu works

  ## Additional Information ##
  * I uses the VirtualBox from upstream on the host side, the version is 5.0.20
  * Note that the Ubuntu Kernel bundled with 16.04 has integrated VirtualBox 
guest modules(vboxguest, vboxsf, and vboxvideo specifically) for unknown 
reason, this bug is reproduced *without* the virtualbox-guest-dkms 
package(since the Additional Drivers interface doesn't provide me the option to 
do so(the option is greyed-out, refer attached screenshot))
  * I have another 14.04 VM and it's OpenGL offloading works, so it's not 
likely that the host isn't providing proper OpenGL functionallity

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox-guest-x11 5.0.18-dfsg-2build1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 11 12:08:31 2016
  InstallationDate: Installed on 2016-01-07 (124 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: virtualbox
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (33 days ago)

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

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

[Kernel-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

[sven-ola]

Upgrading to (self-compiled) 5.41-0ubuntu5 does not help either: still got 
syslog with:
pulseaudio[4465]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for 
transport /org/bluez/hci0/dev_00_18_09_21_36_F0/fd1 (Operation Not Authorized)

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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

[Kernel-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

[sven-ola]

My stereo headphones shows this bug. I've tried to add
https://git.kernel.org/cgit/bluetooth/bluez.git/commit/src/service.c?id=2e2edc36a91d6a8f2c65d793273df28a166d6bed
using dpkg-buildpackage with no success.

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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

[Kernel-packages] [Bug 1605267] Re: Building kernel pachakges failed

[Sven]

Additional info with DEBUG_SECTION_MISMATCH:

WARNING: vmlinux.o(.text.unlikely+0x3201): Section mismatch in reference from 
the function new_kmalloc_cache() to the variable .init.rodata:kmalloc_info
The function new_kmalloc_cache() references
the variable __initconst kmalloc_info.
This is often because new_kmalloc_cache lacks a __initconst
annotation or the annotation of kmalloc_info is wrong.

WARNING: vmlinux.o(.text.unlikely+0x3208): Section mismatch in reference from 
the function new_kmalloc_cache() to the variable .init.rodata:kmalloc_info
The function new_kmalloc_cache() references
the variable __initconst kmalloc_info.
This is often because new_kmalloc_cache lacks a __initconst
annotation or the annotation of kmalloc_info is wrong.

WARNING: vmlinux.o(.text.unlikely+0x320d): Section mismatch in reference from 
the function new_kmalloc_cache() to the function 
.init.text:create_kmalloc_cache()
The function new_kmalloc_cache() references
the function __init create_kmalloc_cache().
This is often because new_kmalloc_cache lacks a __init
annotation or the annotation of create_kmalloc_cache is wrong.

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

Title:
  Building kernel pachakges failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello!

  This command failed: make-kpkg --append-to-version=-test-12 --initrd 
kernel_image
  I tried to build a kernel packages with kernel 3.13.0-92.139 on Ubuntu 
14.04.4 LTS:

  WARNING: modpost: Found 3 section mismatch(es).
  To see full details build your kernel with:
  'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC  init/version.o
LD  init/built-in.o
KSYM.tmp_kallsyms1.o
KSYM.tmp_kallsyms2.o
LD  vmlinux
SORTEX  vmlinux
SYSMAP  System.map
VOFFSET arch/x86/boot/voffset.h
CC  arch/x86/boot/version.o
OBJCOPY arch/x86/boot/compressed/vmlinux.bin
GZIParch/x86/boot/compressed/vmlinux.bin.gz
MKPIGGY arch/x86/boot/compressed/piggy.S
AS  arch/x86/boot/compressed/piggy.o
LD  arch/x86/boot/compressed/vmlinux
  arch/x86/boot/compressed/head_64.o: In function `efi64_config':
  (.data+0x90): undefined reference to `efi_call6'
  make[3]: *** [arch/x86/boot/compressed/vmlinux] Error 1
  make[2]: *** [arch/x86/boot/compressed/vmlinux] Error 2
  make[1]: *** [bzImage] Error 2
  make[1]: Leaving directory `/usr/src/linux-source-3.13.0/linux-source-3.13.0'
  make: *** [debian/stamp/build/kernel] Error 2

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

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

[Kernel-packages] [Bug 1605267] Re: Building kernel pachakges failed

[Sven]

There is no log

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

Title:
  Building kernel pachakges failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello!

  This command failed: make-kpkg --append-to-version=-test-12 --initrd 
kernel_image
  I tried to build a kernel packages with kernel 3.13.0-92.139 on Ubuntu 
14.04.4 LTS:

  WARNING: modpost: Found 3 section mismatch(es).
  To see full details build your kernel with:
  'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC  init/version.o
LD  init/built-in.o
KSYM.tmp_kallsyms1.o
KSYM.tmp_kallsyms2.o
LD  vmlinux
SORTEX  vmlinux
SYSMAP  System.map
VOFFSET arch/x86/boot/voffset.h
CC  arch/x86/boot/version.o
OBJCOPY arch/x86/boot/compressed/vmlinux.bin
GZIParch/x86/boot/compressed/vmlinux.bin.gz
MKPIGGY arch/x86/boot/compressed/piggy.S
AS  arch/x86/boot/compressed/piggy.o
LD  arch/x86/boot/compressed/vmlinux
  arch/x86/boot/compressed/head_64.o: In function `efi64_config':
  (.data+0x90): undefined reference to `efi_call6'
  make[3]: *** [arch/x86/boot/compressed/vmlinux] Error 1
  make[2]: *** [arch/x86/boot/compressed/vmlinux] Error 2
  make[1]: *** [bzImage] Error 2
  make[1]: Leaving directory `/usr/src/linux-source-3.13.0/linux-source-3.13.0'
  make: *** [debian/stamp/build/kernel] Error 2

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

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

[Kernel-packages] [Bug 1605267] [NEW] Building kernel pachakges failed

[Sven]

Public bug reported:

Hello!

This command failed: make-kpkg --append-to-version=-test-12 --initrd 
kernel_image
I tried to build a kernel packages with kernel 3.13.0-92.139 on Ubuntu 14.04.4 
LTS:

WARNING: modpost: Found 3 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
  GEN .version
  CHK include/generated/compile.h
  UPD include/generated/compile.h
  CC  init/version.o
  LD  init/built-in.o
  KSYM.tmp_kallsyms1.o
  KSYM.tmp_kallsyms2.o
  LD  vmlinux
  SORTEX  vmlinux
  SYSMAP  System.map
  VOFFSET arch/x86/boot/voffset.h
  CC  arch/x86/boot/version.o
  OBJCOPY arch/x86/boot/compressed/vmlinux.bin
  GZIParch/x86/boot/compressed/vmlinux.bin.gz
  MKPIGGY arch/x86/boot/compressed/piggy.S
  AS  arch/x86/boot/compressed/piggy.o
  LD  arch/x86/boot/compressed/vmlinux
arch/x86/boot/compressed/head_64.o: In function `efi64_config':
(.data+0x90): undefined reference to `efi_call6'
make[3]: *** [arch/x86/boot/compressed/vmlinux] Error 1
make[2]: *** [arch/x86/boot/compressed/vmlinux] Error 2
make[1]: *** [bzImage] Error 2
make[1]: Leaving directory `/usr/src/linux-source-3.13.0/linux-source-3.13.0'
make: *** [debian/stamp/build/kernel] Error 2

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

** Attachment added: "kernel config"
   https://bugs.launchpad.net/bugs/1605267/+attachment/4704678/+files/config

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

Title:
  Building kernel pachakges failed

Status in linux package in Ubuntu:
  New

Bug description:
  Hello!

  This command failed: make-kpkg --append-to-version=-test-12 --initrd 
kernel_image
  I tried to build a kernel packages with kernel 3.13.0-92.139 on Ubuntu 
14.04.4 LTS:

  WARNING: modpost: Found 3 section mismatch(es).
  To see full details build your kernel with:
  'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC  init/version.o
LD  init/built-in.o
KSYM.tmp_kallsyms1.o
KSYM.tmp_kallsyms2.o
LD  vmlinux
SORTEX  vmlinux
SYSMAP  System.map
VOFFSET arch/x86/boot/voffset.h
CC  arch/x86/boot/version.o
OBJCOPY arch/x86/boot/compressed/vmlinux.bin
GZIParch/x86/boot/compressed/vmlinux.bin.gz
MKPIGGY arch/x86/boot/compressed/piggy.S
AS  arch/x86/boot/compressed/piggy.o
LD  arch/x86/boot/compressed/vmlinux
  arch/x86/boot/compressed/head_64.o: In function `efi64_config':
  (.data+0x90): undefined reference to `efi_call6'
  make[3]: *** [arch/x86/boot/compressed/vmlinux] Error 1
  make[2]: *** [arch/x86/boot/compressed/vmlinux] Error 2
  make[1]: *** [bzImage] Error 2
  make[1]: Leaving directory `/usr/src/linux-source-3.13.0/linux-source-3.13.0'
  make: *** [debian/stamp/build/kernel] Error 2

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

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

[Kernel-packages] [Bug 994931] Re: Altering use_tempaddr drops all IPv6 addresses

[Sven Mueller]

Ping.
The test kernel seems to fix this. Could it be pushed to Trusty?

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

Title:
  Altering use_tempaddr drops all IPv6 addresses

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Utopic:
  Invalid

Bug description:
  $ uname -a
  Linux expvr-alnilam 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59 
UTC 2012 i686 i686 i386 GNU/Linux

  $ sysctl net.ipv6.conf.eth2.use_tempaddr
  net.ipv6.conf.eth2.use_tempaddr = 2
  # (as per the default /etc/sysctl.d/10-ipv6-privacy.conf in 12.04)

  # Add a static IPv6 address:
  $ sudo ip addr add 2001:470:9321:f003::1122/64 dev eth2

  # Verify that it has been set up, and that a temporary address and a SLAAC 
address also exist:
  $ ip -6 addr list dev eth2
  4: eth2:  mtu 1500 qlen 1000
  inet6 2001:470:9321:f003:74e3:aa2b:7ee5:c002/64 scope global temporary 
dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003:6c97:24ff:fe3f:263b/64 scope global dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003::1122/64 scope global 
 valid_lft forever preferred_lft forever
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link 
 valid_lft forever preferred_lft forever

  # Disable RFC 4941 temporary addresses:
  $ sudo sysctl net.ipv6.conf.eth2.use_tempaddr=0
  net.ipv6.conf.eth2.use_tempaddr = 0

  $ ip -6 addr list dev eth2
  4: eth2:  mtu 1500 qlen 1000
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link tentative 
 valid_lft forever preferred_lft forever

  I.e. on setting use_tempaddr=0, _all_ IPv6 addresses are removed,
  including statically-configured and non-temporary SLAAC-configured
  addresses.  (The link-local address reappears quickly but the
  'tentative' flag indicates that it has been newly re-added.  The SLAAC
  address reappears after a slightly longer interval as the kernel
  continues to undergo SLAAC, but the static address is gone forever
  unless manually reinstated.)

  The same happens if use_tempaddr is changed from 0 back to 2.

  The expected outcome is that only temporary addresses are affected by a 
change to use_tempaddr.
  --- 
  AcpiTables:
   
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 May  5 03:53 seq
   crw-rw---T 1 root audio 116, 33 May  5 03:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  DistroRelease: Ubuntu 12.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen.linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=b16ffd9c-a54a-4dd3-a839-16c382ea8787 ro  
console=hvc0
  ProcModules:
   lp 17455 0 - Live 0x
   parport 40930 1 lp, Live 0x
   xenfs 17877 1 - Live 0x
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic-pae N/A
   linux-backports-modules-3.2.0-24-generic-pae  N/A
   linux-firmware1.79
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.2.0-24-generic-pae i686
  UpgradeStatus: Upgraded to precise on 2012-05-05 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Kernel-packages] [Bug 1535904] Re: No Resume from Suspend function on eeePC 1101ha 1201ha

[Sven Behrend]

The Bug exists also in 4.4.0-040400-generic. 
Tested and downloaded today.

No functional way to wake the eeePC up after standby.

** Tags added: kernel-bug-exists-upstream

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

Title:
  No Resume from Suspend function on eeePC 1101ha 1201ha

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From Kernel 3.13.x on the eeePC can't wake up from  suspend.

  After the laptop suspends it can't be reactivated using any of the
  keys, the lid or the power switch.

  I tested today with the 4.2.0-25-generic , 3.13.0-24-generic  and 
3.13.0-32-generic. 
  All of the above are not functional with resuming from suspend the laptop.

  As tests from earlier last year show, the 3.12 kernel is capable of
  suspending and resuming.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bse1744 F pulseaudio
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
  CurrentDesktop: LXDE
  Date: Tue Jan 19 21:57:31 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=15b8d64c-9230-495e-be86-2ecc848f4886
  InstallationDate: Installed on 2015-12-17 (33 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 001 Device 002: ID 13d3:5108 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer INC. 1101HA
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=bc853181-e847-4a67-ba13-90fe83b59697 ro acpi_osi=Linux 
acpi_backlight=vendor mem=1920mb quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.19
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0322
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1101HA
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0322:bd11/05/2009:svnASUSTeKComputerINC.:pn1101HA:pvrx.x:rvnASUSTeKComputerINC.:rn1101HA:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1101HA
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Kernel-packages] [Bug 994931] Re: Altering use_tempaddr drops all IPv6 addresses

[Sven Mueller]

Any chance this could be fixed in Trusty?

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

Title:
  Altering use_tempaddr drops all IPv6 addresses

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Utopic:
  Invalid

Bug description:
  $ uname -a
  Linux expvr-alnilam 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59 
UTC 2012 i686 i686 i386 GNU/Linux

  $ sysctl net.ipv6.conf.eth2.use_tempaddr
  net.ipv6.conf.eth2.use_tempaddr = 2
  # (as per the default /etc/sysctl.d/10-ipv6-privacy.conf in 12.04)

  # Add a static IPv6 address:
  $ sudo ip addr add 2001:470:9321:f003::1122/64 dev eth2

  # Verify that it has been set up, and that a temporary address and a SLAAC 
address also exist:
  $ ip -6 addr list dev eth2
  4: eth2:  mtu 1500 qlen 1000
  inet6 2001:470:9321:f003:74e3:aa2b:7ee5:c002/64 scope global temporary 
dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003:6c97:24ff:fe3f:263b/64 scope global dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003::1122/64 scope global 
 valid_lft forever preferred_lft forever
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link 
 valid_lft forever preferred_lft forever

  # Disable RFC 4941 temporary addresses:
  $ sudo sysctl net.ipv6.conf.eth2.use_tempaddr=0
  net.ipv6.conf.eth2.use_tempaddr = 0

  $ ip -6 addr list dev eth2
  4: eth2:  mtu 1500 qlen 1000
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link tentative 
 valid_lft forever preferred_lft forever

  I.e. on setting use_tempaddr=0, _all_ IPv6 addresses are removed,
  including statically-configured and non-temporary SLAAC-configured
  addresses.  (The link-local address reappears quickly but the
  'tentative' flag indicates that it has been newly re-added.  The SLAAC
  address reappears after a slightly longer interval as the kernel
  continues to undergo SLAAC, but the static address is gone forever
  unless manually reinstated.)

  The same happens if use_tempaddr is changed from 0 back to 2.

  The expected outcome is that only temporary addresses are affected by a 
change to use_tempaddr.
  --- 
  AcpiTables:
   
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 May  5 03:53 seq
   crw-rw---T 1 root audio 116, 33 May  5 03:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  DistroRelease: Ubuntu 12.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen.linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=b16ffd9c-a54a-4dd3-a839-16c382ea8787 ro  
console=hvc0
  ProcModules:
   lp 17455 0 - Live 0x
   parport 40930 1 lp, Live 0x
   xenfs 17877 1 - Live 0x
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic-pae N/A
   linux-backports-modules-3.2.0-24-generic-pae  N/A
   linux-firmware1.79
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.2.0-24-generic-pae i686
  UpgradeStatus: Upgraded to precise on 2012-05-05 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Kernel-packages] [Bug 1535904] [NEW] No Resume from Suspend function on eeePC 1101ha 1201ha

[Sven Behrend]

Public bug reported:

>From Kernel 3.13.x on the eeePC can't wake up from  suspend.

After the laptop suspends it can't be reactivated using any of the keys,
the lid or the power switch.

I tested today with the 4.2.0-25-generic , 3.13.0-24-generic  and 
3.13.0-32-generic. 
All of the above are not functional with resuming from suspend the laptop.

As tests from earlier last year show, the 3.12 kernel is capable of
suspending and resuming.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bse1744 F pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
CurrentDesktop: LXDE
Date: Tue Jan 19 21:57:31 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=15b8d64c-9230-495e-be86-2ecc848f4886
InstallationDate: Installed on 2015-12-17 (33 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
Lsusb:
 Bus 001 Device 002: ID 13d3:5108 IMC Networks 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTeK Computer INC. 1101HA
ProcFB: 0 psbdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=bc853181-e847-4a67-ba13-90fe83b59697 ro acpi_osi=Linux 
acpi_backlight=vendor mem=1920mb quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic  N/A
 linux-firmware 1.127.19
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0322
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1101HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0322:bd11/05/2009:svnASUSTeKComputerINC.:pn1101HA:pvrx.x:rvnASUSTeKComputerINC.:rn1101HA:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1101HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

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


** Tags: apport-bug i386 trusty

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

Title:
  No Resume from Suspend function on eeePC 1101ha 1201ha

Status in linux package in Ubuntu:
  New

Bug description:
  From Kernel 3.13.x on the eeePC can't wake up from  suspend.

  After the laptop suspends it can't be reactivated using any of the
  keys, the lid or the power switch.

  I tested today with the 4.2.0-25-generic , 3.13.0-24-generic  and 
3.13.0-32-generic. 
  All of the above are not functional with resuming from suspend the laptop.

  As tests from earlier last year show, the 3.12 kernel is capable of
  suspending and resuming.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bse1744 F pulseaudio
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
  CurrentDesktop: LXDE
  Date: Tue Jan 19 21:57:31 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=15b8d64c-9230-495e-be86-2ecc848f4886
  InstallationDate: Installed on 2015-12-17 (33 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 001 Device 002: ID 13d3:5108 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer INC. 1101HA
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=bc853181-e847-4a67-ba13-90fe83b59697 ro acpi_osi=Linux 
acpi_backlight=vendor mem=1920mb quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.19
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Kernel-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode

[Sven]

Also experienced on Aquaris E5 OTA-6

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

Title:
  Bluetooth initiated after quitting airplane mode

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in urfkill package in Ubuntu:
  Confirmed

Bug description:
  This happens despite bluetooth not being enabled when entering
  airplane mode.

  On Aquaris E5 OTA-5.

  Boot with bluetooth disabled
  Turn on flight mode
  turn off flight mode
  Bluetooth gets enabled

  See bug #1421249 for related symptoms

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+subscriptions

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

[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)

[Sven]

I don't know who at Samsung wrote that response. They have a bug in
their SSD firmware. Full stop. The issue with Linux probably is, that it
supports a feature that Windows doesn't and thus is the only OS affected
by the broken firmware.

Martin Petersen from the linux-ide mailing list wrote, when he was
sending the patch blacklisting all 800 series SSDs, that they would work
with Samsung to resolve the issue - whatever that means.

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

Title:
  trim does not work with Samsung 840 EVO after firmware update
  (EXT0DB6Q)

Status in fstrim package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in fstrim source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Confirmed
Status in fstrim source package in Utopic:
  Invalid
Status in linux source package in Utopic:
  Confirmed
Status in fstrim source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Confirmed

Bug description:
  Hi,
  after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the 
fstream command doesn't work anymore. Besides, there are a lot of file system 
errors and bad sectors reports. The problem is certainly caused by Samsung's 
firmware but I reported it as a bug because in Windows TRIM works normally 
after the upgrade. I have attached an image uploaded by a user who is 
experiencing the same problem. If you execute the command sudo fstrim / the  
console gets stuck. If you add that command in rc.local the boot is 
compromised. I really hope this problem could be solved.
  Thanks

  ===
  break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a
  break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81

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

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

[Kernel-packages] [Bug 1414930] Re: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work

[Sven Mueller]

Actually, Markus tested Trusty, not Utopic:
3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 
14.04.1 is the Trusty version, not Utopic. Therefor adding 
verification-needed-utopic back and adding verification-done-trusty.


** Tags removed: verification-done-utopic verification-needed-trusty
** Tags added: verification-done-trusty verification-needed-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/1414930

Title:
  [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't
  work

Status in HWE Next Project:
  In Progress
Status in The Linux Kernel:
  Fix Released
Status in libinput package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in linux source package in Utopic:
  Fix Committed
Status in systemd source package in Utopic:
  Confirmed

Bug description:
  Lenovo X1 3rd Carbon (201411-16196)

  Steps to reproduce the bug:
  1, Log in to system
  2, Click left/right/middle buttons of the touchpad

  Actual result:
  No response after clicking the buttons

  Expected results:
  Buttons work as expected behavirour

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: 
boot/vmlinuz-3.13.0-45-generic]
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1598 F pulseaudio
   /dev/snd/controlC0:  u  1598 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 27 02:48:23 2015
  HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f
  InstallationDate: Installed on 2015-01-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126)
  MachineType: LENOVO 20BTZ09ZUS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-45-generic N/A
   linux-backports-modules-3.13.0-45-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET24W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTZ09ZUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTZ09ZUS
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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