[Kernel-packages] [Bug 1949262] Re: Power Savings doesn't turn monitor off in Wayland on NUC8i5INH

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1929650
   Screen doesn't turn off when using Wayland on some 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/1949262

Title:
  Power Savings doesn't turn monitor off in Wayland on NUC8i5INH

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  On previous versions of Ubuntu, after 5 minutes, my monitor would turn
  off as per settings. Since I reinstalled fresh 21.10, this is not
  happening. Screen becomes black and stays powered on.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 30 08:11:02 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / 
E9171 MCM] [1002:6987] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Lexa [Radeon 540X/550X/630 / RX 640 / E9171 
MCM] [8086:2079]
  InstallationDate: Installed on 2021-10-14 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Intel(R) Client Systems NUC8i5INH
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=1e81e0c8-99b9-447b-b8a2-2ebe4bf0eb88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: INWHL357.0043.2021.0817.1957
  dmi.board.name: NUC8i5INB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K29935-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrINWHL357.0043.2021.0817.1957:bd08/17/2021:br5.13:svnIntel(R)ClientSystems:pnNUC8i5INH:pvrK47340-403:skuBXNUC8i5INHPA:rvnIntelCorporation:rnNUC8i5INB:rvrK29935-402:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: IN
  dmi.product.name: NUC8i5INH
  dmi.product.sku: BXNUC8i5INHPA
  dmi.product.version: K47340-403
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Kernel-packages] [Bug 1941030] Re: [Fujitsu Lifebook U7411] Screen Flickers

[Daniel van Vugt]

Comment #3 confirmed the screen flicker was the automatic PSR setting in
i915. The comments after that should really have gone in a new bug.

** Changed in: linux-hwe-5.11 (Ubuntu)
   Status: Expired => Triaged

** Changed in: linux-hwe-5.11 (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- [Fujitsu Lifebook U7411] Screen Flickers
+ [Fujitsu Lifebook U7411] Screen Flickers when PSR is enabled

** Tags added: psr

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

Title:
  [Fujitsu Lifebook U7411] Screen Flickers when PSR is enabled

Status in linux-hwe-5.11 package in Ubuntu:
  Triaged

Bug description:
  After the laptop goes to sleep mode, it starts to flicker when i try
  to use the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 25 10:10:33 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Client Computing Limited Device [1e26:0050]
  InstallationDate: Installed on 2021-08-18 (6 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7411
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=2ef2e3af-1c99-45d0-8bdf-5c9bd7e07ab9 ro quiet splash pcie_aspm=off 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2021
  dmi.bios.release: 2.21
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 2.21
  dmi.board.name: FJNB2E7
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: A3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.21:bd06/28/2021:br2.21:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7411:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:
  dmi.product.family: LIFEBOOK-FPCA
  dmi.product.name: LIFEBOOK U7411
  dmi.product.sku: SK01
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1929892] Re: [TGL] enable USB-dw3

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [TGL] enable USB-dw3

Status in intel:
  Invalid
Status in linux package in Ubuntu:
  Expired
Status in linux-intel package in Ubuntu:
  Invalid

Bug description:
  Description
  Enable USB-dw3 for Tiger Lake

  Hardware: Tiger Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

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


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

[Kernel-packages] [Bug 1941030] Re: [Fujitsu Lifebook U7411] Screen Flickers

[Launchpad Bug Tracker]

[Expired for linux-hwe-5.11 (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: linux-hwe-5.11 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [Fujitsu Lifebook U7411] Screen Flickers

Status in linux-hwe-5.11 package in Ubuntu:
  Expired

Bug description:
  After the laptop goes to sleep mode, it starts to flicker when i try
  to use the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 25 10:10:33 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Client Computing Limited Device [1e26:0050]
  InstallationDate: Installed on 2021-08-18 (6 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7411
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=2ef2e3af-1c99-45d0-8bdf-5c9bd7e07ab9 ro quiet splash pcie_aspm=off 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2021
  dmi.bios.release: 2.21
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 2.21
  dmi.board.name: FJNB2E7
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: A3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.21:bd06/28/2021:br2.21:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7411:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:
  dmi.product.family: LIFEBOOK-FPCA
  dmi.product.name: LIFEBOOK U7411
  dmi.product.sku: SK01
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1949321] Re: Fix System hangs on black screen when reboot

[koba]

** Tags added: oem-priority originate-from-1946057 somerville

** Tags added: originate-from-1942069

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

Title:
  Fix System hangs on black screen when reboot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  New
Status in linux-oem-5.14 source package in Hirsute:
  New
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  New
Status in linux-oem-5.14 source package in Impish:
  New
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.10 source package in Jammy:
  New
Status in linux-oem-5.14 source package in Jammy:
  New

Bug description:
  [Impact]
  System hangs on black screen when reboot

  [Fix]
  Looks like our VBIOS/GOP generally fail to turn the DP dual mode adater
  TMDS output buffers back on after a reboot. This leads to a black screen
  after reboot if we turned the TMDS output buffers off prior to reboot.
  And if i915 decides to do a fastboot the black screen will persist even
  after i915 takes over.
  
  Apparently this has been a problem ever since commit b2ccb822d376 
("drm/i915:Enable/disable TMDS output buffers in DP++ adaptor as needed") if 
one rebooted while the display was turned off. And things became worse with 
commit fe0f1e3bfdfe ("drm/i915: Shut down displays gracefully on reboot") since 
now we always turn the display off before a reboot.
  
  This was reported on a RKL, but I confirmed the same behaviour on my
  SNB as well. So looks pretty universal.
  
  Let's fix this by explicitly turning the TMDS output buffers back on
  in the encoder->shutdown() hook. Note that this gets called after irqs
  have been disabled, so the i2c communication with the DP dual mode
  adapter has to be performed via polling (which the gmbus code is
  perfectly happy to do for us).
  
  We also need a bit of care in handling DDI encoders which may or may
  not be set up for HDMI output. Specifically ddc_pin will not be
  populated for a DP only DDI encoder, in which case we don't want to
  call intel_gmbus_get_adapter(). We can handle that by simply doing
  the dual mode adapter type check before calling
  intel_gmbus_get_adapter().
  Ref: https://patchwork.freedesktop.org/series/96433/

  [Test]
  1. install kernel
  2. reboot
  3. check the monitor works well.

  [Regression Potential]
  Medium, patch has sent to patchwork but may have a upgraded version in the 
furtue.

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


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

[Kernel-packages] [Bug 1949321] Re: Fix System hangs on black screen when reboot

[koba]

** Description changed:

  [Impact]
- 
+ System hangs on black screen when reboot
  
  [Fix]
- 
+ Looks like our VBIOS/GOP generally fail to turn the DP dual mode adater
+ TMDS output buffers back on after a reboot. This leads to a black screen
+ after reboot if we turned the TMDS output buffers off prior to reboot.
+ And if i915 decides to do a fastboot the black screen will persist even
+ after i915 takes over.
+ 
+ Apparently this has been a problem ever since commit b2ccb822d376 
("drm/i915:Enable/disable TMDS output buffers in DP++ adaptor as needed") if 
one rebooted while the display was turned off. And things became worse with 
commit fe0f1e3bfdfe ("drm/i915: Shut down displays gracefully on reboot") since 
now we always turn the display off before a reboot.
+ 
+ This was reported on a RKL, but I confirmed the same behaviour on my
+ SNB as well. So looks pretty universal.
+ 
+ Let's fix this by explicitly turning the TMDS output buffers back on
+ in the encoder->shutdown() hook. Note that this gets called after irqs
+ have been disabled, so the i2c communication with the DP dual mode
+ adapter has to be performed via polling (which the gmbus code is
+ perfectly happy to do for us).
+ 
+ We also need a bit of care in handling DDI encoders which may or may
+ not be set up for HDMI output. Specifically ddc_pin will not be
+ populated for a DP only DDI encoder, in which case we don't want to
+ call intel_gmbus_get_adapter(). We can handle that by simply doing
+ the dual mode adapter type check before calling
+ intel_gmbus_get_adapter().
+ Ref: https://patchwork.freedesktop.org/series/96433/
  
  [Test]
- 
+ 1. install kernel
+ 2. reboot
+ 3. check the monitor works well.
  
  [Regression Potential]
+ Medium, patch has sent to patchwork but may have a upgraded version in the 
furtue.

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

Title:
  Fix System hangs on black screen when reboot

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  New
Status in linux-oem-5.14 source package in Hirsute:
  New
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  New
Status in linux-oem-5.14 source package in Impish:
  New
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.10 source package in Jammy:
  New
Status in linux-oem-5.14 source package in Jammy:
  New

Bug description:
  [Impact]
  System hangs on black screen when reboot

  [Fix]
  Looks like our VBIOS/GOP generally fail to turn the DP dual mode adater
  TMDS output buffers back on after a reboot. This leads to a black screen
  after reboot if we turned the TMDS output buffers off prior to reboot.
  And if i915 decides to do a fastboot the black screen will persist even
  after i915 takes over.
  
  Apparently this has been a problem ever since commit b2ccb822d376 
("drm/i915:Enable/disable TMDS output buffers in DP++ adaptor as needed") if 
one rebooted while the display was turned off. And things became worse with 
commit fe0f1e3bfdfe ("drm/i915: Shut down displays gracefully on reboot") since 
now we always turn the display off before a reboot.
  
  This was reported on a RKL, but I confirmed the same behaviour on my
  SNB as well. So looks pretty universal.
  
  Let's fix this by explicitly turning the TMDS output buffers back on
  in the encoder->shutdown() hook. Note that this gets called after irqs
  have been disabled, so the i2c communication with the DP dual mode
  adapter has to be performed via polling (which the gmbus code is
  perfectly happy to do for us).
  
  We also need a bit of care in handling DDI encoders which may or may
  not be set up for HDMI output. Specifically ddc_pin will not be
  populated for a DP only DDI encoder, in which case we don't want to
  call intel_gmbus_get_adapter(). We can handle that by simply doing
  the dual mode adapter type check before calling
  intel_gmbus_get_adapter().
  Ref: https://patchwork.freedesktop.org/series/96433/

  [Test]
  1. install kernel
  2. reboot
  3. check the monitor works well.

  [Regression Potential]
  Medium, patch has sent to patchwork but may have a upgraded version in the 
furtue.

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


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

[Kernel-packages] [Bug 1949321] [NEW] Fix System hangs on black screen when reboot

[koba]

Public bug reported:

[Impact]
System hangs on black screen when reboot

[Fix]
Looks like our VBIOS/GOP generally fail to turn the DP dual mode adater
TMDS output buffers back on after a reboot. This leads to a black screen
after reboot if we turned the TMDS output buffers off prior to reboot.
And if i915 decides to do a fastboot the black screen will persist even
after i915 takes over.

Apparently this has been a problem ever since commit b2ccb822d376 
("drm/i915:Enable/disable TMDS output buffers in DP++ adaptor as needed") if 
one rebooted while the display was turned off. And things became worse with 
commit fe0f1e3bfdfe ("drm/i915: Shut down displays gracefully on reboot") since 
now we always turn the display off before a reboot.

This was reported on a RKL, but I confirmed the same behaviour on my
SNB as well. So looks pretty universal.

Let's fix this by explicitly turning the TMDS output buffers back on
in the encoder->shutdown() hook. Note that this gets called after irqs
have been disabled, so the i2c communication with the DP dual mode
adapter has to be performed via polling (which the gmbus code is
perfectly happy to do for us).

We also need a bit of care in handling DDI encoders which may or may
not be set up for HDMI output. Specifically ddc_pin will not be
populated for a DP only DDI encoder, in which case we don't want to
call intel_gmbus_get_adapter(). We can handle that by simply doing
the dual mode adapter type check before calling
intel_gmbus_get_adapter().
Ref: https://patchwork.freedesktop.org/series/96433/

[Test]
1. install kernel
2. reboot
3. check the monitor works well.

[Regression Potential]
Medium, patch has sent to patchwork but may have a upgraded version in the 
furtue.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

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

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

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

** Affects: linux-oem-5.10 (Ubuntu Focal)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-5.14 (Ubuntu Focal)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-5.10 (Ubuntu Hirsute)
 Importance: Undecided
 Status: New

** Affects: linux-oem-5.14 (Ubuntu Hirsute)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Impish)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-5.10 (Ubuntu Impish)
 Importance: Undecided
 Status: New

** Affects: linux-oem-5.14 (Ubuntu Impish)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-5.10 (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: linux-oem-5.14 (Ubuntu Jammy)
 Importance: Undecided
 Status: New

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

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

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

** Also affects: linux-oem-5.10 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.14 (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-5.10 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.14 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-5.10 (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.14 (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-5.10 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.14 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => koba (kobako)

** Changed in: linux (Ubuntu Impish)
   Status: New => In Progress

** Changed in: linux (Ubuntu Impish)
 Assignee: (unassigned) => koba (kobako)

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => koba (kobako)

[Kernel-packages] [Bug 1931072] Re: USB Type-C hotplug event not handled properly in TGL-H system during s2idle

[Chris Chiu]

** Tags removed: verification-needed-impish
** Tags added: verification-done-impish

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

Title:
  USB Type-C hotplug event not handled properly in TGL-H system during
  s2idle

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  The system will be hold by the infinite loop in ACPI method IPCS after 
exiting s2idle in TGL-H systems if the docking station with external display 
connected is unplugged when the system is still in s2idle. It's
  because the system is unaware of the unplug event and it seems keep something 
asserted which will never be released while the system trying to exit s2idle.

  [Fix]
  Disconnect TypeC PHYs during system suspend and shutdown, even with the
  corresponding TypeC sink still plugged to its connector. The HPD event is no 
longer triggered when the system is in s2idle so the resume process will not be 
hindered.

  [Test Case]
  1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the 
NVIDIA GPU is running in either On-Demand mode or Performance mode.
  2. Connect the docking station with the external display connected.
  3. Suspend the system.
  4. Remove the docking station when the system is suspended.
  5. Press power button to wake up the system and wait > 1 minutes to make sure 
if the display comes back.

  [Where problems could occur]
  Low. This will only make a difference in the TypeC DP alternate mode, and the 
display driver will detect the display connector after resume.

  == Original Bug Description ==

  [Summary]
  As mentioned in #1929166, the NVIDIA GPU will fall off the bus after exiting 
s2idle in TGL-H systems if the USB Type-C docking/dongle with external display 
connected is unplugged when the system is still in s2idle. The system will be 
hold by the infinite loop in ACPI method IPCS and then the PCIe root port of 
NVIDIA gpu fails the power transition from D3cold to D0. It's because the 
display connector hotplug event not handled properly in graphics drivers and 
the system will freeze for > 30 seconds to wait for ACPI method IPCS to exit.

  [ 154.446781]
  [ 154.446783]
  [ 154.446783] Initialized Local Variables for Method [IPCS]:
  [ 154.446784] Local0: 9863e365  Integer 09C5
  [ 154.446790]
  [ 154.446791] Initialized Arguments for Method [IPCS]: (7 arguments
  defined for method invocation)
  [ 154.446792] Arg0: 25568fbd  Integer 00AC
  [ 154.446795] Arg1: 9ef30e76  Integer 
  [ 154.446798] Arg2: fdf820f0  Integer 0010
  [ 154.446801] Arg3: 9fc2a088  Integer 0001
  [ 154.446804] Arg4: 3a3418f7  Integer 0001
  [ 154.446807] Arg5: 20c4b87c  Integer 
  [ 154.446810] Arg6: 8b965a8a  Integer 
  [ 154.446813]
  [ 154.446815] ACPI Error: Aborting method \IPCS due to previous error
  (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446824] ACPI Error: Aborting method \MCUI due to previous error
  (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446829] ACPI Error: Aborting method \SPCX due to previous error
  (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446835] ACPI Error: Aborting method \_SB.PC00.PGSC due to
  previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446841] ACPI Error: Aborting method \_SB.PC00.PGON due to
  previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446846] ACPI Error: Aborting method \_SB.PC00.PEG1.NPON due to
  previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446852] ACPI Error: Aborting method \_SB.PC00.PEG1.PG01._ON due
  to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446860] acpi device:02: Failed to change power state to D0
  [ 154.690760] video LNXVIDEO:00: Cannot transition to power state D0
  for parent in (unknown)

  [Reproduce Steps]
  1. Connect either Dell WD19SC/DC/TB docking station(USB Type-C) to the system.
  2. Connect to external display to HDMI/DisplayPort of the docking
  3. Suspend the system
  4. Unplug the USB Type-C connector 

[Kernel-packages] [Bug 1949262] Re: Power Savings doesn't turn monitor off in Wayland on NUC8i5INH

[Daniel van Vugt]

Does it work if you log into 'Ubuntu on Xorg'?

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

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

** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #1991
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1991

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

Title:
  Power Savings doesn't turn monitor off in Wayland on NUC8i5INH

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  On previous versions of Ubuntu, after 5 minutes, my monitor would turn
  off as per settings. Since I reinstalled fresh 21.10, this is not
  happening. Screen becomes black and stays powered on.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 30 08:11:02 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / 
E9171 MCM] [1002:6987] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Lexa [Radeon 540X/550X/630 / RX 640 / E9171 
MCM] [8086:2079]
  InstallationDate: Installed on 2021-10-14 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Intel(R) Client Systems NUC8i5INH
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=1e81e0c8-99b9-447b-b8a2-2ebe4bf0eb88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: INWHL357.0043.2021.0817.1957
  dmi.board.name: NUC8i5INB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K29935-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrINWHL357.0043.2021.0817.1957:bd08/17/2021:br5.13:svnIntel(R)ClientSystems:pnNUC8i5INH:pvrK47340-403:skuBXNUC8i5INHPA:rvnIntelCorporation:rnNUC8i5INB:rvrK29935-402:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: IN
  dmi.product.name: NUC8i5INH
  dmi.product.sku: BXNUC8i5INHPA
  dmi.product.version: K47340-403
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Kernel-packages] [Bug 1949262] Re: Power Savings doesn't turn monitor off

[Daniel van Vugt]

This sounds like bug 1929650, which has been generalised in
https://gitlab.gnome.org/GNOME/mutter/-/issues/1991

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

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

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1991
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1991

** Summary changed:

- Power Savings doesn't turn monitor off
+ Power Savings doesn't turn monitor off in Wayland on NUC8i5INH

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

Title:
  Power Savings doesn't turn monitor off in Wayland on NUC8i5INH

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  On previous versions of Ubuntu, after 5 minutes, my monitor would turn
  off as per settings. Since I reinstalled fresh 21.10, this is not
  happening. Screen becomes black and stays powered on.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 30 08:11:02 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / 
E9171 MCM] [1002:6987] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Lexa [Radeon 540X/550X/630 / RX 640 / E9171 
MCM] [8086:2079]
  InstallationDate: Installed on 2021-10-14 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Intel(R) Client Systems NUC8i5INH
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=1e81e0c8-99b9-447b-b8a2-2ebe4bf0eb88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: INWHL357.0043.2021.0817.1957
  dmi.board.name: NUC8i5INB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K29935-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrINWHL357.0043.2021.0817.1957:bd08/17/2021:br5.13:svnIntel(R)ClientSystems:pnNUC8i5INH:pvrK47340-403:skuBXNUC8i5INHPA:rvnIntelCorporation:rnNUC8i5INB:rvrK29935-402:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: IN
  dmi.product.name: NUC8i5INH
  dmi.product.sku: BXNUC8i5INHPA
  dmi.product.version: K47340-403
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Kernel-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)

[Daniel van Vugt]

** Changed in: linux (Ubuntu)
   Status: Won't Fix => Confirmed

** Tags removed: groovy
** Tags added: hirsute

** No longer affects: pulseaudio (Ubuntu)

** Summary changed:

- [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 
20.10 (not even wired, cable headset)
+ [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 
21.04 (not even wired, cable headset)

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

Title:
  [Acer Spin 5 - SP513-54N] External headset microphone not working on
  Ubuntu 21.04 (not even wired, cable headset)

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

Bug description:
  Recently, external microphone has stopped working while using classic
  wired audio combo jack headset.

  Basics:

  1) Headset's microphone works fine both in MS Windows on the same machine and 
on older Xubuntu on another machine.
  2) Internal laptop mic works normally.
  3) Yes, I have mic unmuted in settings.

  I've followed whole step1 from this troubleshoot guide:
  https://help.ubuntu.com/community/SoundTroubleshootingProcedure

  Did not help.

  There are more information with screenshots here:
  https://askubuntu.com/questions/1305942/external-headset-microphone-
  not-working-on-ubuntu-20-10-not-even-wired-cable-h:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crysman2301 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 13:31:13 2021
  InstallationDate: Installed on 2020-06-19 (210 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago)
  dmi.bios.date: 07/17/2020
  dmi.bios.release: 1.5
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.05
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot

[Anthony Wong]

** Changed in: linux-intel-5.13 (Ubuntu)
   Status: New => Fix Released

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

Title:
  [iotg][tgl][tgl-aaeon] 20211006 image does not boot

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  Fix Released
Status in linux-intel-5.13 source package in Focal:
  Fix Released

Bug description:
  The daily build containing the new kernel does not boot.  It gets
  stuck about 2 seconds into the cycle with the message "Run /init as
  init process" (see attached image file for boot message sequence.)

  System: TGL-Aaeon (CID: 202110-29509)

  Steps to reproduce:
  Downloaded focal-preinstalled-desktop-amd64+intel-iot.img.xz from 
https://cdimage.ubuntu.com/focal/daily-preinstalled/20211006/

  Uncompressed file with unxz -k

  Copied the .img file to my secondary USB drive.

  Boot 20.04 LTS from primary USB drive.

  Select Try Ubuntu

  Wipe out /dev/sda (primary storage)

  Use dd to copy the image from secondary USB drive to /dev/sda

  Reboot, removing USB drives when prompted.

  Expected Result:
  System should boot Ubuntu Desktop with kernel 5.13-1006

  Actual Result:
  System hangs 2 seconds into the boot cycle with
  "Run /init as init process"

  Reproducibility: 100%

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


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

[Kernel-packages] [Bug 1949314] [NEW] intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

[FurretUber]

Public bug reported:

When resizing the terminal window, intel_gpu_top may crash if the window
become small enough. The output when it crashes is:

intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion 
`max_len > 0' failed.
Abortado

I was able to reproduce this crash with tilix and xterm.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: intel-gpu-tools 1.26-2
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu72
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Sun Oct 31 21:06:01 2021
InstallationDate: Installed on 2017-06-13 (1601 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: intel-gpu-tools
UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago)
modified.conffile..etc.cron.daily.apport: [deleted]

** Affects: intel-gpu-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

Status in intel-gpu-tools package in Ubuntu:
  New

Bug description:
  When resizing the terminal window, intel_gpu_top may crash if the
  window become small enough. The output when it crashes is:

  intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion 
`max_len > 0' failed.
  Abortado

  I was able to reproduce this crash with tilix and xterm.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: intel-gpu-tools 1.26-2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sun Oct 31 21:06:01 2021
  InstallationDate: Installed on 2017-06-13 (1601 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: intel-gpu-tools
  UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago)
  modified.conffile..etc.cron.daily.apport: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


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

[Kernel-packages] [Bug 1938983] Re: missing modules after 5.11.0-25-generic update

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  missing modules after 5.11.0-25-generic update

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

Bug description:
  After updating to kernel 5.11.0-25-generic wireless driver failed to 
recognize WiFi card.
  Possible reasons/symptoms:
  $ sudo update-initramfs -u -k all
  update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
  W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for 
module i915
  update-initramfs: Generating /boot/initrd.img-5.8.0-63-generic

  $ lsb_release -a
  LSB Version:  core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  July2021
  Release:  20.04
  Codename: focal

  Workaround: connected Ethernet. (Inconvenient)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1938983/+subscriptions


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

[Kernel-packages] [Bug 1946808] Re: zfs fails reverting to a previous snapshot on reboot when selected on grub

[Mathew Hodson]

** Tags added: verification-needed-impish

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

Title:
  zfs fails reverting to a previous snapshot on reboot when selected on
  grub

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * zfs fails reverting to a previous snapshot on reboot when selected
  on grub

   * A miss-merge dropped initramfs hook changes, which result in
  failing to generate and use a new zfs uid.

   * Thus revert code to how it was before in
  https://launchpad.net/ubuntu/+source/zfs-linux/2.0.2-1ubuntu3

  [Test Plan]

   * Create snapshot with $ zsysctl save test-sru --system

   * Reboot and attempt to boot into test-sru snapshot

  [Where problems could occur]

   * The change is to initramfs hook only, thus initrd generation and
  boot paths are affected. Only latest initrd is rebuilt, rather than
  old ones, meaning booting initrds of older kernel abis will not be
  resolved.

  [Other Info]

   * Original bug report

  After creating a snapshot with: zsysctl save 211012-linux13-19 -s
  the reboot fails as shown on the screenshot, the other screenshot shows the 
result of the snapshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: zsys 0.5.8
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Tue Oct 12 19:11:43 2021
  InstallationDate: Installed on 2021-10-12 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Mounts: Error: [Errno 40] Too many levels of symbolic links: '/proc/mounts'
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zgtuq6@/vmlinuz-5.13.0-19-generic 
root=ZFS=rpool/ROOT/ubuntu_zgtuq6 ro quiet splash
  RelatedPackageVersions:
   zfs-initramfs  2.0.6-1ubuntu2
   zfsutils-linux 2.0.6-1ubuntu2
  SourcePackage: zsys
  SystemdFailedUnits:

  UpgradeStatus: No upgrade log present (probably fresh install)
  ZFSImportedPools:
   NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH 
 ALTROOT
   bpool   768M  79.2M   689M- - 0%10%  1.00xONLINE 
 -
   rpool14G  3.33G  10.7G- - 1%23%  1.00xONLINE 
 -
  ZFSListcache-bpool:
   bpool/boot   off on  on  off on  off on  
off -   none-   -   -   -   -   -   -   
-
   bpool/BOOT   noneoff on  on  off on  off on  
off -   none-   -   -   -   -   -   -   
-
   bpool/BOOT/ubuntu_zgtuq6 /boot   on  on  on  off on  
off on  off -   none-   -   -   -   -   
-   -   -
  ZSYSJournal:
   -- Journal begins at Tue 2021-10-12 18:10:37 AST, ends at Tue 2021-10-12 
19:11:52 AST. --
   -- No entries --
  modified.conffile..etc.apt.apt.conf.d.90_zsys_system_autosnapshot: [deleted]

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


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

[Kernel-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915

[jtlpa]

Can also confirm this bug, I'm on Ubuntu Mate 20.04.3.

Manually replaced missing /lib/firmware/i915 files with binaries from

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/tree/i915

Then ran update-initramfs -u w/o any errors.

Installing the the missing i915 files also made my sound card produce
music like it should.

The bottom line is if you are missing firmware files, don't expect you
computer work the way the manufacture expected.

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

Title:
  Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it
  loads i915

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  I can see that the linux-firmware is missing firmware files, in Ubuntu
  20.04.1 LTS, for initramfs, when it loads i915.

  Package: linux-firmware 1.187.15
  It contains the following files, for the module i915:
  i915/tgl_dmc_ver2_04.bin  2019-09-13  installed
  i915/tgl_dmc_ver2_06.bin  2020-03-04  installed
  i915/tgl_dmc_ver2_08.bin  2020-08-13  installed
  i915/tgl_guc_35.2.0.bin   2019-11-06  installed
  i915/tgl_huc_7.0.12.bin   2020-03-04  installed
  i915/tgl_huc_7.0.3.bin2019-11-06  installed

  Package: linux-firmware
  MUST at least contain the following files, for the module i915:
  i915/tgl_huc_7.5.0.bin2020-08-13  i915: Add HuC 
firwmare v7.5.0 for TGL
  as the module asks for it, during 'update-initramfs', to avoid:
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  But it COULD also contain : 
  i915/tgl_dmc_ver2_12.bin  2021-07-28  i915: Add v2.12 DMC for TGL
  i915/tgl_guc_49.0.1.bin   2020-11-24  i915: Add GuC firmware 
v49.0.1 for all platforms
  i915/tgl_guc_62.0.0.bin   2021-06-29  firmware/i915/guc: Add 
GuC v62.0.0 for all platforms
  i915/tgl_huc_7.9.3.bin2021-06-29  firmware/i915/guc: Add 
HuC v7.9.3 for TGL & DG1

  Source: 
  $ modprobe --show-depends --ignore-install i915
  ...
  insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko 

  $ modinfo -F firmware 
/lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko
  ...
  i915/tgl_dmc_ver2_08.bin
  i915/tgl_guc_35.2.0.bin
  i915/tgl_huc_7.5.0.bin

  Actual result:
  $ sudo update-initramfs -u
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  
  Expected result:
  No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915

  
  Info : INTEL Repository of firmware:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.15
  ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46
  Uname: Linux 5.10.0-1038-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  1699 F pulseaudio
   /dev/snd/pcmC0D0p:   chris  1699 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Aug 15 14:46:47 2021
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54
  InstallationDate: Installed on 2021-08-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem 
root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1038-oem N/A
   linux-backports-modules-5.10.0-1038-oem  N/A
   linux-firmware   1.187.15
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2021
  dmi.bios.release: 3.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.0.4
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.0.4:bd07/16/2021:br3.0:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1939986/+subscriptions


-- 
Mailing list: 

[Kernel-packages] [Bug 1938886] Re: rrr:no dh_strip or strip loose setuid bit

[Mathew Hodson]

** No longer affects: virtualbox (Ubuntu)

** No longer affects: linux (Ubuntu)

** No longer affects: debugedit (Ubuntu)

** No longer affects: dash (Ubuntu)

** No longer affects: bash (Ubuntu)

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

Title:
  rrr:no dh_strip or strip loose setuid bit

Status in binutils package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  Fix Released

Bug description:
  Over at https://launchpadlibrarian.net/550715513/buildlog_ubuntu-
  hirsute-amd64.virtualbox_6.1.22-dfsg-2~ubuntu1.21.04.2_BUILDING.txt.gz

  I have rebuilt an earlier version of virtualbox, that sets Rules-
  Requires-Root: no and added extra ls statements to find where/when/why
  setuid bits are getting lost after fixperms.

  make[1]: Leaving directory '/<>'
 debian/rules override_dh_strip
  make[1]: Entering directory '/<>'
  ls -latr debian/virtualbox/usr/lib/virtualbox/VBoxSDL
  -rwsr-sr-x 1 buildd buildd 406808 Jul 29 14:34 
debian/virtualbox/usr/lib/virtualbox/VBoxSDL
  ...
  dh_strip --dbgsym-migration='virtualbox-dbg'
  debugedit: debian/virtualbox/usr/lib/virtualbox/VBoxSDL.so: Unknown DWARF 
DW_FORM_0x1f20
  a7cf3c43c8b18c3261d2d4737a475bf730ad1554

  ls -latr debian/virtualbox/usr/lib/virtualbox/VBoxSDL
  -rwxr-xr-x 1 buildd buildd 166208 Jul 29 14:35 
debian/virtualbox/usr/lib/virtualbox/VBoxSDL

  It seems to me that either dh_strip or something it calls (strip,
  debugedit) looses the setuid permission in hirsute and up.

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


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

[Kernel-packages] [Bug 1949232] Re: Touchpad doesn't work in ubuntu.

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-signed-hwe-5.11 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Touchpad doesn't work in ubuntu.

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

Bug description:
  The touchpad works fine in windows 10. I tried to install drivers, but
  with no luck. It is not totally being recognized by the system.

  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 29 21:43:23 2021
  InstallationDate: Installed on 2021-10-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)

[crysman]

Thanks to @Jaroslav_Kysela, we've got the solution.

SOLUTION SUMMARY:
1) use kernel 5.11+
2) use `snd_sof_intel_hda_common.hda_model=alc255-acer` kernel boot parameter

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

Title:
  [Acer Spin 5 - SP513-54N] External headset microphone not working on
  Ubuntu 20.10 (not even wired, cable headset)

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Recently, external microphone has stopped working while using classic
  wired audio combo jack headset.

  Basics:

  1) Headset's microphone works fine both in MS Windows on the same machine and 
on older Xubuntu on another machine.
  2) Internal laptop mic works normally.
  3) Yes, I have mic unmuted in settings.

  I've followed whole step1 from this troubleshoot guide:
  https://help.ubuntu.com/community/SoundTroubleshootingProcedure

  Did not help.

  There are more information with screenshots here:
  https://askubuntu.com/questions/1305942/external-headset-microphone-
  not-working-on-ubuntu-20-10-not-even-wired-cable-h:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crysman2301 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 13:31:13 2021
  InstallationDate: Installed on 2020-06-19 (210 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago)
  dmi.bios.date: 07/17/2020
  dmi.bios.release: 1.5
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.05
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 1949304] [NEW] package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess ret

[mvelte54]

Public bug reported:

Tried to install on 20.04.3 Ubuntu Gnome andwill not load.Trying to get
WiFi on Dell Optiplex 9020

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
AptOrdering:
 linux-headers-3.5.0-30:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Oct 31 12:38:49 2021
ErrorMessage: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2021-10-30 (1 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: bcmwl
Title: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to 
install/upgrade: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check third-party-packages

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

Title:
  package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to
  install/upgrade: installed bcmwl-kernel-source package post-
  installation script subprocess returned error exit status 10

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Tried to install on 20.04.3 Ubuntu Gnome andwill not load.Trying to
  get WiFi on Dell Optiplex 9020

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   linux-headers-3.5.0-30:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Oct 31 12:38:49 2021
  ErrorMessage: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2021-10-30 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to 
install/upgrade: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1926330] Re: HWE kernels should support eBPF CO-RE

[Rafael David Tinoco]

** Changed in: dwarves-dfsg (Ubuntu Bionic)
   Status: Won't Fix => Confirmed

** Changed in: linux (Ubuntu Bionic)
   Status: Won't Fix => 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/1926330

Title:
  HWE kernels should support eBPF CO-RE

Status in dwarves-dfsg package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in dwarves-dfsg source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in dwarves-dfsg source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in dwarves-dfsg source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Fix Released

Bug description:
  I had recent discussion with kernel team regarding support or not BTF
  in HWE kernels (Bionic and Focal). Having CONFIG_DEBUG_INFO_BTF option
  enabled for HWE kernels (v4.4 and v.4.8) would allow eBPF based code
  (powered by libbpf or not) to be RO.CE
  (https://github.com/rafaeldtinoco/portablebpf for more information).

  By allowing runtime relocations, using provided BTF, libbpf binaries
  might end up running, without modifications, in different kernel
  versions (from Bionic HWE v5.4 kernel to Hirsute v5.11).

  A good example would be to support tools such as:
  
https://github.com/aquasecurity/tracee/discussions/713#discussioncomment-665641
  An ebpf powered backend for a containers security solution.

  Considering:

  $ rmadisonb dwarves
   dwarves | 1.9-1  | precise/universe | amd64
   dwarves | 1.10-2 | trusty   | amd64
   dwarves | 1.10-2.1   | xenial/universe  | amd64
   dwarves | 1.10-2.1build1 | bionic/universe  | amd64
   dwarves | 1.15-2 | focal/universe   | amd64
   dwarves | 1.17-1 | groovy/universe  | amd64
   dwarves | 1.20-1 | hirsute/universe | amd64
   dwarves | 1.20-1 | impish/universe  | amd64

  And the fact that the 'pahole' binary, from dwarves package, is the
  one to blame, not to have CONFIG_DEBUG_INFO_BTF available, for this
  bug to be solved we would have to provide a backport of dwarves (at
  least 1.17-1) to Bionic and Focal. It could have another name (not to
  mess with original dwarves package and its dependencies) and it is
  unclear if it needs to be in [main] or [universe].

  Question: Would have dwarves backported in -backports be enough for
  Bionic and Focal HWE kernels compilation to have CONFIG_DEBUG_INFO_BTF
  enabled ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1926330/+subscriptions


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

[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11

[Nikolaos Chachampis]

Same here, Dell Latitude 7490, freezes when running in battery with
5.11.x and 5.13.x kernels. Doesn't happen with 5.8.x.

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

Title:
  Ubuntu 20.04 freeze since kernel 5.11

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since the last kernel update 5.11.0-25-generic, the system freezes in a few 
seconds or minutes, sometimes even on the login screen. 
  The machine is a recent dell latitude 7490. The graphics card is Intel 
Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the 
previous kernel 5.8.0-63.
  I had the same problem with fedora a few months ago, which forced me to 
switch to ubuntu without any problems so far.  
  Thanks for your help.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  plawrence   1996 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-21 (414 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.187.15
  Tags:  focal
  Uname: Linux 5.11.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/23/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1949301] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (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/1949301

Title:
  Radeon HD 5400 page flips fills syslog

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Syslog fills up with "drm:radeon_crtc_page_flip_target [radeon]] flip-
  ioctl() " after adding plugin PCIexpress graphics board. Mobo
  integrated Radeon HD4000 did not cause issues.

  As it is plugin I cannot change the memory allocation.

  Causes occasional lockups, probably due to syslog file size.
  Kubuntu distribution with FOSS graphics drivers.
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  Linux SAL9000 5.4.0-90-generic #101-Ubuntu SMP  x86_64 x86_64 x86_64 GNU/Linux

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-90-generic 5.4.0-90.101
  ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148
  Uname: Linux 5.4.0-90-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davidbowman   2858 F pulseaudio
   /dev/snd/controlC1:  davidbowman   2858 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Oct 31 09:27:34 2021
  HibernationDevice: RESUME=UUID=b636f38e-30a4-43a2-8943-8c0046119221
  InstallationDate: Installed on 2017-05-07 (1637 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic 
root=UUID=55048241-0ce7-40fd-a1e8-9f289c293980 ro iommu=noagp ipv6.disable=1 
net.ifnames=0 biosdevname=0 splash raid=noautodetect ipv6.disable=1 
net.ifnames=0 biosdevname=0 acpi_enforce_resources=strict quiet drm.debug=0xe 
plymouth:debug crashkernel=512M-:192M
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-90-generic N/A
   linux-backports-modules-5.4.0-90-generic  N/A
   linux-firmware1.187.20
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: 760GM-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd05/11/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn760GM-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1949301] [NEW] Radeon HD 5400 page flips fills syslog

[Mats]

Public bug reported:

Syslog fills up with "drm:radeon_crtc_page_flip_target [radeon]] flip-
ioctl() " after adding plugin PCIexpress graphics board. Mobo integrated
Radeon HD4000 did not cause issues.

As it is plugin I cannot change the memory allocation.

Causes occasional lockups, probably due to syslog file size.
Kubuntu distribution with FOSS graphics drivers.
Description:Ubuntu 20.04.3 LTS
Release:20.04
Linux SAL9000 5.4.0-90-generic #101-Ubuntu SMP  x86_64 x86_64 x86_64 GNU/Linux

Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-90-generic 5.4.0-90.101
ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148
Uname: Linux 5.4.0-90-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  davidbowman   2858 F pulseaudio
 /dev/snd/controlC1:  davidbowman   2858 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Sun Oct 31 09:27:34 2021
HibernationDevice: RESUME=UUID=b636f38e-30a4-43a2-8943-8c0046119221
InstallationDate: Installed on 2017-05-07 (1637 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic 
root=UUID=55048241-0ce7-40fd-a1e8-9f289c293980 ro iommu=noagp ipv6.disable=1 
net.ifnames=0 biosdevname=0 splash raid=noautodetect ipv6.disable=1 
net.ifnames=0 biosdevname=0 acpi_enforce_resources=strict quiet drm.debug=0xe 
plymouth:debug crashkernel=512M-:192M
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-90-generic N/A
 linux-backports-modules-5.4.0-90-generic  N/A
 linux-firmware1.187.20
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.20
dmi.board.name: 760GM-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd05/11/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn760GM-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

Title:
  Radeon HD 5400 page flips fills syslog

Status in linux package in Ubuntu:
  New

Bug description:
  Syslog fills up with "drm:radeon_crtc_page_flip_target [radeon]] flip-
  ioctl() " after adding plugin PCIexpress graphics board. Mobo
  integrated Radeon HD4000 did not cause issues.

  As it is plugin I cannot change the memory allocation.

  Causes occasional lockups, probably due to syslog file size.
  Kubuntu distribution with FOSS graphics drivers.
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  Linux SAL9000 5.4.0-90-generic #101-Ubuntu SMP  x86_64 x86_64 x86_64 GNU/Linux

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-90-generic 5.4.0-90.101
  ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148
  Uname: Linux 5.4.0-90-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davidbowman   2858 F pulseaudio
   /dev/snd/controlC1:  davidbowman   2858 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Oct 31 09:27:34 2021
  HibernationDevice: RESUME=UUID=b636f38e-30a4-43a2-8943-8c0046119221
  InstallationDate: Installed on 2017-05-07 (1637 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic 
root=UUID=55048241-0ce7-40fd-a1e8-9f289c293980 ro iommu=noagp ipv6.disable=1 
net.ifnames=0 biosdevname=0 splash raid=noautodetect ipv6.disable=1 
net.ifnames=0 biosdevname=0 acpi_enforce_resources=strict quiet drm.debug=0xe 
plymouth:debug crashkernel=512M-:192M
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-90-generic N/A
   linux-backports-modules-5.4.0-90-generic  N/A
   

[Kernel-packages] [Bug 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

[navycat]

** Tags removed: groovy

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

Title:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

  PIONEER BD-RW   BDR-205

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-23-generic 5.8.0-23.24
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 10:11:53 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-23-generic N/A
   linux-backports-modules-5.8.0-23-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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


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

[Kernel-packages] [Bug 1900391] Re: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled

[navycat]

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

Title:
  EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is
  disabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4.589406] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but 
ECC is disabled
  [4.589410] EDAC sbridge: Couldn't find mci handler
  [4.589411] EDAC sbridge: Failed to register device with error -19.

  but x79 doesn't have ecc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-23-generic 5.8.0-23.24
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 10:19:05 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-23-generic N/A
   linux-backports-modules-5.8.0-23-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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


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

[Kernel-packages] [Bug 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

[navycat]

** Tags added: groovy

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

Title:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

  PIONEER BD-RW   BDR-205

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-23-generic 5.8.0-23.24
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 10:11:53 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-23-generic N/A
   linux-backports-modules-5.8.0-23-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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


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

[Kernel-packages] [Bug 1945136] Re: Broken audio capture subsystem

[navycat]

In general descriprion i said "ffmpeg -f alsa -i  -t 30
out.wav and ffmpeg -f pulse -i  -t 30 out.wav captures
sound normally."

** Changed in: ubuntu-mate
   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/1945136

Title:
  Broken audio capture subsystem

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed

Bug description:
  In Impish the problem of capturing audio by discord (from app or browser does 
not matter) when broadcasting reappeared.
  The window is being captured or not - it doesn't matter.
  It looks like a regression.

  Webcamoid don't capture sound from micro too.

  If I set gstreamer method instead of ffmpeg 4.4 then sound appears, but very 
laggy
  Discord launched in a browser and streaming an adjacent tab does the same.
  I don't even know what to report on. Looks like a broken audio capture 
subsystem.

  ffmpeg -f alsa -i  -t 30 out.wav and ffmpeg -f pulse -i
   -t 30 out.wav captures sound normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2083 F pulseaudio
   /dev/snd/controlC0:  navycat2083 F pulseaudio
   /dev/snd/controlC1:  navycat2083 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Sep 27 05:06:06 2021
  InstallationDate: Installed on 2021-05-28 (121 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210526)
  IwConfig:
   lono wireless extensions.

   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=bc8287ed-7647-42ae-8f04-6297f1c30b1d ro nouveau.noaccel=1 
nouveau.nofbaccel=1 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.200
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: yes
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:skuPROJECT_SUB_TAG:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1945136/+subscriptions


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

[Kernel-packages] [Bug 1948701] Re: Hard system lock under 5.* kernel on standard laptop

[Dirk Eddelbuettel]

If anybody has a hypothesis of what could be causing the lock, I would
be game to trying different kernel builds (or parameterizations).  So
far I mostly glad I can run the machine again, even if it needs a 4.*
kernel.

Otherwise, is there a particular crash I could enable to diagnose?  The
machine really locks *hard* i.e. all I can do once it happens is
powercycle so I am not too hopeful about logging.

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

Title:
  Hard system lock under 5.* kernel on standard laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This issue appeared first under 21.04, and I (wrongly) suspected a bug
  in the window manager or graphics stack. I posted on askubuntu at

  https://askubuntu.com/questions/1346317/ubuntu-21-04-and-21-10-lock-
  hard-with-basic-gui-redrawing-using-standard-intel-g

  and even offered a bounty but no luck.  I then hopen 21.10 may solve
  it, but alas, no.

  At issue is a fairly immediate system lock as soon as I use Chrome or
  Slack and switch desktops.  It typically locks the machine with
  minutes of a reboot -- making it unuseable under GUI.

  On the other hand, I kept it running 'headless' (just ssh'ed in from
  byobu running on my desktop) for a month so I had some reason to
  believe the hard ware was not at fault.

  Now, more recently, I realized that I had not tried an older kernel,
  and indeed under 4.13.0-46-generic, still installed from an older
  relese, everything runs fine!

  I would be happy to help debug if you pointers or test builds.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16
  Uname: Linux 4.13.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edd2005 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Mon Oct 25 13:04:38 2021
  HibernationDevice: RESUME=UUID=97ca6744-22ea-45bd-bf19-38197b40062c
  InstallationDate: Installed on 2016-08-08 (1904 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20FCCTO1WW
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-46-generic 
root=UUID=5f3d6606-96bb-422c-9918-62d7cf6850fb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-46-generic N/A
   linux-backports-modules-4.13.0-46-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-14 (11 days ago)
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FCCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1949289] Re: Screen flickering and then turn off.

[Andrea]

Can you please advise how to reattach the log? I thought this was automatically 
done since I saw the screen annoying for papers
Three issues to capture the details

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

Title:
  Screen flickering and then turn off.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I'm working without the power cable connected (mostly), I noticed that 
after some while - still can't identify a pattern - the screen starts to 
flicker and then goes black/turn off.
  Closing the lid and reopening after few secs restores the screen (sure at 
that point I have to log in again).

  As far as I've seen, if a second screen is connected, this is not
  happening. But at that point I have the power cable in. So this might
  explain why.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-release-upgrader-core 1:21.10.8
  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
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 31 08:57:52 2021
  InstallationDate: Installed on 2021-10-19 (11 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1949289] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1949289

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

Title:
  Screen flickering and then turn off.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I'm working without the power cable connected (mostly), I noticed that 
after some while - still can't identify a pattern - the screen starts to 
flicker and then goes black/turn off.
  Closing the lid and reopening after few secs restores the screen (sure at 
that point I have to log in again).

  As far as I've seen, if a second screen is connected, this is not
  happening. But at that point I have the power cable in. So this might
  explain why.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-release-upgrader-core 1:21.10.8
  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
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 31 08:57:52 2021
  InstallationDate: Installed on 2021-10-19 (11 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1949289] Re: Screen flickering and then turn off.

[Chris Guiver]

Thank you for reporting this bug to Ubuntu.

I'm changing package from `ubuntu-release-upgrader` (which is used to
upgrade your system from one release (eg. 21.10) to a later release (eg.
22.04); your system indicates you're using the same release as was
installed & haven't used the tool.

It's been changed to the 'linux' kernel; the closest fit I an think of.
Alas few details currently exist (as bug was filed on the release-
upgrade tool); so you may be asked to provide more details.

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  Screen flickering and then turn off.

Status in linux package in Ubuntu:
  New

Bug description:
  When I'm working without the power cable connected (mostly), I noticed that 
after some while - still can't identify a pattern - the screen starts to 
flicker and then goes black/turn off.
  Closing the lid and reopening after few secs restores the screen (sure at 
that point I have to log in again).

  As far as I've seen, if a second screen is connected, this is not
  happening. But at that point I have the power cable in. So this might
  explain why.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-release-upgrader-core 1:21.10.8
  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
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 31 08:57:52 2021
  InstallationDate: Installed on 2021-10-19 (11 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1949289] [NEW] Screen flickering and then turn off.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I'm working without the power cable connected (mostly), I noticed that 
after some while - still can't identify a pattern - the screen starts to 
flicker and then goes black/turn off.
Closing the lid and reopening after few secs restores the screen (sure at that 
point I have to log in again).

As far as I've seen, if a second screen is connected, this is not
happening. But at that point I have the power cable in. So this might
explain why.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: ubuntu-release-upgrader-core 1:21.10.8
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
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 31 08:57:52 2021
InstallationDate: Installed on 2021-10-19 (11 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade impish wayland-session
-- 
Screen flickering and then turn off. 
https://bugs.launchpad.net/bugs/1949289
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1949275] Re: linux-image-raspi PWM not available

[Alex Kurichenko]

Duplicate of 1949276

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

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

Title:
  linux-image-raspi PWM not available

Status in linux-meta-raspi package in Ubuntu:
  Invalid

Bug description:
  I'm using Raspberry Pi 4b with Ubuntu 21.10.
  Seems like all 5.13 kernels don't have PWM support.

  Replication steps:
  - Enable pwm in config.txt:
  dtoverlay=pwm-2chan,pin=12,func=4,pin2=13,func2=4

  - Check /sys/class/pwm

  Expected result:
  PWM exists

  - What I get:

  root@raspberrypi:~# ls -l /sys/class/pwm/
  total 0
  root@raspberrypi:~#

  ---
  Same output with 5.11.0-1021-raspi kernel:

  root@raspberrypi:~# uname -a
  Linux raspberrypi 5.11.0-1021-raspi #22-Ubuntu SMP PREEMPT Wed Oct 6 17:30:38 
UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
  root@raspberrypi:~# ls -l /sys/class/pwm/
  total 0
  lrwxrwxrwx 1 root root 0 окт 31 00:49 pwmchip0 -> 
../../devices/platform/soc/fe20c000.pwm/pwm/pwmchip0

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


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

[Kernel-packages] [Bug 1949276] Re: linux-image-raspi PWM not available

[Alex Kurichenko]

** Package changed: linux (Ubuntu) => linux-raspi (Ubuntu)

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

** Description changed:

  Hello,
  
  I'm using Raspberry Pi 4b with Ubuntu 21.10.
  Seems like all 5.13 kernels don't have PWM support.
  
  Replication steps:
  - Enable pwm in config.txt:
  `dtoverlay=pwm-2chan,pin=12,func=4,pin2=13,func2=4`
  
  - Check /sys/class/pwm
  
  Expected result:
  PWM exists
+ lrwxrwxrwx 1 root root 0 окт 31 00:49 pwmchip0 -> 
../../devices/platform/soc/fe20c000.pwm/pwm/pwmchip0
+ 
  
  - What I get:
- ```
+ 
  root@raspberrypi:~# ls -l /sys/class/pwm/
  total 0
  root@raspberrypi:~#
- ```
+ 
  ---
  Same output using 5.11.0-1021-raspi kernel:
- ```
- root@raspberrypi:~# uname -a 
+ 
+ root@raspberrypi:~# uname -a
  Linux raspberrypi 5.11.0-1021-raspi #22-Ubuntu SMP PREEMPT Wed Oct 6 17:30:38 
UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
  root@raspberrypi:~# ls -l /sys/class/pwm/
  total 0
  lrwxrwxrwx 1 root root 0 окт 31 00:49 pwmchip0 -> 
../../devices/platform/soc/fe20c000.pwm/pwm/pwmchip0
- ```
- --- 
+ 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC2', 
'/dev/snd/pcmC2D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.10
  ImageMediaBuild: 20210421.1
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 
xHCI USB 3.0 Controller
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 24ae:2010 Shenzhen Rapoo Technology Co., Ltd. Rapoo 
2.4G Wireless Device
-  Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 24ae:2010 Shenzhen Rapoo Technology Co., Ltd. Rapoo 
2.4G Wireless Device
+  Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=ru_UA.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=ru_UA.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 vc4drmfb
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:61:DD:84 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 
root=/dev/mmcblk0p2 rootwait rootfstype=ext4 fixrtc pty.legacy_count=6 
zswap.enabled=1 net.ifnames=0
  ProcVersionSignature: Ubuntu 5.13.0-1010.11-raspi 5.13.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.13.0-1010-raspi N/A
-  linux-backports-modules-5.13.0-1010-raspi  N/A
-  linux-firmware 1.201.1
+  linux-restricted-modules-5.13.0-1010-raspi N/A
+  linux-backports-modules-5.13.0-1010-raspi  N/A
+  linux-firmware 1.201.1
  StagingDrivers: bcm2835_mmal_vchiq bcm2835_v4l2 vc_sm_cma bcm2835_codec 
bcm2835_isp snd_bcm2835
  Tags:  arm64-image raspi-image impish staging
  Uname: Linux 5.13.0-1010-raspi aarch64
  UpgradeStatus: Upgraded to impish on 2021-08-31 (60 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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

Title:
  linux-image-raspi PWM not available

Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm using Raspberry Pi 4b with Ubuntu 21.10.
  Seems like all 5.13 kernels don't have PWM support.

  Replication steps:
  - Enable pwm in config.txt:
  `dtoverlay=pwm-2chan,pin=12,func=4,pin2=13,func2=4`

  - Check /sys/class/pwm

  Expected result:
  PWM exists
  lrwxrwxrwx 1 root root 0 окт 31 00:49 pwmchip0 -> 
../../devices/platform/soc/fe20c000.pwm/pwm/pwmchip0

  
  - What I get:

  root@raspberrypi:~# ls -l /sys/class/pwm/
  total 0
  root@raspberrypi:~#

  ---
  Same output using 5.11.0-1021-raspi kernel:

  root@raspberrypi:~# uname -a
  Linux raspberrypi 5.11.0-1021-raspi #22-Ubuntu SMP PREEMPT Wed Oct 6 17:30:38 
UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
  root@raspberrypi:~# ls -l /sys/class/pwm/
  total 0
  lrwxrwxrwx 1 root root 0 окт 31 00:49 pwmchip0 -> 
../../devices/platform/soc/fe20c000.pwm/pwm/pwmchip0

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC2', 
'/dev/snd/pcmC2D0p', '/dev/snd/controlC1', 

[Kernel-packages] [Bug 1939160] Re: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work (updated system log)

[azen0r]

solved with newest 5.11.0-38-generic kernel update (Ubuntu20.04.3)

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

Title:
  [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older
  kernel versions work (updated system log)

Status in linux-signed-hwe-5.11 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  I had previously submitted this bug here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937914 , but I
  submitted a system log from an older, working version of Ubuntu rather
  than from the failing version. This report has the updated log.

  While starting the my laptop

  (Computer Model: HP Probook 450 G6
  ProdID 5YH15UT#ABA
  Memory: 15.5 GB
  Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8
  Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2)
  Disk Capacity: 256.1 GB)

  which runs

  (OS Name: Ubuntu 20.04.2 LTS
  OS Type: 64-bit
  GNOME Version: 3.36.8
  Windowing System: X11)

  the monitor turns off as soon as Ubuntu loads. The OS loads as normal
  and my external monitor still works, but my laptop monitor does not. I
  was able to fix the problem by pressing ESC as soon as the HP logo
  appears during start-up, then selecting "Advanced Ubuntu Options",
  then choosing an older version of Ubuntu (currently that's
  ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...).

  It seems clear that this problem is caused by a bug that was
  introduced in one of the more recent updates (...5.8.0-59..., maybe?).
  I am not at all sure that the problem is in xorg; the package
  identification webpage just suggested that, if the monitor is blank
  when I would expect to see the Ubuntu logo during startup, then I
  should say that the relevant package is xorg.

  I am more than happy to run additional diagnostics that you would
  recommend if that would help you diagnose and fix the problem.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  6 10:34:40 2021
  InstallationDate: Installed on 2021-07-06 (30 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)

[crysman]

I've made a new test, currently on POPOS 21.04, kernel 5.13
❱ cat /proc/cmdline
initrd=\EFI\Pop_OS-a99686bf-c48a-464b-af3a-25f67847049a\initrd.img 
root=UUID=a99686bf-c48a-464b-af3a-25f67847049a ro snd_intel_dspcfg.dsp_driver=1 
snd_hda_intel.model=headset-mic

1) default boot options:

- internal mic works, external not

2) changed to  intel_dspcfg.dsp_driver + headset-mic:

❱ cat /proc/cmdline
initrd=\EFI\Pop_OS-a99686bf-c48a-464b-af3a-25f67847049a\initrd.img 
root=UUID=a99686bf-c48a-464b-af3a-25f67847049a ro snd_intel_dspcfg.dsp_driver=1 
snd_hda_intel.model=headset-mic

- neither mic works

3) changed to intel_dspcfg.dsp_driver + alc255-acer
=
❱ cat /proc/cmdline
initrd=\EFI\Pop_OS-a99686bf-c48a-464b-af3a-25f67847049a\initrd.img 
root=UUID=a99686bf-c48a-464b-af3a-25f67847049a ro quiet splash 
snd_intel_dspcfg.dsp_driver=1 snd_hda_intel.model=alc255-acer

- external mic is now working (!), when jack is plugged-in, it corerctly asks 
what device have I connected (headset or headphones?)
- internal mic is not working, though :(

4) it (does not) works with pci=nocrs, too:

❱ cat /proc/cmdline
initrd=\EFI\Pop_OS-a99686bf-c48a-464b-af3a-25f67847049a\initrd.img 
root=UUID=a99686bf-c48a-464b-af3a-25f67847049a ro quiet splash pci=nocrs 
snd_intel_dspcfg.dsp_driver=1 snd_hda_intel.model=alc255-acer


So, this solution is not very practical, because when I do not have headset 
available at the moment, I cannot use internal microphone :(

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

Title:
  [Acer Spin 5 - SP513-54N] External headset microphone not working on
  Ubuntu 20.10 (not even wired, cable headset)

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Recently, external microphone has stopped working while using classic
  wired audio combo jack headset.

  Basics:

  1) Headset's microphone works fine both in MS Windows on the same machine and 
on older Xubuntu on another machine.
  2) Internal laptop mic works normally.
  3) Yes, I have mic unmuted in settings.

  I've followed whole step1 from this troubleshoot guide:
  https://help.ubuntu.com/community/SoundTroubleshootingProcedure

  Did not help.

  There are more information with screenshots here:
  https://askubuntu.com/questions/1305942/external-headset-microphone-
  not-working-on-ubuntu-20-10-not-even-wired-cable-h:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crysman2301 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 13:31:13 2021
  InstallationDate: Installed on 2020-06-19 (210 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago)
  dmi.bios.date: 07/17/2020
  dmi.bios.release: 1.5
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.05
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)

[crysman]

issue still present in hirsute (21.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/1912052

Title:
  [Acer Spin 5 - SP513-54N] External headset microphone not working on
  Ubuntu 20.10 (not even wired, cable headset)

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Recently, external microphone has stopped working while using classic
  wired audio combo jack headset.

  Basics:

  1) Headset's microphone works fine both in MS Windows on the same machine and 
on older Xubuntu on another machine.
  2) Internal laptop mic works normally.
  3) Yes, I have mic unmuted in settings.

  I've followed whole step1 from this troubleshoot guide:
  https://help.ubuntu.com/community/SoundTroubleshootingProcedure

  Did not help.

  There are more information with screenshots here:
  https://askubuntu.com/questions/1305942/external-headset-microphone-
  not-working-on-ubuntu-20-10-not-even-wired-cable-h:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crysman2301 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 13:31:13 2021
  InstallationDate: Installed on 2020-06-19 (210 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago)
  dmi.bios.date: 07/17/2020
  dmi.bios.release: 1.5
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.05
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 1949286] Re: [MIR]: Include dwarves-dfsg-hwe package into Bionic and Focal

[Rafael David Tinoco]

After this MIR, the kernel HWE source code will have to use "pahole-btf"
tool to do the BTF encoding in the HWE kernel builds from then on.

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

Title:
  [MIR]: Include dwarves-dfsg-hwe package into Bionic and Focal

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  This is a follow-on request of bug:

  HWE kernels should support eBPF CO-RE
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330

  [Availability]

  - Package is already available in all Ubuntu versions.
  - This is a backported version (Impish) to Bionic and Focal

  [Rationale]

  - Current package dwarves-dfsg is old in Ubuntu Bionic and Focal.
  - HWE kernel compilation needs recent "pahole" binary to encode BTF[1] 
information.
  - After talking to SRU team members, updating dwarves-dfsg seemed risky.
  - Creating a new package containing only the new "pahole" tool binary is the 
best option. 
  - Kernel HWE compilations will need to use this package, so it has to be in 
main repository (as kernels builds depend on main only).

  [Security]

  - This package is already stable and exists in Ubuntu.

  
  [Quality assurance]

  - This package is already stable and exists in Ubuntu.

  [Dependencies]

  - Same dependencies as dwarves-dfsg package (already satisfied).

  [Standards compliance]

  - This package is already stable and exists in Ubuntu.

  [Maintenance]

  - SRUs for dwarves-dfsg package within Impish should be applied to
  this package as well.

  [Background information]

  Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330
  contains more information about why this is needed.

  I have been maintaining BTFHUB
  (https://github.com/aquasecurity/btfhub) in order to generate BTF
  files to each existing Ubuntu kernel but I feel that a simple change,
  like adding a recent pahole tool to the main archive in Bionic and
  Focal, is enough to resolve a VERY BIG problem for eBPF applications
  to run in HWE kernels in those Ubuntu versions.

  A very complete explanation on why BTF is needed for eBPF to be
  portable among different kernels currently exists at:
  https://github.com/aquasecurity/btfhub/tree/main/tools.

  Projects that would already benefit from this change:

  - Microsoft: Sysmon Tools for Linux
  - Microsoft: Inspektor Gadge
  - Elastic: They're working together with us upstream
  - Aqua Security: libbpfgo & tracee-ebpf
  - All BCC libbpf-tools

  and many more.

  
  [1] https://www.kernel.org/doc/html/latest/bpf/btf.html

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


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

[Kernel-packages] [Bug 1926330] Re: HWE kernels should support eBPF CO-RE

[Rafael David Tinoco]

I have placed a MIR for "pahole-btf" package (a backport of Impish's
dwarves-dfsg package to Bionic and Focal) at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949286. This way,
the kernel builds may depend on "pahole-btf" binary package, from main,
and finally include BTF debug information into Bionic and Focal HWE
kernels.

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

Title:
  HWE kernels should support eBPF CO-RE

Status in dwarves-dfsg package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in dwarves-dfsg source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Won't Fix
Status in dwarves-dfsg source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in dwarves-dfsg source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Fix Released

Bug description:
  I had recent discussion with kernel team regarding support or not BTF
  in HWE kernels (Bionic and Focal). Having CONFIG_DEBUG_INFO_BTF option
  enabled for HWE kernels (v4.4 and v.4.8) would allow eBPF based code
  (powered by libbpf or not) to be RO.CE
  (https://github.com/rafaeldtinoco/portablebpf for more information).

  By allowing runtime relocations, using provided BTF, libbpf binaries
  might end up running, without modifications, in different kernel
  versions (from Bionic HWE v5.4 kernel to Hirsute v5.11).

  A good example would be to support tools such as:
  
https://github.com/aquasecurity/tracee/discussions/713#discussioncomment-665641
  An ebpf powered backend for a containers security solution.

  Considering:

  $ rmadisonb dwarves
   dwarves | 1.9-1  | precise/universe | amd64
   dwarves | 1.10-2 | trusty   | amd64
   dwarves | 1.10-2.1   | xenial/universe  | amd64
   dwarves | 1.10-2.1build1 | bionic/universe  | amd64
   dwarves | 1.15-2 | focal/universe   | amd64
   dwarves | 1.17-1 | groovy/universe  | amd64
   dwarves | 1.20-1 | hirsute/universe | amd64
   dwarves | 1.20-1 | impish/universe  | amd64

  And the fact that the 'pahole' binary, from dwarves package, is the
  one to blame, not to have CONFIG_DEBUG_INFO_BTF available, for this
  bug to be solved we would have to provide a backport of dwarves (at
  least 1.17-1) to Bionic and Focal. It could have another name (not to
  mess with original dwarves package and its dependencies) and it is
  unclear if it needs to be in [main] or [universe].

  Question: Would have dwarves backported in -backports be enough for
  Bionic and Focal HWE kernels compilation to have CONFIG_DEBUG_INFO_BTF
  enabled ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1926330/+subscriptions


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

[Kernel-packages] [Bug 1949286] Re: [MIR]: Include dwarves-dfsg-hwe package into Bionic and Focal

[Rafael David Tinoco]

The proposed package is at:

https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/pahole-btf

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

Title:
  [MIR]: Include dwarves-dfsg-hwe package into Bionic and Focal

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  This is a follow-on request of bug:

  HWE kernels should support eBPF CO-RE
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330

  [Availability]

  - Package is already available in all Ubuntu versions.
  - This is a backported version (Impish) to Bionic and Focal

  [Rationale]

  - Current package dwarves-dfsg is old in Ubuntu Bionic and Focal.
  - HWE kernel compilation needs recent "pahole" binary to encode BTF[1] 
information.
  - After talking to SRU team members, updating dwarves-dfsg seemed risky.
  - Creating a new package containing only the new "pahole" tool binary is the 
best option. 
  - Kernel HWE compilations will need to use this package, so it has to be in 
main repository (as kernels builds depend on main only).

  [Security]

  - This package is already stable and exists in Ubuntu.

  
  [Quality assurance]

  - This package is already stable and exists in Ubuntu.

  [Dependencies]

  - Same dependencies as dwarves-dfsg package (already satisfied).

  [Standards compliance]

  - This package is already stable and exists in Ubuntu.

  [Maintenance]

  - SRUs for dwarves-dfsg package within Impish should be applied to
  this package as well.

  [Background information]

  Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330
  contains more information about why this is needed.

  I have been maintaining BTFHUB
  (https://github.com/aquasecurity/btfhub) in order to generate BTF
  files to each existing Ubuntu kernel but I feel that a simple change,
  like adding a recent pahole tool to the main archive in Bionic and
  Focal, is enough to resolve a VERY BIG problem for eBPF applications
  to run in HWE kernels in those Ubuntu versions.

  A very complete explanation on why BTF is needed for eBPF to be
  portable among different kernels currently exists at:
  https://github.com/aquasecurity/btfhub/tree/main/tools.

  Projects that would already benefit from this change:

  - Microsoft: Sysmon Tools for Linux
  - Microsoft: Inspektor Gadge
  - Elastic: They're working together with us upstream
  - Aqua Security: libbpfgo & tracee-ebpf
  - All BCC libbpf-tools

  and many more.

  
  [1] https://www.kernel.org/doc/html/latest/bpf/btf.html

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


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

[Kernel-packages] [Bug 1949286] Re: [MIR]: Include dwarves-dfsg-hwe package into Bionic and Focal

[Rafael David Tinoco]

** Description changed:

  This is a follow-on request of bug:
  
  HWE kernels should support eBPF CO-RE
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330
  
  [Availability]
  
  - Package is already available in all Ubuntu versions.
  - This is a backported version (Impish) to Bionic and Focal
  
  [Rationale]
  
- - Current package dwarves-dfsg is old in Ubuntu Bionic and Focal
- - HWE kernel compilation needs recent "pahole" binary to encode BTF[1] 
information
- - After talking to SRU team members, updating dwarves-dfsg seemed risky
- - Creating a new package for a more recent version of dwarves seems 
appropriate 
+ - Current package dwarves-dfsg is old in Ubuntu Bionic and Focal.
+ - HWE kernel compilation needs recent "pahole" binary to encode BTF[1] 
information.
+ - After talking to SRU team members, updating dwarves-dfsg seemed risky.
+ - Creating a new package containing only the new "pahole" tool binary is the 
best option. 
+ - Kernel HWE compilations will need to use this package, so it has to be in 
main repository (as kernels builds depend on main only).
  
  [Security]
  
+ - This package is already stable and exists in Ubuntu.
+ 
+ 
  [Quality assurance]
  
- [UI standards]
+ - This package is already stable and exists in Ubuntu.
  
  [Dependencies]
  
+ - Same dependencies as dwarves-dfsg package (already satisfied).
+ 
  [Standards compliance]
+ 
+ - This package is already stable and exists in Ubuntu.
  
  [Maintenance]
  
+ - SRUs for dwarves-dfsg package within Impish should be applied to this
+ package as well.
+ 
  [Background information]
  
+ Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330
+ contains more information about why this is needed.
+ 
+ I have been maintaining BTFHUB (https://github.com/aquasecurity/btfhub)
+ in order to generate BTF files to each existing Ubuntu kernel but I feel
+ that a simple change, like adding a recent pahole tool to the main
+ archive in Bionic and Focal, is enough to resolve a VERY BIG problem for
+ eBPF applications to run in HWE kernels in those Ubuntu versions.
+ 
+ A very complete explanation on why BTF is needed for eBPF to be portable
+ among different kernels currently exists at:
+ https://github.com/aquasecurity/btfhub/tree/main/tools.
+ 
+ Projects that would already benefit from this change:
+ 
+ - Microsoft: Sysmon Tools for Linux
+ - Microsoft: Inspektor Gadge
+ - Elastic: They're working together with us upstream
+ - Aqua Security: libbpfgo & tracee-ebpf
+ - All BCC libbpf-tools
+ 
+ and many more.
  
  
  [1] https://www.kernel.org/doc/html/latest/bpf/btf.html

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

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

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

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => High

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

** Changed in: linux (Ubuntu Focal)
   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/1949286

Title:
  [MIR]: Include dwarves-dfsg-hwe package into Bionic and Focal

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  This is a follow-on request of bug:

  HWE kernels should support eBPF CO-RE
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330

  [Availability]

  - Package is already available in all Ubuntu versions.
  - This is a backported version (Impish) to Bionic and Focal

  [Rationale]

  - Current package dwarves-dfsg is old in Ubuntu Bionic and Focal.
  - HWE kernel compilation needs recent "pahole" binary to encode BTF[1] 
information.
  - After talking to SRU team members, updating dwarves-dfsg seemed risky.
  - Creating a new package containing only the new "pahole" tool binary is the 
best option. 
  - Kernel HWE compilations will need to use this package, so it has to be in 
main repository (as kernels builds depend on main only).

  [Security]

  - This package is already stable and exists in Ubuntu.

  
  [Quality assurance]

  - This package is already stable and exists in Ubuntu.

  [Dependencies]

  - Same dependencies as dwarves-dfsg package (already satisfied).

  [Standards compliance]

  - This package is already stable and exists in Ubuntu.

  [Maintenance]

  - SRUs for dwarves-dfsg package within Impish should be applied to
  this package as well.

  [Background information]

  Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330
  contains more information about why this is needed.

  I have been maintaining BTFHUB
  (https://github.com/aquasecurity/btfhub) in order to generate BTF
  files 

[Kernel-packages] [Bug 1949286] [NEW] [MIR]: Include dwarves-dfsg-hwe package into Bionic and Focal

[Rafael David Tinoco]

Public bug reported:

This is a follow-on request of bug:

HWE kernels should support eBPF CO-RE
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330

[Availability]

- Package is already available in all Ubuntu versions.
- This is a backported version (Impish) to Bionic and Focal

[Rationale]

- Current package dwarves-dfsg is old in Ubuntu Bionic and Focal.
- HWE kernel compilation needs recent "pahole" binary to encode BTF[1] 
information.
- After talking to SRU team members, updating dwarves-dfsg seemed risky.
- Creating a new package containing only the new "pahole" tool binary is the 
best option. 
- Kernel HWE compilations will need to use this package, so it has to be in 
main repository (as kernels builds depend on main only).

[Security]

- This package is already stable and exists in Ubuntu.


[Quality assurance]

- This package is already stable and exists in Ubuntu.

[Dependencies]

- Same dependencies as dwarves-dfsg package (already satisfied).

[Standards compliance]

- This package is already stable and exists in Ubuntu.

[Maintenance]

- SRUs for dwarves-dfsg package within Impish should be applied to this
package as well.

[Background information]

Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330
contains more information about why this is needed.

I have been maintaining BTFHUB (https://github.com/aquasecurity/btfhub)
in order to generate BTF files to each existing Ubuntu kernel but I feel
that a simple change, like adding a recent pahole tool to the main
archive in Bionic and Focal, is enough to resolve a VERY BIG problem for
eBPF applications to run in HWE kernels in those Ubuntu versions.

A very complete explanation on why BTF is needed for eBPF to be portable
among different kernels currently exists at:
https://github.com/aquasecurity/btfhub/tree/main/tools.

Projects that would already benefit from this change:

- Microsoft: Sysmon Tools for Linux
- Microsoft: Inspektor Gadge
- Elastic: They're working together with us upstream
- Aqua Security: libbpfgo & tracee-ebpf
- All BCC libbpf-tools

and many more.


[1] https://www.kernel.org/doc/html/latest/bpf/btf.html

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

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

** Affects: linux (Ubuntu Focal)
 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/1949286

Title:
  [MIR]: Include dwarves-dfsg-hwe package into Bionic and Focal

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New

Bug description:
  This is a follow-on request of bug:

  HWE kernels should support eBPF CO-RE
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330

  [Availability]

  - Package is already available in all Ubuntu versions.
  - This is a backported version (Impish) to Bionic and Focal

  [Rationale]

  - Current package dwarves-dfsg is old in Ubuntu Bionic and Focal.
  - HWE kernel compilation needs recent "pahole" binary to encode BTF[1] 
information.
  - After talking to SRU team members, updating dwarves-dfsg seemed risky.
  - Creating a new package containing only the new "pahole" tool binary is the 
best option. 
  - Kernel HWE compilations will need to use this package, so it has to be in 
main repository (as kernels builds depend on main only).

  [Security]

  - This package is already stable and exists in Ubuntu.

  
  [Quality assurance]

  - This package is already stable and exists in Ubuntu.

  [Dependencies]

  - Same dependencies as dwarves-dfsg package (already satisfied).

  [Standards compliance]

  - This package is already stable and exists in Ubuntu.

  [Maintenance]

  - SRUs for dwarves-dfsg package within Impish should be applied to
  this package as well.

  [Background information]

  Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330
  contains more information about why this is needed.

  I have been maintaining BTFHUB
  (https://github.com/aquasecurity/btfhub) in order to generate BTF
  files to each existing Ubuntu kernel but I feel that a simple change,
  like adding a recent pahole tool to the main archive in Bionic and
  Focal, is enough to resolve a VERY BIG problem for eBPF applications
  to run in HWE kernels in those Ubuntu versions.

  A very complete explanation on why BTF is needed for eBPF to be
  portable among different kernels currently exists at:
  https://github.com/aquasecurity/btfhub/tree/main/tools.

  Projects that would already benefit from this change:

  - Microsoft: Sysmon Tools for Linux
  - Microsoft: Inspektor Gadge
  - Elastic: They're working together with us upstream
  - Aqua Security: libbpfgo & tracee-ebpf
  - All BCC libbpf-tools

  and many more.

  
  [1] 

[Kernel-packages] [Bug 1926330] Re: HWE kernels should enable BTF support to enable eBPF CO-RE support

[Rafael David Tinoco]

** Summary changed:

- HWE kernels should enable BTF support to enable eBPF RO.CE support
+ HWE kernels should enable BTF support to enable eBPF CO-RE support

** Summary changed:

- HWE kernels should enable BTF support to enable eBPF CO-RE support
+ HWE kernels should support eBPF CO-RE

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

Title:
  HWE kernels should support eBPF CO-RE

Status in dwarves-dfsg package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in dwarves-dfsg source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Won't Fix
Status in dwarves-dfsg source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in dwarves-dfsg source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Fix Released

Bug description:
  I had recent discussion with kernel team regarding support or not BTF
  in HWE kernels (Bionic and Focal). Having CONFIG_DEBUG_INFO_BTF option
  enabled for HWE kernels (v4.4 and v.4.8) would allow eBPF based code
  (powered by libbpf or not) to be RO.CE
  (https://github.com/rafaeldtinoco/portablebpf for more information).

  By allowing runtime relocations, using provided BTF, libbpf binaries
  might end up running, without modifications, in different kernel
  versions (from Bionic HWE v5.4 kernel to Hirsute v5.11).

  A good example would be to support tools such as:
  
https://github.com/aquasecurity/tracee/discussions/713#discussioncomment-665641
  An ebpf powered backend for a containers security solution.

  Considering:

  $ rmadisonb dwarves
   dwarves | 1.9-1  | precise/universe | amd64
   dwarves | 1.10-2 | trusty   | amd64
   dwarves | 1.10-2.1   | xenial/universe  | amd64
   dwarves | 1.10-2.1build1 | bionic/universe  | amd64
   dwarves | 1.15-2 | focal/universe   | amd64
   dwarves | 1.17-1 | groovy/universe  | amd64
   dwarves | 1.20-1 | hirsute/universe | amd64
   dwarves | 1.20-1 | impish/universe  | amd64

  And the fact that the 'pahole' binary, from dwarves package, is the
  one to blame, not to have CONFIG_DEBUG_INFO_BTF available, for this
  bug to be solved we would have to provide a backport of dwarves (at
  least 1.17-1) to Bionic and Focal. It could have another name (not to
  mess with original dwarves package and its dependencies) and it is
  unclear if it needs to be in [main] or [universe].

  Question: Would have dwarves backported in -backports be enough for
  Bionic and Focal HWE kernels compilation to have CONFIG_DEBUG_INFO_BTF
  enabled ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1926330/+subscriptions


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