[Kernel-packages] [Bug 1948351] Re: linux ADT test_bpf failure with linux/5.4.0-90.101

[Po-Hsu Lin]

Manually tested on a P8 node (gulpin) with 5.4.0-89-generic and
5.4.0-90-generic

Conclusion:
It looks like a real kernel regression.
The following two test cases are failing with 5.4.0-90-generic (passed with 
5.4.0-89-generic)
[  736.795192] test_bpf: #142 ALU_MOD_K: 3 % 1 = 0 jited:1 ret 3 != 0 FAIL (1 
times)
[  736.795285] test_bpf: #145 ALU64_MOD_K: 3 % 1 = 0 jited:1 ret 3 != 0 FAIL (1 
times)

Test results:
* Kernel: 5.4.0-89 + Source: 5.4.0-89 = PASSED
* Kernel: 5.4.0-89 + Source: 5.4.0-90 = PASSED
* Kernel: 5.4.0-90 + Source: 5.4.0-90 = FAILED
* Kernel: 5.4.0-90 + Source: 5.4.0-89 = FAILED

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

Title:
  linux ADT test_bpf failure with linux/5.4.0-90.101

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  
  Consistently failing on Focal/linux 5.4.0-90.101

  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1

  
  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

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


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

[Kernel-packages] [Bug 1948377] Re: [linux-iot][F] USB: serial: pl2303: add support for PL2303HXN

[AaronMa]

** Tags added: austin oem-priority originate-from-1945148

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

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => In Progress

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

Title:
  [linux-iot][F] USB: serial: pl2303: add support for PL2303HXN

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  PL2303HXN is not supported by 5.4 kernel.
  5.5 kernel starts to support it.

  [Fix]
  Add support for PL2303HXN.

  [Test]
  Verified on hardware, use minicom to test serial port, it works fine.

  [Where problems could occur]
  It may break the pl2303 ttyUSBx.

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


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

[Kernel-packages] [Bug 1948377] 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 1948377

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

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

Title:
  [linux-iot][F] USB: serial: pl2303: add support for PL2303HXN

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  PL2303HXN is not supported by 5.4 kernel.
  5.5 kernel starts to support it.

  [Fix]
  Add support for PL2303HXN.

  [Test]
  Verified on hardware, use minicom to test serial port, it works fine.

  [Where problems could occur]
  It may break the pl2303 ttyUSBx.

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


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

[Kernel-packages] [Bug 1948377] [NEW] [linux-iot][F] USB: serial: pl2303: add support for PL2303HXN

[AaronMa]

Public bug reported:

[Impact]
PL2303HXN is not supported by 5.4 kernel.
5.5 kernel starts to support it.

[Fix]
Add support for PL2303HXN.

[Test]
Verified on hardware, use minicom to test serial port, it works fine.

[Where problems could occur]
It may break the pl2303 ttyUSBx.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: AaronMa (mapengyu)
 Status: In Progress

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress


** Tags: austin oem-priority originate-from-1945148

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

Title:
  [linux-iot][F] USB: serial: pl2303: add support for PL2303HXN

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  PL2303HXN is not supported by 5.4 kernel.
  5.5 kernel starts to support it.

  [Fix]
  Add support for PL2303HXN.

  [Test]
  Verified on hardware, use minicom to test serial port, it works fine.

  [Where problems could occur]
  It may break the pl2303 ttyUSBx.

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


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

[Kernel-packages] [Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system

[Yuan-Chen Cheng]

** Tags added: originate-from-1942484

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

Title:
  Fix A yellow screen pops up in an instant (< 1 second) and then
  disappears before loading the system

Status in HWE Next:
  New
Status in OEM Priority Project:
  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-oem-5.14 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-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  Fix Committed
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-oem-5.14 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
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  *** this issue happen with secure boot on and issue gone when secure boot is 
off***

  After the BIOS loading screen, a yellow screen pops up in an instant
  (< 1 second) and then disappears. Attached a demo video.

  [Fix]
  do what intel_color_commit() does to make sure the bottom color state
  matches whatever out hardware readout produced.
  Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171=1

  [Test]
  1. Power on the system
  2. Check if any unusual screen shows before and after the system loading 
screen.
  3. No unusual screen shows before and after the system loading screen

  [Regression Potential]
  Medium, maintainer still not totally sure what should do about color 
management
  features here in general.

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


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

[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
 Assignee: Po-Hsu Lin (cypressyew) => (unassigned)

** Changed in: ubuntu-kernel-tests
   Status: In Progress => 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/1836694

Title:
  memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed
Status in linux source package in Impish:
  Confirmed

Bug description:
  This failure could be found in the LTP test suite on a Moonshot ARM64
  node with B-4.15, but sometimes it will pass if you try to run it
  manually. (Sometimes not.)

  <<>>
  tag=memcg_test_3 stime=1563249678
  cmdline="memcg_test_3"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  Test timeouted, sending SIGKILL!
  tst_test.c:1140: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1141: BROK: Test killed! (timeout?)

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: 
unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: 
EPERM
  <<>>

  
  When it fails, the attempt to remove files will fail, and most of the 
cgroup_fj_* test will fail:
* cgroup_fj_function_memory
* cgroup_fj_stress_memory_10_3_each
* cgroup_fj_stress_memory_10_3_none
* cgroup_fj_stress_memory_10_3_one
* cgroup_fj_stress_memory_1_200_each
* cgroup_fj_stress_memory_1_200_none
* cgroup_fj_stress_memory_1_200_one
* cgroup_fj_stress_memory_200_1_each
* cgroup_fj_stress_memory_200_1_none
* cgroup_fj_stress_memory_200_1_one
* cgroup_fj_stress_memory_2_2_each
* cgroup_fj_stress_memory_2_2_none
* cgroup_fj_stress_memory_2_2_one
* cgroup_fj_stress_memory_2_9_each
* cgroup_fj_stress_memory_2_9_none
* cgroup_fj_stress_memory_2_9_one
* cgroup_fj_stress_memory_3_3_each
* cgroup_fj_stress_memory_3_3_none
* cgroup_fj_stress_memory_3_3_one
* cgroup_fj_stress_memory_4_4_each
* cgroup_fj_stress_memory_4_4_none
* cgroup_fj_stress_memory_4_4_one

  Steps to run this:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "memcg_test_3memcg_test_3" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 16 03:46 seq
   crw-rw 1 root audio 116, 33 Jul 16 03:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 16 04:16:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.173.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+subscriptions


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Mitsutoshi Yamamoto]

Hi,
 I tried to install Ubuntu 21.10 on my Lenovo ThinkPad E14 AMD Gen 2(AMD Ryzen 
5 4500U with Radeon Graphics) today but I got also kernel panic. (when entered 
in safe graphics mode)
 Here are the first few lines of error message:
[drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel
Kernel panic - not syncing: stack-protector: Kernet stack is corrupted in: 
elantech_change_report_id+0x1bf/0x1c4 [psmouse]
CPU: 4 PID: 123 Comm: kworker/4:1 Not tainted 5.13.0-19-generic #19-Ubuntu
Hardware name: LENOVO 20T60022US/20T60022US, BIOS R1AET34W (1.10) 12/19/2020
Workqueue: events_long serio_handle_event
Call Trace:
...
...
...
---[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted 
in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]---

Please fix this ASAP!!!

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro 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.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Mitsutoshi Yamamoto]

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro 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.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1948349] Re: Ubuntu 21.10 Kernel Panic error.. Unable to boot from Live USB installer

[moxzie hook]

How can I run the terminal when the device is unable to boot in the first 
place..?
I don't know how to run the above mentioned command as the problem appears in 
the first few minutes of the boot process..
Help

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

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

Title:
  Ubuntu 21.10 Kernel Panic error.. Unable to boot from Live USB
  installer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I tried to install Ubuntu 21.10 stable which was released couple of days ago.
  I get Kernel panic error on both my ThinkPad and Thinkcenter when trying to 
boot from the Live usb installer.
  My ThinkPad x201 processor is Intel 1stGen.
  My Thinkcenter m93p runs on Intel Core i5- 4430s.
  I have tried to disable the track point and touchpad from BIOS but with no 
luck.
  I tried acpi=off from the unetbootin boot menu and kernel panic doesn't 
appear but another problem "unable to find a medium containing a live file 
system" popped up. I don't know how to go past this.
  Any help will be appreciated. Thanks

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


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

[Kernel-packages] [Bug 1936842] Re: agent cannot be up on LXD/Fan network on OpenStack OVN/geneve mtu=1442

[Canonical Juju QA Bot]

** Changed in: juju
Milestone: 2.9.17 => 2.9.18

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

Title:
  agent cannot be up on LXD/Fan network on OpenStack OVN/geneve mtu=1442

Status in juju:
  In Progress
Status in ubuntu-fan package in Ubuntu:
  New

Bug description:
  When one runs OpenStack with MTU=1500 underlying network, Neutron/OVN
  by default will create a tenant/overlay network with
  MTU=1442(1500-58). However, when deploying a workload on top, the Fan
  network with Juju will use MTU=1450 which is actually bigger than
  that. Then, Juju agent cannot be up inside LXD/Fan on top of
  OpenStack.

  
  OpenStack deployment is based on https://jaas.ai/openstack-base
  and k8s as a workload on top of OpenStack is: https://jaas.ai/kubernetes-core

  
  $ openstack network list
  
+--+--+--+
  | ID   | Name | Subnets   
   |
  
+--+--+--+
  | ba9880e3-5f07-4b49-aeda-20dfa8fe66ec | internal | 
45efcc4c-fb99-4fe8-98a4-77195ec4aef1 |
  | e27b1cef-c53b-42e0-b307-8ba2e622c2dd | ext_net  | 
5315d907-ce90-4605-ad72-b78229965b40 |
  
+--+--+--+

  $ openstack network show internal 
  +---+--+
  | Field | Value|
  +---+--+
  ...
  | mtu   | 1442 |
  | name  | internal |
  ...
  | provider:network_type | geneve   |
  | provider:physical_network | None |
  | provider:segmentation_id  | 1410 |
  ...
  +---+--+

  $ juju machines -m k8s-on-openstack
  Machine  StateDNS Inst id   
Series  AZMessage
  0started  192.168.151.75  0e96a5b1-3665-44f6-bcb7-4851ab6cd22d  focal 
  nova  ACTIVE
  0/lxd/0  pending  juju-b9bd8b-0-lxd-0   focal 
  nova  Container started
  1started  192.168.151.66  6bfa5d2e-24e6-42b8-b5ec-1f2a0d0e6b02  focal 
  nova  ACTIVE

  
  [openstack instance/VM provisioned by Juju - ens3: mtu=1442, fan-252: 
mtu=1450]

  juju-b9bd8b-k8s-on-openstack-0:~# ip link
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1442 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether fa:16:3e:48:85:85 brd ff:ff:ff:ff:ff:ff
  3: fan-252:  mtu 1450 qdisc noqueue state UP 
mode DEFAULT group default qlen 1000
  link/ether 06:28:c7:b4:50:eb brd ff:ff:ff:ff:ff:ff
  4: ftun0:  mtu 1392 qdisc noqueue master 
fan-252 state UNKNOWN mode DEFAULT group default qlen 1000
  link/ether 92:d7:07:6e:b4:db brd ff:ff:ff:ff:ff:ff
  5: lxdbr0:  mtu 1500 qdisc noqueue state 
DOWN mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:03:0e:96 brd ff:ff:ff:ff:ff:ff
  7: 0lxd0-0@if6:  mtu 1450 qdisc noqueue 
master fan-252 state UP mode DEFAULT group default qlen 1000
  link/ether 06:28:c7:b4:50:eb brd ff:ff:ff:ff:ff:ff link-netnsid 0

  
  [lxc config of LXD container as juju machine 0/lxd/0]

  juju-b9bd8b-k8s-on-openstack-0:~# lxc config show juju-b9bd8b-0-lxd-0
  ...
user.user-data: |
  #cloud-config
  apt_mirror: ""
  bootcmd:
  - install -D -m 644 /dev/null '/etc/netplan/99-juju.yaml'
  - |-
printf '%s\n' 'network:
  version: 2
  ethernets:
eth0:
  match:
macaddress: 00:16:3e:82:f9:44
  dhcp4: true
  nameservers:
search: [openstack.internal]
addresses: [8.8.8.8, 8.8.4.4]
  mtu: 1450
  ...
  devices:
eth0:
  host_name: 0lxd0-0
  hwaddr: 00:16:3e:82:f9:44
  mtu: "1450"
  name: eth0
  nictype: bridged
  parent: fan-252
  type: nic

  
  [cloud-init-output.log - stuck at the initial apt update and also failing to 
fetch the agent binary]

  Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~20.04.1 running 'modules:config' at 
Mon, 19 Jul 2021 03:27:32 +. Up 53.99 seconds.
  Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Err:2 http://security.ubuntu.com/ubuntu focal-security InRelease
Connection failed [IP: 192.168.151.1 8000]
  Err:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Connection failed [IP: 192.168.151.1 8000]
  Err:4 

[Kernel-packages] [Bug 1944080] Re: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error

[Canonical Juju QA Bot]

** Changed in: juju
Milestone: 2.9.17 => 2.9.18

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

Title:
  [fan-network] Race-condition between "apt update" and dhcp request
  causes cloud-init error

Status in OpenStack rabbitmq-server charm:
  New
Status in juju:
  In Progress
Status in ubuntu-fan package in Ubuntu:
  New

Bug description:
  Hi,

  Using manual provider on top of VMWare.

  Juju: 2.9.14
  VM: Focal
  Containers: Bionic

  I've noticed that, in a given Focal host, 2x Bionic containers may
  have different behavior: one successfully completes cloud-init whereas
  the other fails. The failed container errors at "apt update" in cloud-
  init with:

  Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Something wicked happened resolving 'PROXY_IP:' (-9 - Address family 
for hostname not supported)
  (Likely this is the line where it breaks: 
https://github.com/Debian/apt/blob/766b24b7f7484751950c76bc66d3d6cdeaf949a5/methods/connect.cc#L436)

  Failed container, full cloud-init-output.log: 
https://pastebin.canonical.com/p/hKNw49mvJP/
  Successful container, full cloud-init-output.log: 
https://pastebin.canonical.com/p/P6MZdQPrWd/
  Host syslog: https://pastebin.canonical.com/p/jjMmWRFd9y/

  I can see that, on the host, dnsmasq served the FAN IP to the broken
  container after the "apt-update" was called.

  - FAILED CONTAINER -:
  Sep 19 13:02:14 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 
252.252.15.198 00:16:3e:da:dd:c4 
  apt-update on cloud-init was ran:
  Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at 
Sun, 19 Sep 2021 13:02:13 +. Up 3.90 seconds.

  
  - SUCCESSFUL CONTAINER -:
  Sep 19 13:09:40 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 
252.252.15.253 00:16:3e:d7:6b:ef 
  apt-update on cloud-init was ran:
  Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at 
Sun, 19 Sep 2021 13:10:10 +. Up 35.99 seconds.

  In the case of the Failed Container, the DHCPOFFER arrived 1s after
  the "apt update" was requested, whereas the Successful Container
  logged a DHCPOFFER 30s before the "apt update".

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1944080/+subscriptions


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

[Kernel-packages] [Bug 1948005] Re: Dell 6000 dock freeze and restart since october 19.

[Daniel van Vugt]

** Summary changed:

- Dell 6000 freeze and restart since october 19.
+ Dell 6000 dock freeze and restart since october 19.

** Package changed: xorg (Ubuntu) => linux-oem-5.10 (Ubuntu)

** Tags added: regression-update

** Tags added: displaylink evdi

** Summary changed:

- Dell 6000 dock freeze and restart since october 19.
+ Dell 6000 dock freeze and restart since October 19.

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

Title:
  Dell 6000 dock freeze and restart since October 19.

Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  Ramdomly my external display (conected via HDMI over a dell 6000
  displaylink port) stop working, gone black, and then restart.

  Buy I notice that all devices conected to dell 6000 stop working.

  It happens since october 19 ubuntu auto update.

  I need this continue working as it was before that update.

  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 08:16:15 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.9.1, 5.10.0-1049-oem, x86_64: installed
   evdi, 1.9.1, 5.10.0-1050-oem, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0a29]
  InstallationDate: Installed on 2021-08-18 (63 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2021
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd05/31/2021:br1.6:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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-oem-5.10/+bug/1948005/+subscriptions


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

[Kernel-packages] [Bug 1948005] [NEW] Dell 6000 dock freeze and restart since october 19.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ramdomly my external display (conected via HDMI over a dell 6000
displaylink port) stop working, gone black, and then restart.

Buy I notice that all devices conected to dell 6000 stop working.

It happens since october 19 ubuntu auto update.

I need this continue working as it was before that update.

Description:Ubuntu 20.04.3 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
Uname: Linux 5.10.0-1050-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 21 08:16:15 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 evdi, 1.9.1, 5.10.0-1049-oem, x86_64: installed
 evdi, 1.9.1, 5.10.0-1050-oem, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0a29]
InstallationDate: Installed on 2021-08-18 (63 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Dell Inc. Vostro 3401
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2021
dmi.bios.release: 1.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.0
dmi.board.name: 0790WT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd05/31/2021:br1.6:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 3401
dmi.product.sku: 0A29
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
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

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


** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu
-- 
Dell 6000 dock freeze and restart since october 19.
https://bugs.launchpad.net/bugs/1948005
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-oem-5.10 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 1948351] 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 1948351

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

Title:
  linux ADT test_bpf failure with linux/5.4.0-90.101

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  
  Consistently failing on Focal/linux 5.4.0-90.101

  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1

  
  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

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


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

[Kernel-packages] [Bug 1929889] Re: [TGL][ADL] Enable CET(Control-flow Enforcement Technology)

[Anthony Wong]

** Tags removed: verification-done-focal
** Tags added: verification-failed-focal

** Changed in: linux-intel (Ubuntu Focal)
 Assignee: Alex Hung (alexhung) => (unassigned)

** Changed in: linux-intel (Ubuntu)
 Assignee: Alex Hung (alexhung) => (unassigned)

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

Title:
  [TGL][ADL] Enable CET(Control-flow Enforcement Technology)

Status in intel:
  New
Status in linux-intel package in Ubuntu:
  Triaged
Status in linux-intel source package in Focal:
  New

Bug description:
  Description
  Enable Tiger Lake ROP CET(Control-flow Enforcement Technology)
  An upcoming Intel® processor family feature that counters 
return/jump-oriented programming (ROP) attacks

  Hardware: Tiger Lake & Alder 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/1929889/+subscriptions


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

[Kernel-packages] [Bug 1948351] [NEW] linux ADT test_bpf failure with linux/5.4.0-90.101

[Kelsey Skunberg]

Public bug reported:

This is a scripted bug report about ADT failures while running linux
tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.


Consistently failing on Focal/linux 5.4.0-90.101

13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1


Testing failed on:
ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

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


** Tags: focal kernel-adt-failure

** Tags added: kernel-adt-failure

** Tags added: focal

** Description changed:

  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be determined.
  
+ 
+ Consistently failing on Focal/linux 5.4.0-90.101
+ 
+ 13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
+ 13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
+ 13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1
+ 
+ 
  Testing failed on:
- ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz
+ ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

** Summary changed:

- linux ADT test failure with linux/5.4.0-90.101
+ linux ADT test_bpf failure with linux/5.4.0-90.101

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

Title:
  linux ADT test_bpf failure with linux/5.4.0-90.101

Status in linux package in Ubuntu:
  New

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  
  Consistently failing on Focal/linux 5.4.0-90.101

  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1

  
  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

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


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

[Kernel-packages] [Bug 1948343] 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 1948343

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  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/1948343/+subscriptions


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

[Kernel-packages] [Bug 1948349] 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 1948349

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

** Tags added: impish

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

Title:
  Ubuntu 21.10 Kernel Panic error.. Unable to boot from Live USB
  installer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I tried to install Ubuntu 21.10 stable which was released couple of days ago.
  I get Kernel panic error on both my ThinkPad and Thinkcenter when trying to 
boot from the Live usb installer.
  My ThinkPad x201 processor is Intel 1stGen.
  My Thinkcenter m93p runs on Intel Core i5- 4430s.
  I have tried to disable the track point and touchpad from BIOS but with no 
luck.
  I tried acpi=off from the unetbootin boot menu and kernel panic doesn't 
appear but another problem "unable to find a medium containing a live file 
system" popped up. I don't know how to go past this.
  Any help will be appreciated. Thanks

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


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

[Kernel-packages] [Bug 1948349] Re: Ubuntu 21.10 Kernel Panic error.. Unable to boot from Live USB installer

[moxzie hook]

Ubuntu 21.10 Kernel Panic

** Attachment added: "Here the screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948349/+attachment/5534977/+files/DSC02963_1.JPG

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

Title:
  Ubuntu 21.10 Kernel Panic error.. Unable to boot from Live USB
  installer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I tried to install Ubuntu 21.10 stable which was released couple of days ago.
  I get Kernel panic error on both my ThinkPad and Thinkcenter when trying to 
boot from the Live usb installer.
  My ThinkPad x201 processor is Intel 1stGen.
  My Thinkcenter m93p runs on Intel Core i5- 4430s.
  I have tried to disable the track point and touchpad from BIOS but with no 
luck.
  I tried acpi=off from the unetbootin boot menu and kernel panic doesn't 
appear but another problem "unable to find a medium containing a live file 
system" popped up. I don't know how to go past this.
  Any help will be appreciated. Thanks

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


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

[Kernel-packages] [Bug 1948349] [NEW] Ubuntu 21.10 Kernel Panic error.. Unable to boot from Live USB installer

[moxzie hook]

Public bug reported:

I tried to install Ubuntu 21.10 stable which was released couple of days ago.
I get Kernel panic error on both my ThinkPad and Thinkcenter when trying to 
boot from the Live usb installer.
My ThinkPad x201 processor is Intel 1stGen.
My Thinkcenter m93p runs on Intel Core i5- 4430s.
I have tried to disable the track point and touchpad from BIOS but with no luck.
I tried acpi=off from the unetbootin boot menu and kernel panic doesn't appear 
but another problem "unable to find a medium containing a live file system" 
popped up. I don't know how to go past this.
Any help will be appreciated. Thanks

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

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

Title:
  Ubuntu 21.10 Kernel Panic error.. Unable to boot from Live USB
  installer

Status in linux package in Ubuntu:
  New

Bug description:
  I tried to install Ubuntu 21.10 stable which was released couple of days ago.
  I get Kernel panic error on both my ThinkPad and Thinkcenter when trying to 
boot from the Live usb installer.
  My ThinkPad x201 processor is Intel 1stGen.
  My Thinkcenter m93p runs on Intel Core i5- 4430s.
  I have tried to disable the track point and touchpad from BIOS but with no 
luck.
  I tried acpi=off from the unetbootin boot menu and kernel panic doesn't 
appear but another problem "unable to find a medium containing a live file 
system" popped up. I don't know how to go past this.
  Any help will be appreciated. Thanks

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[moxzie hook]

I tried to install Ubuntu 21.10 stable which was released couple of days ago.
I get Kernel panic error on both my ThinkPad and Thinkcenter when trying to 
boot from the Live usb installer.
My ThinkPad x201 processor is Intel 1stGen.
My Thinkcenter m93p runs on Intel Core i5- 4430s.
I have tried to disable the track point and touchpad from BIOS but with no luck.
I tried acpi=off from the unetbootin boot menu and kernel panic doesn't appear 
but another problem "unable to find a medium containing a live file system" 
popped up. I don't know how to go past this.
Any help will be appreciated. Thanks

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro 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.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1875756] Re: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Wi-Fi not enabled

[Craig McQueen]

I've never had this in Ubuntu 21.04 Hirsute. But after upgrading to
Ubuntu 21.10 Impish, I had it boot up without WiFi.

In 21.04 Hirsute, here is an example good boot from /var/log/syslog:

Oct 21 15:03:08 nary kernel: [2.596955] ath10k_pci :02:00.0: enabling 
device ( -> 0002)
Oct 21 15:03:08 nary kernel: [2.599059] ath10k_pci :02:00.0: pci irq 
msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Oct 21 15:03:08 nary kernel: [2.880904] ath10k_pci :02:00.0: qca9377 
hw1.1 target 0x05020001 chip_id 0x003821ff sub 17aa:0901
Oct 21 15:03:08 nary kernel: [2.880913] ath10k_pci :02:00.0: kconfig 
debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
Oct 21 15:03:08 nary kernel: [2.881690] ath10k_pci :02:00.0: firmware 
ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877
Oct 21 15:03:08 nary kernel: [2.945483] ath10k_pci :02:00.0: board_file 
api 2 bmi_id N/A crc32 8aedfa4a
Oct 21 15:03:08 nary kernel: [3.131331] ath10k_pci :02:00.0: htt-ver 
3.56 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Oct 21 15:03:09 nary kernel: [3.222767] ath10k_pci :02:00.0 wlp2s0: 
renamed from wlan0
Oct 21 15:03:09 nary NetworkManager[673]:   [1634788989.1422] rfkill2: 
found Wi-Fi radio killswitch (at 
/sys/devices/pci:00/:00:1d.6/:02:00.0/ieee80211/phy0/rfkill2) 
(driver ath10k_pci)

In 21.10 Impish, here is a bad boot:

Oct 22 07:49:16 nary kernel: [2.444721] ath10k_pci :02:00.0: enabling 
device ( -> 0002)
Oct 22 07:49:16 nary kernel: [2.447680] ath10k_pci :02:00.0: pci irq 
msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Oct 22 07:49:16 nary kernel: [2.740342] ath10k_pci :02:00.0: qca9377 
hw1.1 target 0x05020001 chip_id 0x003821ff sub 17aa:0901
Oct 22 07:49:16 nary kernel: [2.740348] ath10k_pci :02:00.0: kconfig 
debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
Oct 22 07:49:16 nary kernel: [2.741071] ath10k_pci :02:00.0: firmware 
ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877
Oct 22 07:49:16 nary kernel: [2.804728] ath10k_pci :02:00.0: board_file 
api 2 bmi_id N/A crc32 8aedfa4a
Oct 22 07:49:21 nary kernel: [7.967436] ath10k_pci :02:00.0: wmi 
service ready event not received
Oct 22 07:49:21 nary kernel: [8.047727] ath10k_pci :02:00.0: could not 
init core (-110)
Oct 22 07:49:21 nary kernel: [8.047774] ath10k_pci :02:00.0: could not 
probe fw (-110)


But, I rebooted it, and WiFi came back after the boot. It remains to be seen 
how often this issue appears in Ubuntu 21.10 Impish.

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

Title:
  Qualcomm Atheros QCA9377  [168c:0042] Subsystem [1028:1810] Wi-Fi not
  enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  None of the Wi-Fi devices were used or even seen by Ubuntu when I
  booted it up, forcing me to reboot.

  I saved this apport file before I rebooted however.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 28 16:35:30 2020
  InstallationDate: Installed on 2020-04-26 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp1s0no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d6d3e13f-ad59-49e9-a5c7-055147c9065b 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.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: 

[Kernel-packages] [Bug 1948343] Re: Docking Station crash ramdomly after october 19 updates

[Chris Guiver]

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

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

FYI: You've filed this against the `ubuntu-release-upgrader` package,
which would upgrade a 20.04 install to a later release (eg. 20.10, 22.04
etc) for example; yet you appear to have not used that feature; thus
I'll change this to `linux`.

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  New

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  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/1948343/+subscriptions


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

[Kernel-packages] [Bug 1948343] [NEW] Docking Station crash ramdomly after october 19 updates

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

My dell D6000 dockingstation start crashing after installation of
updates on october 19.

Now, randomly the external HDMI monitor goes blank for 5 second until
dock restart. But this fails make external webcam (connected to
dockstation), and bluetooth headphones (mic at external web cam) got
unconfigured, sending audio to the dock port and getting mic from it not
regarding is not used, putting in a meeting without any sound.

And because internet is also used via D6000 wired ethernet port, I got
disconnected from VPN and RDP connections too.

Release info:
Description:Ubuntu 20.04.3 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.36
ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
Uname: Linux 5.10.0-1050-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 21 18:00:54 2021
InstallationDate: Installed on 2021-08-18 (64 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
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 focal
-- 
Docking Station crash ramdomly after october 19 updates
https://bugs.launchpad.net/bugs/1948343
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 1947853] Re: ubuntu20.04 crash

[Seth Arnold]

** Information type changed from Public Security to Public

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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

[Kernel-packages] [Bug 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter

[Alex Hung]

** Changed in: linux (Ubuntu)
 Assignee: Alex Hung (alexhung) => (unassigned)

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

Title:
  AMD-Vi: Unable to read/write to IOMMU perf counter

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This boot warning (concealed by grub not taking over the fbcon console
  on a solo installation but always present on a multi-boot) has been
  bothering Linux users of AMD Ryzen machines for some time.

  The problem is currently under discussion at kernel level
  .

  One solution proposed by Suravee Suthikulpanit

  works but inserts a boot-up delay of (at least) 100 msec. A second
  option by Alexander Monakov 
   also works but
  inserts no delay and more-or-less just moves one line of code.

  I've tried both solutions with kernel rebuilds for both Breezy kernel
  5.8.18 and Hirsute kernel 5.10.11 and both work on my AMD Ryzen 2400G.
  Could I encourage your kernel experts to evaluate the situation (I
  think SuSE folk already are).

  My suggestion (as a humble user :-) ) would be to fold Alex's simple
  patch into your own list of kernel tweeks and get the correction out
  with the upcoming Hirsute release.

  Best regards and all respect!

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


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

[Kernel-packages] [Bug 1943185] Re: Fix AMD GPIO-based power button

[Alex Hung]

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

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

Title:
   Fix AMD GPIO-based power button

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released

Bug description:
  [Impact]

   Power button or other wake up sources connected to GPIO may not wake
  up idle AMD systems.

  [Fix]

   Enable and disable power management wakeup mode, which is disabled by
  default, accordingly.

   The patch series can be found @ https://lore.kernel.org/linux-
  gpio/20210831120613.1514899-1-basavaraj.nati...@amd.com/

  [Test]

   This is requested by AMD.

  [Where problems could occur]

   Only AMD systems that require GPIOs as wake sources will be affected,
  i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended
  behaviour.

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


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

[Kernel-packages] [Bug 1912033] Re: Thinkpad - add palm sensor support needed for WWAN

[Alex Hung]

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

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

Title:
  Thinkpad - add palm sensor support needed for WWAN

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released

Bug description:
  [Impact]
    Add new palm sensor supports to Lenovo Thinkpad systems

  [Fix]
    thinkpad_acpi is updated to check palm sensor presence and its events

  [Test]
    Tested on Thinkpad systems

  [Where problems could occur]
    Low risks. Only thinkpad systems are affected. Also thinkpad systems 
without palm sensor and without TP_HKEY_EV_PALM_DETECTED & 
TP_HKEY_EV_PALM_UNDETECTED events won't be affected either.

    There can an issue as discussed in commit log of "thinkpad_acpi: Add
  palm sensor support"

  Note: On some platforms, because of an issue in the HW implementation,
  the palm sensor presence may be incorrectly advertised as always
  enabled even if a palm sensor is not present. The palm sensor is
  intended for WWAN transmission power control and should be available
  and correct on all WWAN enabled systems. It is not recommended to use
  this interface for other use cases.

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


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

[Kernel-packages] [Bug 1948057] [NEW] linux-azure-cvm: Create a 5.4 based kernel

[Marcelo Cerri]

Public bug reported:

linux-azure-cvm: Create a 5.4 based kernel

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: In Progress

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

Title:
  linux-azure-cvm: Create a 5.4 based kernel

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  linux-azure-cvm: Create a 5.4 based kernel

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


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

[Kernel-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

[Alekk]

still experiencing this issue with plasma 5.23.1 and kernel 5.14.0 on
amd 2500U cpu. switching "EnablePageFlip" on/off doesn't help.

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 

[Kernel-packages] [Bug 1948011] Re: SDDM shows a black screen when nvidia-driver-470 is updated to 470.74

[Karsten]

Disabling G-SYNC on G-SYNC compatible monitor fixed this issue.

Refer to:
https://dev.getsol.us/R2210:8889aa630ca826262f1c3d28f4e208e6f314294b

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

Title:
  SDDM shows a black screen when nvidia-driver-470 is updated to 470.74

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

Bug description:
  This bug is encountered on a computer with:

  Kubuntu 21.10
  MSI Gaming X Trio 3060 Ti

  The following repo is used:

  ppa: kubuntu-backports

  GPU driver:

  Nvidia driver metapackage from nvidia-driver-470(proprietary, tested)

  What I expected: SDDM working just fine, showing every elements
  What happened: SDDM is showing a black screen on login, logout, lockscreen. 
BUT logging in works.
  What I did: Updating nvidia-driver-470 from 470.63 to 470.74
  What I tried to do to fix: dpkg-reconfigure sddm

  I suspect something is conflicting SDDM with the 470.74 driver.
  Downgrading to 470.63 will fix this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nvidia-driver-470 470.74-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 21 20:19:55 2021
  InstallationDate: Installed on 2021-08-24 (58 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-470
  UpgradeStatus: Upgraded to impish on 2021-10-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1948011/+subscriptions


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

[Kernel-packages] [Bug 1947601] Re: Cannot start docker container on ubuntu 21.10 server for raspberry pi

[ianmacs]

I understand the motivation. Reducing boot time by reducing the number
of kernel modules is something I can understand.

However, the original problem is not solved. I had to invest >10 hours
of trying to get docker containers to work with ubuntu 21.10 on
Raspberry Pi.

Why was a solution for running docker containers not mentioned in the Ubuntu 
21.10 release notes?
Why have you, Dave, not immediately told me of the solution (install 
modules-extra!) as soon as you saw this bug report?
Why has the docker.io package not added a dependency on the modules-extra 
package? It clearly does not work without this package on raspi.
Why was the veth kernel module moved to modules-extra? You are talking about 
19MB space savings of compressed initrd, but this module is only 25k, 
uncompressed! And on ubuntu servers, Docker certainly is one of the main use 
cases.

I feel that there needs to be a fix other from invalidating my >10 hours
of my work by invalidating this bug report.

Coming back to boot time savings: IMO that's a thing for desktops. But
for servers? I mean, servers are meant to run uninterrupted until there
is a kernel update. A few seconds more per reboot therefore does not eat
away from the uptime. Your server images, therefore, should have
modules-extra installed by default.

We use ubuntu instead of raspi-os on our ARM build servers because we
need to run Docker for ARM 32 and 64 bits. Please find another solution
for this cannot-run-docker out of the box for your server image than
letting all your users in the dark about why they cannot run docker
anymore in 21.10.

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

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

Title:
  Cannot start docker container on ubuntu 21.10 server for raspberry pi

Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Using the Ubuntu image for Raspberry Pi from here:
  https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-
  server-arm64+raspi.img.xz

  After installing the docker.io package, I cannot start a docker
  container. Example:

  $ sudo docker run --rm hello-world
  docker: Error response from daemon: failed to create endpoint pensive_greider 
on network bridge: failed to add the host (veth2102512) <=> sandbox 
(veth4fb66df) pair interfaces: operation not supported.

  This was working in the previous ubuntu release for 64 bit raspberry
  pi, 21.04.

  This problem is caused by the linux kernel shipped for ubuntu 21.10
  for 64 bit raspberry pi, see post #14.

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


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

[Kernel-packages] [Bug 1948038] 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 1948038

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

Title:
  disable CONFIG_KFENCE_STATIC_KEYS in linux 5.15

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  [Impact]

  KFENCE devs are changing CONFIG_KFENCE_STATIC_KEYS to be disabled by
  default, because it's introducing more problems than benefits:

  https://lore.kernel.org/all/20211019102524.2807208-2-el...@google.com/T/#u

  This also seems to trigger QEMU bugs during the systemd autopkgtest, like:
  https://bugs.launchpad.net/qemu/+bug/1920934

  [Test case]

  Run systemd autopkgtest.

  [Fix]

  Disable CONFIG_KFENCE_STATIC_KEYS.

  [Regression potential]

  We may experience an overall performance regression for not using
  static branches in the KFENCE code.

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


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

[Kernel-packages] [Bug 1948040] 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 1948040

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

** Tags added: focal

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

Title:
  modprobe.d is not honored on uc20

Status in snapd:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu kernels by default ship modprobe.d that excludes many modules
  from loading:

  # Kernel supplied blacklist for linux 5.4.0-89-generic amd64
  # modprobe.d/common.conf
  # LP:1434842 -- disable OSS drivers by default to allow pulseaudio to emulate
  blacklist snd-mixer-oss
  blacklist snd-pcm-oss
  # Autogenerated watchdog blacklist
  blacklist acquirewdt
  blacklist advantechwdt
  blacklist ahc1ec0-wdt
  blacklist alim1535_wdt
  blacklist alim7101_wdt
  blacklist cadence_wdt
  blacklist cpu5wdt
  blacklist da9052_wdt
  blacklist da9055_wdt
  blacklist da9062_wdt
  blacklist da9063_wdt
  blacklist dw_wdt
  blacklist ebc-c384_wdt
  blacklist eurotechwdt
  blacklist f71808e_wdt
  blacklist hpwdt
  blacklist i6300esb
  blacklist iTCO_vendor_support
  blacklist iTCO_wdt
  blacklist ib700wdt
  blacklist ibmasr
  blacklist ie6xx_wdt
  blacklist it8712f_wdt
  blacklist it87_wdt
  blacklist kempld_wdt
  blacklist machzwd
  blacklist max63xx_wdt
  blacklist mei_wdt
  blacklist mena21_wdt
  blacklist menf21bmc_wdt
  blacklist menz69_wdt
  blacklist mlx_wdt
  blacklist ni903x_wdt
  blacklist nic7018_wdt
  blacklist nv_tco
  blacklist of_xilinx_wdt
  blacklist pc87413_wdt
  blacklist pcwd_pci
  blacklist pcwd_usb
  blacklist pretimeout_panic
  blacklist rave-sp-wdt
  blacklist retu_wdt
  blacklist sbc60xxwdt
  blacklist sbc_epx_c3
  blacklist sbc_fitpc2_wdt
  blacklist sc1200wdt
  blacklist sch311x_wdt
  blacklist smsc37b787_wdt
  blacklist softdog
  blacklist sp5100_tco
  blacklist tqmx86_wdt
  blacklist twl4030_wdt
  blacklist via_wdt
  blacklist w83627hf_wdt
  blacklist w83877f_wdt
  blacklist w83977f_wdt
  blacklist wafer5823wdt
  blacklist wdat_wdt
  blacklist wdt_pci
  blacklist wm831x_wdt
  blacklist wm8350_wdt
  blacklist xen_wdt
  blacklist ziirave_wdt

  However kernel snaps do not provide modprobe.d nor they are used by
  default. Is pc-kernel supposed to skip shipping those? Should there be
  modprobe.d in the core20 snap that prevents these known modules from
  loading by default?

  Also I'm not too sure about the watchdog modules exclusion, given that
  systemd can operate watchdogs by default, hence it shouldn't be too
  dangerous to autoenable them?

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


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

[Kernel-packages] [Bug 1948040] [NEW] modprobe.d is not honored on uc20

[Dimitri John Ledkov]

Public bug reported:

Ubuntu kernels by default ship modprobe.d that excludes many modules
from loading:

# Kernel supplied blacklist for linux 5.4.0-89-generic amd64
# modprobe.d/common.conf
# LP:1434842 -- disable OSS drivers by default to allow pulseaudio to emulate
blacklist snd-mixer-oss
blacklist snd-pcm-oss
# Autogenerated watchdog blacklist
blacklist acquirewdt
blacklist advantechwdt
blacklist ahc1ec0-wdt
blacklist alim1535_wdt
blacklist alim7101_wdt
blacklist cadence_wdt
blacklist cpu5wdt
blacklist da9052_wdt
blacklist da9055_wdt
blacklist da9062_wdt
blacklist da9063_wdt
blacklist dw_wdt
blacklist ebc-c384_wdt
blacklist eurotechwdt
blacklist f71808e_wdt
blacklist hpwdt
blacklist i6300esb
blacklist iTCO_vendor_support
blacklist iTCO_wdt
blacklist ib700wdt
blacklist ibmasr
blacklist ie6xx_wdt
blacklist it8712f_wdt
blacklist it87_wdt
blacklist kempld_wdt
blacklist machzwd
blacklist max63xx_wdt
blacklist mei_wdt
blacklist mena21_wdt
blacklist menf21bmc_wdt
blacklist menz69_wdt
blacklist mlx_wdt
blacklist ni903x_wdt
blacklist nic7018_wdt
blacklist nv_tco
blacklist of_xilinx_wdt
blacklist pc87413_wdt
blacklist pcwd_pci
blacklist pcwd_usb
blacklist pretimeout_panic
blacklist rave-sp-wdt
blacklist retu_wdt
blacklist sbc60xxwdt
blacklist sbc_epx_c3
blacklist sbc_fitpc2_wdt
blacklist sc1200wdt
blacklist sch311x_wdt
blacklist smsc37b787_wdt
blacklist softdog
blacklist sp5100_tco
blacklist tqmx86_wdt
blacklist twl4030_wdt
blacklist via_wdt
blacklist w83627hf_wdt
blacklist w83877f_wdt
blacklist w83977f_wdt
blacklist wafer5823wdt
blacklist wdat_wdt
blacklist wdt_pci
blacklist wm831x_wdt
blacklist wm8350_wdt
blacklist xen_wdt
blacklist ziirave_wdt

However kernel snaps do not provide modprobe.d nor they are used by
default. Is pc-kernel supposed to skip shipping those? Should there be
modprobe.d in the core20 snap that prevents these known modules from
loading by default?

Also I'm not too sure about the watchdog modules exclusion, given that
systemd can operate watchdogs by default, hence it shouldn't be too
dangerous to autoenable them?

** Affects: snapd
 Importance: Undecided
 Status: New

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

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

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

Title:
  modprobe.d is not honored on uc20

Status in snapd:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu kernels by default ship modprobe.d that excludes many modules
  from loading:

  # Kernel supplied blacklist for linux 5.4.0-89-generic amd64
  # modprobe.d/common.conf
  # LP:1434842 -- disable OSS drivers by default to allow pulseaudio to emulate
  blacklist snd-mixer-oss
  blacklist snd-pcm-oss
  # Autogenerated watchdog blacklist
  blacklist acquirewdt
  blacklist advantechwdt
  blacklist ahc1ec0-wdt
  blacklist alim1535_wdt
  blacklist alim7101_wdt
  blacklist cadence_wdt
  blacklist cpu5wdt
  blacklist da9052_wdt
  blacklist da9055_wdt
  blacklist da9062_wdt
  blacklist da9063_wdt
  blacklist dw_wdt
  blacklist ebc-c384_wdt
  blacklist eurotechwdt
  blacklist f71808e_wdt
  blacklist hpwdt
  blacklist i6300esb
  blacklist iTCO_vendor_support
  blacklist iTCO_wdt
  blacklist ib700wdt
  blacklist ibmasr
  blacklist ie6xx_wdt
  blacklist it8712f_wdt
  blacklist it87_wdt
  blacklist kempld_wdt
  blacklist machzwd
  blacklist max63xx_wdt
  blacklist mei_wdt
  blacklist mena21_wdt
  blacklist menf21bmc_wdt
  blacklist menz69_wdt
  blacklist mlx_wdt
  blacklist ni903x_wdt
  blacklist nic7018_wdt
  blacklist nv_tco
  blacklist of_xilinx_wdt
  blacklist pc87413_wdt
  blacklist pcwd_pci
  blacklist pcwd_usb
  blacklist pretimeout_panic
  blacklist rave-sp-wdt
  blacklist retu_wdt
  blacklist sbc60xxwdt
  blacklist sbc_epx_c3
  blacklist sbc_fitpc2_wdt
  blacklist sc1200wdt
  blacklist sch311x_wdt
  blacklist smsc37b787_wdt
  blacklist softdog
  blacklist sp5100_tco
  blacklist tqmx86_wdt
  blacklist twl4030_wdt
  blacklist via_wdt
  blacklist w83627hf_wdt
  blacklist w83877f_wdt
  blacklist w83977f_wdt
  blacklist wafer5823wdt
  blacklist wdat_wdt
  blacklist wdt_pci
  blacklist wm831x_wdt
  blacklist wm8350_wdt
  blacklist xen_wdt
  blacklist ziirave_wdt

  However kernel snaps do not provide modprobe.d nor they are used by
  default. Is pc-kernel supposed to skip shipping those? Should there be
  modprobe.d in the core20 snap that prevents these known modules from
  loading by default?

  Also I'm not too sure about the watchdog modules exclusion, given that
  systemd can operate watchdogs by default, hence it shouldn't be too
  dangerous to autoenable them?

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1948038] [NEW] disable CONFIG_KFENCE_STATIC_KEYS in linux 5.15

[Andrea Righi]

Public bug reported:

[Impact]

KFENCE devs are changing CONFIG_KFENCE_STATIC_KEYS to be disabled by
default, because it's introducing more problems than benefits:

https://lore.kernel.org/all/20211019102524.2807208-2-el...@google.com/T/#u

This also seems to trigger QEMU bugs during the systemd autopkgtest, like:
https://bugs.launchpad.net/qemu/+bug/1920934

[Test case]

Run systemd autopkgtest.

[Fix]

Disable CONFIG_KFENCE_STATIC_KEYS.

[Regression potential]

We may experience an overall performance regression for not using static
branches in the KFENCE code.

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

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

** Also affects: linux (Ubuntu Jammy)
   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/1948038

Title:
  disable CONFIG_KFENCE_STATIC_KEYS in linux 5.15

Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  New

Bug description:
  [Impact]

  KFENCE devs are changing CONFIG_KFENCE_STATIC_KEYS to be disabled by
  default, because it's introducing more problems than benefits:

  https://lore.kernel.org/all/20211019102524.2807208-2-el...@google.com/T/#u

  This also seems to trigger QEMU bugs during the systemd autopkgtest, like:
  https://bugs.launchpad.net/qemu/+bug/1920934

  [Test case]

  Run systemd autopkgtest.

  [Fix]

  Disable CONFIG_KFENCE_STATIC_KEYS.

  [Regression potential]

  We may experience an overall performance regression for not using
  static branches in the KFENCE code.

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Benjamin Stanger]

For me it's the same situation, does not mather if touchpad and or
trackpad enabled or disabled in bios, i just get the kernel panic. I've
installed debian stable for now to ensure everything works as expected.

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro 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.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Claudio Romeo]

I got the same kernel panic error showed in the "S13 kernel panic" image by 
Pietro Mingo (skar395).
I workarounded the problem by entering the BIOS and disabling the trackpoint.
The trackpad can remain active.
This is not a solution, but it works.
Please, forgive my bad English

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro 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.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1947568] Re: cannot promote clone: "not a cloned filesystem"

[James Dingwall]

Present with latest kernel and user space packages:

# zfs create -V1G rpool/test1
# zfs snapshot rpool/test1@test2
# zfs clone rpool/test1@test2 rpool/test3
# zfs promote rpool/test3
cannot promote 'rpool/test3': not a cloned filesystem

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.3 LTS
Release:20.04
Codename:   focal

# uname -r
5.11.0-38-generic

# modinfo zfs | grep -i version
version:2.0.2-1ubuntu5.1
srcversion: F267DF7B3FFB43AFE76257D
vermagic:   5.11.0-38-generic SMP mod_unload modversions 

# apt-cache policy zfsutils-linux
zfsutils-linux:
  Installed: 0.8.3-1ubuntu12.13
  Candidate: 0.8.3-1ubuntu12.13
  Version table:
 *** 0.8.3-1ubuntu12.13 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 0.8.3-1ubuntu12.9 500
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 0.8.3-1ubuntu12 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

Title:
  cannot promote clone: "not a cloned filesystem"

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I have a zvol containing a Windows image for a virtual machine.  After
  restarting the system a node under /dev/zvol/... was not created for
  the virtual disk and no amount of prompting by `udevadm trigger`
  helped.  Instead I created a snapshot from the most recent hourly
  backup:

  # zfs clone rpool/vm/windows/windows10/hda@hourly07 
rpool/vm/windows/windows10/hda-new
  # zfs promote rpool/vm/windows/windows10/hda-new
  cannot promote 'rpool/vm/windows/windows10/hda-new': not a cloned filesystem
  (didn't work here but carried on assuming something can be sorted later)
  # zfs rename rpool/vm/windows/windows10/hda rpool/vm/windows/windows10/hda-old
  # zfs rename rpool/vm/windows/windows10/hda-new rpool/vm/windows/windows10/hda

  Entries in /dev appeared and I could start the virtual machine.
  Trying to promote the clone gives 'not a cloned filesystem' message.
  I later renamed the old zvol and tried to cleanup:

  # zfs rename rpool/vm/windows/windows10/hda-old rpool/to-be-deleted
  #  zfs destroy rpool/to-be-deleted@hourly07
  cannot destroy 'rpool/to-be-deleted@hourly07': snapshot has dependent clones
  use '-R' to destroy the following datasets:
  rpool/vm/windows/windows10/hda@hourly09
  rpool/vm/windows/windows10/hda@hourly10
  rpool/vm/windows/windows10/hda
  # zfs promote rpool/vm/windows/windows10/hda
  cannot promote 'rpool/vm/windows/windows10/hda': not a cloned filesystem

  # zfs get origin rpool/vm/windows/windows10/hda
  NAMEPROPERTY  VALUE SOURCE
  rpool/vm/windows/windows10/hda  originrpool/to-be-deleted@hourly07  -

  # zfs get clones rpool/to-be-deleted@hourly07
  NAME  PROPERTY  VALUE   SOURCE
  rpool/to-be-deleted@hourly07  clonesrpool/vm/windows/windows10/hda  -

  The dependency between seems to be as expected.  This small test fails
  in the same way:

  # zfs create -V1G rpool/vm/test
  # zfs snapshot rpool/vm/test@test2
  # zfs clone rpool/vm/test@test2 rpool/vm/test3
  # zfs promote rpool/vm/test3
  cannot promote 'rpool/vm/test3': not a cloned filesystem
  # zfs get origin rpool/vm/test3
  NAMEPROPERTY  VALUESOURCE
  rpool/vm/test3  originrpool/vm/test@test2  -
  # zfs get clones rpool/vm/test@test2
  NAME PROPERTY  VALUE   SOURCE
  rpool/vm/test@test2  clonesrpool/vm/test3  -

  All the zpool members are ONLINE and no errors are reported.

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal

  # uname -r
  5.11.0-37-generic

  # modinfo zfs | grep -i version
  version:2.0.2-1ubuntu5.1
  srcversion: F267DF7B3FFB43AFE76257D
  vermagic:   5.11.0-37-generic SMP mod_unload modversions

  # apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.8.3-1ubuntu12.12
Candidate: 0.8.3-1ubuntu12.13
Version table:
   0.8.3-1ubuntu12.13 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   *** 0.8.3-1ubuntu12.12 100
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12.9 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   0.8.3-1ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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


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

[Kernel-packages] [Bug 1947601] Re: Cannot start docker container on ubuntu 21.10 server for raspberry pi

[Dave Jones]

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

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

Title:
  Cannot start docker container on ubuntu 21.10 server for raspberry pi

Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  Using the Ubuntu image for Raspberry Pi from here:
  https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-
  server-arm64+raspi.img.xz

  After installing the docker.io package, I cannot start a docker
  container. Example:

  $ sudo docker run --rm hello-world
  docker: Error response from daemon: failed to create endpoint pensive_greider 
on network bridge: failed to add the host (veth2102512) <=> sandbox 
(veth4fb66df) pair interfaces: operation not supported.

  This was working in the previous ubuntu release for 64 bit raspberry
  pi, 21.04.

  This problem is caused by the linux kernel shipped for ubuntu 21.10
  for 64 bit raspberry pi, see post #14.

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


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

[Kernel-packages] [Bug 1947859] Re: linux-azure: Updata MANA to 5.15-rc6

[Tim Gardner]

** Changed in: linux-azure (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: linux-azure (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

** Changed in: linux-azure (Ubuntu Impish)
   Status: In Progress => Fix Committed

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

Title:
  linux-azure: Updata MANA to 5.15-rc6

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-azure source package in Hirsute:
  Fix Committed
Status in linux-azure source package in Impish:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested the addition of MANA EQ-sharing patch set
  which is essentially everything up through v5.15-rc6.

  3 more patches from Haiyang regarding EQ-sharing for Microsoft Azure
  Network Adapter (MANA). This saves MSI-X interrupts and allows the
  host to offer more virtual ports (network interfaces) to the VM. With
  the patches, the MANA driver supports up to 256 virtual ports per VF
  (it was 16/VF), and support up to 64 queues per vPort (it was 16).

  [Test Case]

  Microsoft to test and verify.

  [Where things might go wrong]

  More virtual ports may cause issues in older kernels.

  [Other Info]

  SF: #00321275

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


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

[Kernel-packages] [Bug 1943103] Re: Kernel 5.4.0-84 Graphical Issues and Overheating

[Piotr Filiciak]

Mainline kernel had this issue - but it was resolved by patch:
https://github.com/torvalds/linux/commit/8b4bd256674720709a9d858a219fcac6f2f253b5#diff-fa93c4ecc9ca98e9a9a7895c81c1965a1732bc6928e2edf74734a5638215f794

Can you apply that patch for Ubuntu kernels 5.4.0-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/1943103

Title:
  Kernel 5.4.0-84 Graphical Issues and Overheating

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  > Windows are glitchy and laptop is overheating.

  cat /proc/version_signature:
  Ubuntu 5.4.0-84.94-generic 5.4.133

  sudo lspci -vnvn:
  [Log Attached]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  knj6145 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Linux Mint 20.2
  InstallationDate: Installed on 2021-08-16 (24 days ago)
  InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703
  MachineType: LENOVO 82A1
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_PH:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic 
root=UUID=bf191557-7167-4211-a91d-d9ef3b7412f1 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
  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.4.0-84-generic N/A
   linux-backports-modules-5.4.0-84-generic  N/A
   linux-firmware1.187.16
  Tags:  uma
  Uname: Linux 5.4.0-84-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 01/14/2021
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO

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


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

Re: [Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver

[cedric]

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

Hi Chris,

I was trying to install Ubuntu 21.10 (fresh download) and I have the 
same issue.

Regards

Cédric

On 9/6/21 13:20, Chris Chiu wrote:
> It should be caused by the kbuild flag `-fcf-protection=none` and this
> will not be applied for the UBUNTU release image.
>

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

Title:
  kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do not know how to find information to help debug.
  The laptop is lenovo E15 with latest BIOS 1.13

  kubuntu 21.04

  laptop boots correctly with 5.13.8 and trackpad works.
  with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-12 (13 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: linux (not installed)
  Tags:  hirsute
  Uname: Linux 5.13.8-051308-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-12 (14 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: linux (not installed)
  Tags:  hirsute
  Uname: Linux 5.13.8-051308-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1948006] CRDA.txt

[Richard Appleby]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1948006/+attachment/5534900/+files/CRDA.txt

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

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

[Richard Appleby]

apport information

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

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard1338 F pulseaudio
   /dev/snd/controlC1:  richard1338 F pulseaudio
   /dev/snd/controlC0:  richard1338 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-10-17 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ProBook 430 G8 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-19-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: 08/26/2021
  dmi.bios.release: 6.3
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.06.03
  dmi.board.name: 87DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.12.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.18
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G8 Notebook PC
  dmi.product.sku: 2W1E9EA#ABU
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1948006] Re: Speaker Mute and Microphone Mute LED indicators not working on HP Probook 430 G8

[Richard Appleby]

apport information

** Tags added: apport-collected wayland-session

** Description changed:

  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.
  
  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.
  
  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10
  
  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14
  
  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status
  
  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI
  
  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl
  
  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 
  
  ... with /dev/snd/hwC0D0 as the  and  set to 0x01,
  0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.
  
- Code appears to exist to drive these LEDs (and is used by other HP
- ProBook models) but it needs to be enabled when this specific Audio
- Controller [103c:87df] is detected.
+ Code appears to exist to drive these LEDs (and is used by other HP ProBook 
models) but it needs to be enabled when this specific Audio Controller 
[103c:87df] is detected.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu70
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  richard1338 F pulseaudio
+  /dev/snd/controlC1:  richard1338 F pulseaudio
+  /dev/snd/controlC0:  richard1338 F pulseaudio
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2021-10-17 (3 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ MachineType: HP HP ProBook 430 G8 Notebook PC
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=36d5e175-d718-4137-974a-719ca99e9b27 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
+ RelatedPackageVersions:
+  linux-restricted-modules-5.13.0-19-generic N/A
+  linux-backports-modules-5.13.0-19-generic  N/A
+  linux-firmware 1.201
+ Tags:  wayland-session impish
+ Uname: Linux 5.13.0-19-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: 08/26/2021
+ dmi.bios.release: 6.3
+ dmi.bios.vendor: HP
+ dmi.bios.version: T70 Ver. 01.06.03
+ dmi.board.name: 87DF
+ dmi.board.vendor: HP
+ dmi.board.version: KBC Version 33.12.00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: HP
+ dmi.ec.firmware.release: 51.18
+ dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.06.03:bd08/26/2021:br6.3:efr51.18:svnHP:pnHPProBook430G8NotebookPC:pvr:sku2W1E9EA#ABU:rvnHP:rn87DF:rvrKBCVersion33.12.00:cvnHP:ct10:cvr:
+ dmi.product.family: 103C_5336AN HP ProBook
+ dmi.product.name: HP ProBook 430 G8 Notebook PC
+ dmi.product.sku: 2W1E9EA#ABU
+ dmi.sys.vendor: HP

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1948006/+attachment/5534899/+files/AlsaInfo.txt

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Confirmed

Bug 

[Kernel-packages] [Bug 1947853] Re: ubuntu20.04 crash

[susew]

** Information type changed from Public to Private Security

** Information type changed from Private Security to Public Security

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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

[Kernel-packages] [Bug 1948011] [NEW] SDDM shows a black screen when nvidia-driver-470 is updated to 470.74

[Karsten]

Public bug reported:

This bug is encountered on a computer with:

Kubuntu 21.10
MSI Gaming X Trio 3060 Ti

The following repo is used:

ppa: kubuntu-backports

GPU driver:

Nvidia driver metapackage from nvidia-driver-470(proprietary, tested)

What I expected: SDDM working just fine, showing every elements
What happened: SDDM is showing a black screen on login, logout, lockscreen. BUT 
logging in works.
What I did: Updating nvidia-driver-470 from 470.63 to 470.74
What I tried to do to fix: dpkg-reconfigure sddm

I suspect something is conflicting SDDM with the 470.74 driver.
Downgrading to 470.63 will fix this problem.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: nvidia-driver-470 470.74-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Oct 21 20:19:55 2021
InstallationDate: Installed on 2021-08-24 (58 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 LANGUAGE=en_HK:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_HK.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-graphics-drivers-470
UpgradeStatus: Upgraded to impish on 2021-10-21 (0 days ago)

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


** Tags: amd64 apport-bug impish

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

Title:
  SDDM shows a black screen when nvidia-driver-470 is updated to 470.74

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

Bug description:
  This bug is encountered on a computer with:

  Kubuntu 21.10
  MSI Gaming X Trio 3060 Ti

  The following repo is used:

  ppa: kubuntu-backports

  GPU driver:

  Nvidia driver metapackage from nvidia-driver-470(proprietary, tested)

  What I expected: SDDM working just fine, showing every elements
  What happened: SDDM is showing a black screen on login, logout, lockscreen. 
BUT logging in works.
  What I did: Updating nvidia-driver-470 from 470.63 to 470.74
  What I tried to do to fix: dpkg-reconfigure sddm

  I suspect something is conflicting SDDM with the 470.74 driver.
  Downgrading to 470.63 will fix this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nvidia-driver-470 470.74-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 21 20:19:55 2021
  InstallationDate: Installed on 2021-08-24 (58 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-470
  UpgradeStatus: Upgraded to impish on 2021-10-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1948011/+subscriptions


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

[Kernel-packages] [Bug 1948006] 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 1948006

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

** Tags added: impish

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP
  Probook 430 G8

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
  key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14

  apt-cache policy alsa-base:
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu7
    Candidate: 1.0.25+dfsg-0ubuntu7
    Version table:
   *** 1.0.25+dfsg-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
   Flags: bus master, fast devsel, latency 64, IRQ 168
   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
   Capabilities: [50] Power Management version 3
   Capabilities: [80] Vendor Specific Information: Len=14 
   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Kernel driver in use: sof-audio-pci-intel-tgl
   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  Using:
  sudo hda-verb  0x01 SET_GPIO_MASK 
  sudo hda-verb  0x01 SET_GPIO_DIRECTION 
  sudo hda-verb  0x01 SET_GPIO_DATA 

  ... with /dev/snd/hwC0D0 as the  and  set to
  0x01, 0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
  connected to the GPIO associated with  = 0x01, and the F6
  (Speaker Mute) LED is connected to the GPIO associated with
   = 0x02.

  Code appears to exist to drive these LEDs (and is used by other HP
  ProBook models) but it needs to be enabled when this specific Audio
  Controller [103c:87df] is detected.

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


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

[Kernel-packages] [Bug 1948006] [NEW] Speaker Mute and Microphone Mute LED indicators not working on HP Probook 430 G8

[Richard Appleby]

Public bug reported:

The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
key to indicate that the Speakers (F6) and Microphone (F8) are muted.
Pressing F6 correctly toggles the output of sound off and on, but the
indicator LED never illuminates. Pressing F8 correctly toggles the
Microphone input on and off, but again the indicator LED never
illuminates.

The expected operation would be that each of the LEDs would be
illuminated when their respective mutes are in effect.

lsb_release -rd:
Description:Ubuntu 21.10
Release:21.10

cat /proc/version_signature:
Ubuntu 5.13.0-19.19-generic 5.13.14

apt-cache policy alsa-base:
alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu7
  Candidate: 1.0.25+dfsg-0ubuntu7
  Version table:
 *** 1.0.25+dfsg-0ubuntu7 500
500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
100 /var/lib/dpkg/status

grep -i codec /proc/asound/card*/codec*:
/proc/asound/card0/codec#0:Codec: Realtek ALC236
/proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI

sudo lspci -nn -v -s 00:1f.3:
00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
 Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology Audio 
Controller [103c:87df]
 Flags: bus master, fast devsel, latency 64, IRQ 168
 Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
 Memory at 600300 (64-bit, non-prefetchable) [size=1M]
 Capabilities: [50] Power Management version 3
 Capabilities: [80] Vendor Specific Information: Len=14 
 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
 Kernel driver in use: sof-audio-pci-intel-tgl
 Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

Using:
sudo hda-verb  0x01 SET_GPIO_MASK 
sudo hda-verb  0x01 SET_GPIO_DIRECTION 
sudo hda-verb  0x01 SET_GPIO_DATA 

... with /dev/snd/hwC0D0 as the  and  set to 0x01,
0x02 in turn it is possible to see that the F8 (Mic Mute) LED is
connected to the GPIO associated with  = 0x01, and the F6
(Speaker Mute) LED is connected to the GPIO associated with
 = 0x02.

Code appears to exist to drive these LEDs (and is used by other HP
ProBook models) but it needs to be enabled when this specific Audio
Controller [103c:87df] is detected.

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

** Description changed:

- The HP ProBook 430 has LED indicators built into the F6 key and F8 key
- to indicate that the Speakers (F6) and Microphone (F8) are muted.
+ The HP ProBook 430 G8 has LED indicators built into the F6 key and F8
+ key to indicate that the Speakers (F6) and Microphone (F8) are muted.
  Pressing F6 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.
  
  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.
  
  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10
  
  cat /proc/version_signature:
  Ubuntu 5.13.0-19.19-generic 5.13.14
  
  apt-cache policy alsa-base:
  alsa-base:
-   Installed: 1.0.25+dfsg-0ubuntu7
-   Candidate: 1.0.25+dfsg-0ubuntu7
-   Version table:
-  *** 1.0.25+dfsg-0ubuntu7 500
- 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
- 500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.0.25+dfsg-0ubuntu7
+   Candidate: 1.0.25+dfsg-0ubuntu7
+   Version table:
+  *** 1.0.25+dfsg-0ubuntu7 500
+ 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
+ 500 http://gb.archive.ubuntu.com/ubuntu impish/main i386 Packages
+ 100 /var/lib/dpkg/status
  
  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: Realtek ALC236
  /proc/asound/card0/codec#2:Codec: Intel Tigerlake HDMI
  
  sudo lspci -nn -v -s 00:1f.3:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
-   Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
-   Flags: bus master, fast devsel, latency 64, IRQ 168
-   Memory at 6003248000 (64-bit, non-prefetchable) [size=16K]
-   Memory at 600300 (64-bit, non-prefetchable) [size=1M]
-   Capabilities: [50] Power Management version 3
-   Capabilities: [80] Vendor Specific Information: Len=14 
-   Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
-   Kernel driver in use: sof-audio-pci-intel-tgl
-   Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl
+  Subsystem: Hewlett-Packard Company Tiger Lake-LP Smart Sound Technology 
Audio Controller [103c:87df]
+  Flags: bus master, fast devsel, latency 64, IRQ 168
+  

[Kernel-packages] [Bug 1930754] Re: e1000e extremly slow

[Merlin Hartley]

Brilliant! This seems to have solved the issues on our new Dell OptiPlex
7090s too .

Apologies if this is obvious ... but does this fix end up being back-
ported into HWE (I seem to recall reading that it may do that after 3
weeks or something?)

Thanks!

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

Title:
  e1000e extremly slow

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
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-oem-5.14 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-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  In Progress
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-oem-5.14 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
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  e1000e on TGP PCH encounters a network speed issue that rx speed is below 
1MB/s

  [Fix]
  Intel provides 2 patches to fix this
  https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=263466

  [Test]
  Verified by our Dell and Lenovo platforms and the bug reporter.

  [Where problems could occur]
  The fix only applies to e1000e with TGP PCH, and add a flag 
"E1000_FFLT_DBG_DONT_GATE_WAKE_DMA_CLK". The impact should be minimized and 
should not lead to other regressions.

  =

  We have dell latitude 5420 & 5520 laptops with onboard intel ethernet 
controller.
  Problem is that the ethernet port is extremely slow. about 100kbyte/s 
download throughput while on a gigabit connection. Upload seems to work just 
fine.

  Also when I pxe boot the system it's also painfully slow.

  But here comes the funny part. When I attach a usb memory stick the
  throughput of the networkcontroller is as expected.

  I've used latest ubuntu 20.04.2 kernel 5.8.0-55
  I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem

  Turns out this problem is not showing up when I manually install the
  5.8.18 kernel.

  Also when I create my own iso with the help of Cubic and install the
  5.8.18 kernel in it the pxe boot is working as expected with high
  throughput

  system: Dell latitude 5420 + 5520
  nic: Ethernet Connection (13) I219-LM
  ubuntu 20.04.2
  module: e1000e

  Please assist. Thank you

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


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

[Kernel-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow

[Luca Capra]

Hi, I am on 21.10 with intel driver and latest displaylink from their
website. Everything used to work decently until a couple of day ago when
I started seeing the external monitor very slow. I was on 21.04 and
after  an update it has started being slow.

1. It is slower when more things change on the screen, only the mouse works 
slow a full screen rendering is unusably slow.
2. on the login screen the screen works very well, as I was used to.
3. Audio work fine, rendering is very slow

About my pc

1. Linux vin 5.13.0-20-generic #20-Ubuntu SMP Fri Oct 15 14:21:35 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux
2. Driver from display link displaylink-driver-5.4.1-55.174
3. Tried X11 and Wayland from GDM with Gnome

I tried to troubleshoot as described here
https://wiki.archlinux.org/title/DisplayLink and setting
LIBGL_DRI3_DISABLE=true as said here but it does not change

Any hint is appreciated! 
Thank you

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

Title:
  Ubuntu 20.04 and Displaylink is extremely slow

Status in Nouveau Xorg driver:
  Unknown
Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  In Progress
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  In Progress
Status in xorg-server source package in Hirsute:
  In Progress
Status in xorg-server source package in Impish:
  Fix Released

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

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


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

[Kernel-packages] [Bug 1947999] Re: Ubuntu on Wayland stutters, runs at half frame rate for Nvidia Ampere cards

[Daniel van Vugt]

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: New => Triaged

** Description changed:

  GNOME on Wayland stutters, runs at half frame rate for Nvidia Ampere
  cards.
  
  https://forums.developer.nvidia.com/t/eglstreamconsumeracquireattribnv-
  function-execution-became-significantly-slower-in-470-42-01-driver-
  release/182746/6
+ 
+ Workaround: Use a Xorg session instead.

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

Title:
  Ubuntu on Wayland stutters, runs at half frame rate for Nvidia Ampere
  cards

Status in Mutter:
  Unknown
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged

Bug description:
  GNOME on Wayland stutters, runs at half frame rate for Nvidia Ampere
  cards.

  https://forums.developer.nvidia.com/t/eglstreamconsumeracquireattribnv-
  function-execution-became-significantly-slower-in-470-42-01-driver-
  release/182746/6

  Workaround: Use a Xorg session instead.

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


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

[Kernel-packages] [Bug 1947999] [NEW] Ubuntu on Wayland stutters, runs at half frame rate for Nvidia Ampere cards

[Daniel van Vugt]

Public bug reported:

GNOME on Wayland stutters, runs at half frame rate for Nvidia Ampere
cards.

https://forums.developer.nvidia.com/t/eglstreamconsumeracquireattribnv-
function-execution-became-significantly-slower-in-470-42-01-driver-
release/182746/6

** Affects: mutter
 Importance: Unknown
 Status: Unknown

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


** Tags: impish nvidia nvidia-drm.modeset performance

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

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1924
   Importance: Unknown
   Status: Unknown

** Summary changed:

- GNOME on Wayland stutters, runs at half frame rate for Nvidia Ampere cards
+ Ubuntu on Wayland stutters, runs at half frame rate for Nvidia Ampere cards

** Tags added: performance

** Tags added: nvidia-drm.modeset

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

Title:
  Ubuntu on Wayland stutters, runs at half frame rate for Nvidia Ampere
  cards

Status in Mutter:
  Unknown
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  GNOME on Wayland stutters, runs at half frame rate for Nvidia Ampere
  cards.

  https://forums.developer.nvidia.com/t/eglstreamconsumeracquireattribnv-
  function-execution-became-significantly-slower-in-470-42-01-driver-
  release/182746/6

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


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

[Kernel-packages] [Bug 1929901] Re: [EHL][TGL][ADL] EDAC support

[Anthony Wong]

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

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

Title:
  [EHL][TGL][ADL] EDAC support

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged
Status in linux-intel package in Ubuntu:
  Fix Released
Status in linux-intel-5.13 package in Ubuntu:
  Fix Committed

Bug description:
  Description
  EDAC driver support on EHL & TGL for reporting ECC error and DIMM location

  Hardware: Tiger Lake & Elkhart Lake & Alder 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/1929901/+subscriptions


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

[Kernel-packages] [Bug 1842106] Re: [EHL][OSE] HS-UART implementation

[quanxian]

254cc7743e84(5.5) 4f912b898dc2(5.4) b4d0aac23e35(5.4)

UART testing is passed. seems no more commits needed.

** Changed in: intel
   Status: In Progress => Fix Released

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

Title:
  [EHL][OSE] HS-UART implementation

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:
  Elkhart Lake has Offload Services Engine (OSE) that will be BIOS configurable 
either to have some RTOS take control of its IO blocks or hand them off to 
running OS. IoTG has asked to support UART. This should be based on Synopsys 
v4.00a specification.

  Target Release: 20.10
  Target Kernel: TBD

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


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

[Kernel-packages] [Bug 1947819] Re: Can't resume from sleep on on ThinkPad P14S Gen 2

[Bin Li]

@Rishi,

 Could you help provide the log when you reproduced this issue? Thanks!

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

Title:
  Can't resume from sleep on on ThinkPad P14S Gen 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If it goes to sleep, it doesn't wake back up again.

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


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

[Kernel-packages] [Bug 1947818] Re: The fans are constantly whirring on ThinkPad P14S Gen 2

[Bin Li]

@Rishi,

 Could you help provide the log when you reproduced this issue? Thanks!

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

Title:
  The fans are constantly whirring on ThinkPad P14S Gen 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans are constantly whirring despite next to no CPU usage, it's
  quite loud, on versions 20.04, 21.04 and 21.10 it has the same issues.

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


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

[Kernel-packages] [Bug 1909814] Re: Medion Notebook Keyboard not working

[Hui Wang]

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

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

Title:
  Medion Notebook Keyboard not working

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Released

Bug description:
  [Impact]
  The keyboard of some medion laptops can't work under Linux.

  [Fix]
  Backport a upstream patch, after applying the patch, the keyboard
  will skip the irq override from the acpi resource layer, and the
  keyboard could work normally.

  [Test]
  Booting the patched kernel, use the keyboard to do the input.

  [Where problems could occur]
  The patch will skip the irq override based on the DMI info, so
  if a medion laptop which has the same DMI info and the irq 1
  needs to be overriden, this patch will introduce regression on
  the machine, but this possibility is very low. If this happens,
  we will consider to add more DMI match info in the table.


  Hello,
  Brand new laptop (Medion), keyboard is only working with the grub menu.
  Mouse is now working since 20.10 have been installed.
  Only the luminosity key are working on the keyboard.
  External usb keyboard works fine.
  I tried to install with usb keyboard disconnected but doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  did4364 F pulseaudio
   /dev/snd/pcmC0D0p:   did4364 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  1 16:24:12 2021
  InstallationDate: Installed on 2021-01-01 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: MEDION S15450
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2020
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 209
  dmi.board.asset.tag: Default string
  dmi.board.name: M15T
  dmi.board.vendor: MEDION
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring:
  dmi.product.family: Akoya
  dmi.product.name: S15450
  dmi.product.sku: ML-230008 30030452
  dmi.product.version: Default string
  dmi.sys.vendor: MEDION

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[ahmet yıldırım]

I returned to kernel 5.11 because of this problem.

I hope that it will be fixed as soon as possible.

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro 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.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1934293] Re: Add l2tp.sh in net from ubuntu_kernel_selftests back

[Stefan Bader]

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

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

Title:
  Add l2tp.sh in net from ubuntu_kernel_selftests back

Status in ubuntu-kernel-tests:
  In Progress
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:
  Fix Released
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 Groovy:
  Fix Committed
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.13 source package in Groovy:
  Invalid
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:
  Fix Committed
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  We have this test disabled intentionally in the past because of the
  lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from
  l2tp_xmit_skb()" in our kernels.

  The way we disable it is to override the executable bit with our
  autotest-client-tests suite [1], but this makes the test suite
  complain about script is not executable. Henceforth we further
  disable it by removing it from the Makefile in the patch "UBUNTU:
  SAUCE: selftests/net -- disable timeout"

  Now with commit 27d53323664c54 landed and l2tp.sh test re-enabled in
  our test suite [2], we still need to revert that SAUCE patch to get
  it tested.

  [1] 
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16
  [2] 
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d

  [Fix]
  Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  This test only exists in our tree since Focal.

  [Test]
  Run the net test suite in kselftest with patched source tree:
    sudo make -C linux/tools/testing/selftests TARGETS=net run_tests

  The l2tp.sh test will be executed.

  [Where problems could occur]
  This is only for testing tools, however if commit 27d53323664c54 "l2tp:
  remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we
  might crash our testing node like in bug 1854968. Also, we might see
  new failures caused by this test in the test report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934293/+subscriptions


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

[Kernel-packages] [Bug 1909814] Re: Medion Notebook Keyboard not working

[Did VDT]

I juts tested 5.11.0-39-generic and the keyboard is working fine on my Medion 
laptop.
Tank you VERY much for this update !

Not being familiar with tag changes etc.. I have no idea how to comply
with the suggested action ('verifiction-done-hirsute').

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

Title:
  Medion Notebook Keyboard not working

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Released

Bug description:
  [Impact]
  The keyboard of some medion laptops can't work under Linux.

  [Fix]
  Backport a upstream patch, after applying the patch, the keyboard
  will skip the irq override from the acpi resource layer, and the
  keyboard could work normally.

  [Test]
  Booting the patched kernel, use the keyboard to do the input.

  [Where problems could occur]
  The patch will skip the irq override based on the DMI info, so
  if a medion laptop which has the same DMI info and the irq 1
  needs to be overriden, this patch will introduce regression on
  the machine, but this possibility is very low. If this happens,
  we will consider to add more DMI match info in the table.


  Hello,
  Brand new laptop (Medion), keyboard is only working with the grub menu.
  Mouse is now working since 20.10 have been installed.
  Only the luminosity key are working on the keyboard.
  External usb keyboard works fine.
  I tried to install with usb keyboard disconnected but doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  did4364 F pulseaudio
   /dev/snd/pcmC0D0p:   did4364 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  1 16:24:12 2021
  InstallationDate: Installed on 2021-01-01 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: MEDION S15450
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2020
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 209
  dmi.board.asset.tag: Default string
  dmi.board.name: M15T
  dmi.board.vendor: MEDION
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring:
  dmi.product.family: Akoya
  dmi.product.name: S15450
  dmi.product.sku: ML-230008 30030452
  dmi.product.version: Default string
  dmi.sys.vendor: MEDION

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


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

[Kernel-packages] [Bug 1943103] Re: Kernel 5.4.0-84 Graphical Issues and Overheating

[Kai-Heng Feng]

Piotr,
Does mainline kernel have this issue?

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

Title:
  Kernel 5.4.0-84 Graphical Issues and Overheating

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  > Windows are glitchy and laptop is overheating.

  cat /proc/version_signature:
  Ubuntu 5.4.0-84.94-generic 5.4.133

  sudo lspci -vnvn:
  [Log Attached]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  knj6145 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Linux Mint 20.2
  InstallationDate: Installed on 2021-08-16 (24 days ago)
  InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703
  MachineType: LENOVO 82A1
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_PH:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic 
root=UUID=bf191557-7167-4211-a91d-d9ef3b7412f1 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
  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.4.0-84-generic N/A
   linux-backports-modules-5.4.0-84-generic  N/A
   linux-firmware1.187.16
  Tags:  uma
  Uname: Linux 5.4.0-84-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 01/14/2021
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Marco De Felice]

I have the same issue on my ThinkPad E14 Gen 2 Type 20TA with the latest
firmware.

Just wanted to add that the proposed workaround of disabling psmouse
(via boot options or via disabling in bios) is not working for me.

Also tried the kernel at
https://people.canonical.com/~mschiu77/lp1941773/I/ but this too is not
working.

I have a zsys encripted filesystem, when I boot normally I get the same
error others are getting.

When I boot with modprobe.blacklist=psmouse I can go past the previous
error and get to the point where the system asks for the password to
decrypt the filesystem, but then I get a different error (picture
attached)

** Attachment added: "kernel_problem.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+attachment/5534773/+files/kernel_problem.jpg

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro 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.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1662620] Re: "ip addr add" permits illegal labels

[Christian Ehrhardt ]

Thanks Chris for having a look.

> On the other hand, from the bug it looks like if you *don't* mix valid and 
> invalid labels
> then everything actually works? So this would potentially be breaking 
> currently working setups?

Yes while having that echoing in my head for a while I think you are
right. We would have the chance to disrupt working setups, so I beg your
pardon and would step back marking it won't fix.

** Changed in: iproute2 (Ubuntu Bionic)
   Status: Incomplete => Won't Fix

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

Title:
  "ip addr add" permits illegal labels

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

   * The filter on label names does not match the intention
 by upstream nor the description in the man page

   * Fix by backporting upstream fix that strengthens the check

  [Test Plan]

  Bad case:
  root@b:~# ip addr add 1.1.1.1 label test1 dev eth0
  "dev" (eth0) must match "label" (test1).
  root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0
  root@b:~# ip addr show dev eth0 | grep test
  inet 1.1.1.1/32 scope global eth0-test

  With the fix it should look like:
  root@i:~# ip addr add 1.1.1.1 label test1 dev eth0
  "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon.
  root@i:~# ip addr add 1.1.1.1 label eth0-test dev eth0
  "label" (eth0-test) must match "dev" (eth0) or be prefixed by "dev" with a 
colon.
  root@i:~# ip addr show dev eth0 | grep test

  [Where problems could occur]

   * While the fix indeed "corrects" behavior I must say that if someone 
 relied on the non-intended behavior it would now break e.g. his 
 scripting or automation.

  [Other Info]
   
   * It was too easy to fix and too long dormant to ignore it further,
 but if the SRU team says this is too much regression risk relative to 
 the gain we will mark it Won't Fix based on that decision.

  
  ---

  ip-address(8) manpage states:

    label NAME
  Each address may be tagged with a label string.  In order to preserve 
compatibility with Linux-2.0 net aliases, this string must coincide with the 
name of the device or must be prefixed with the device name followed by colon.

  But you can omit the colon, "ip addr add" is ONLY checking the label
  is prefixed with the device:

  # ip addr add 1.1.1.1 label test1 dev eth0
  "dev" (eth0) must match "label" (test1).

  # ip addr add 1.1.1.2 label eth0-test2 dev eth0

  # ip addr add 1.1.1.3 label eth0:test3 dev eth0

  Now ifconfig becomes confused about eth0-test2:

  # ifconfig eth0-test2
  eth0-test2: error fetching interface information: Device not found

  # ifconfig eth0:test3
  eth0:test3 Link encap:Ethernet  HWaddr b0:d5:cc:fe:1d:7c
    inet addr:1.1.1.3  Bcast:0.0.0.0  Mask:255.255.255.255
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    Interrupt:171

  And daemons like ntpd also log errors about the interface with the
  illegal label:

  ntpd[7570]: eth0-test3: getting interface flags: No such device
    ## => many of this error per minute until:
  ntpd[7570]: Too many errors.  Shutting up.

  So, I think ip addr show disallow adding address with illegal (as
  stated by his own documentation) labels, it must also check for the
  colon following the dev name.

  Version: 4.3.0-1ubuntu3

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


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

[Kernel-packages] [Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

[Kent Lin]

** Changed in: intel
   Status: New => Fix Committed

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

Title:
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

Status in intel:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  [Summary]
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
  [Steps to reproduce]
  1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to 
the system
  2. Boot to desktop
  3. Check if all Ethernet get IP address
  [Expected result]
  All Ethernet Port should up and runing and get the IP address.
  [Actual result]
  I225-IT Ethernet (8086:0d9f) does not work and did not get IP address
  [Failure rate]
  100%
  [Additional information]
  CID: 202109-29492
  SKU: N/A
  system-manufacturer: AAEON
  system-product-name: UPN-EHL01
  bios-version: UNEHAM0D
  CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571] (rev 01)
  kernel-version: 5.13.0-1004-intel

  [Stage]
  Issue reported and logs collected right after it happened

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


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

[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

[Kai-Heng Feng]

Does kernel parameter "pcie_aspm=off" help?

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

Title:
  b44 Ethernet driver null pointer during initialization

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This problem started after upgrading to Ubuntu 19.04. It was not
  present with 4.18.0-16-generic kernel and is present in the
  4.18.0-15-generic kernel. Ever time during boot there is a null
  pointer dereference in the b44 driver for the on-board Ethernet on
  this Dell Inspiron 6400. After that I can log in but networking
  related commands hang and the computer eventually locks up.
  Blacklisting the b44 module so it doesn't load works as a workaround,
  though of course the on board Ethernet can't be used that way. The b43
  WiFi still works then. The following is pasted from the log of one
  crash:

  6.483003] BUG: unable to handle kernel NULL pointer dereference at 

  6.483052] #PF error: [normal kernel read fault]
  6.483093] PGD 0 P4D 0 
  6.483133] Oops:  [#1] SMP PTI
  6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 
5.0.0-7-generic #8-Ubuntu
  6.483217] Hardware name: Dell Inc. MM061   /0XD720, 
BIOS A17 06/13/2007
  6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310
  6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 
44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 
0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f
  6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016
  6.483416] RAX: 0001 RBX:  RCX: 
  6.483467] RDX:  RSI: 001f RDI: 0001
  6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001
  6.483572] R10:  R11:  R12: 
  6.483621] R13:  R14: 0001 R15: 0020
  6.483670] FS:  7f2cb49ccbc0() GS:9d8a4c40() 
knlGS:
  6.483726] CS:  0010 DS:  ES:  CR0: 80050033
  6.483773] CR2:  CR3: c72ce000 CR4: 06f0
  6.483820] Call Trace:
  6.483869]  swiotlb_map+0x6c/0x1c0
  6.483915]  dma_direct_map_page+0xc5/0x160
  6.483965]  b44_alloc_rx_skb+0x18e/0x3f0 [b44]
  6.484013]  b44_init_rings+0xbe/0x1b0 [b44]
  6.484060]  b44_open+0xfc/0x3f0 [b44]
  6.484107]  __dev_open+0xd4/0x170
  6.484153]  __dev_change_flags+0x18f/0x200
  6.484199]  dev_change_flags+0x27/0x60
  6.484246]  do_setlink+0x31c/0xe30
  6.484292]  ? __nla_parse+0xf1/0x120
  6.484340]  ? cpumask_next+0x1b/0x20
  6.484388]  ? __snmp6_fill_stats64.isra.57+0xf6/0x120
  6.484439]  ? __nla_parse+0x38/0x120
  6.484488]  __rtnl_newlink+0x531/0x910
  6.484535]  ? __nla_put+0x20/0x30
  6.484586]  ? __kmalloc_node_track_caller+0x1e6/0x2b0
  6.484636]  ? pskb_expand_head+0x70/0x2e0
  6.484693]  ? __kmalloc_reserve.isra.53+0x31/0x90
  6.484751]  ? apparmor_inet_conn_request+0x40/0x40
  6.484822]  ? security_sock_rcv_skb+0x2f/0x50
  6.484879]  ? skb_queue_tail+0x43/0x50
  6.484934]  ? __netlink_sendskb+0x53/0x70
  6.484992]  ? syscall_return_via_sysret+0xf/0x7f
  6.485043]  ? __switch_to_asm+0x40/0x70
  6.485097]  ? syscall_return_via_sysret+0xf/0x7f
  6.485153]  ? _cond_resched+0x19/0x30
  6.485204]  ? kmem_cache_alloc_trace+0x153/0x1d0
  6.485253]  rtnl_newlink+0x48/0x70
  6.485301]  rtnetlink_rcv_msg+0x213/0x300
  6.485348]  ? __d_lookup+0x126/0x140
  6.485393]  ? rtnl_calcit.isra.31+0x100/0x100
  6.485440]  netlink_rcv_skb+0x4f/0x120
  6.485485]  rtnetlink_rcv+0x15/0x20
  6.485518]  netlink_unicast+0x1a1/0x260
  6.485518]  netlink_sendmsg+0x20d/0x3c0
  6.485518]  sock_sendmsg+0x3e/0x50
  6.485518]  ___sys_sendmsg+0x295/0x2f0
  6.485518]  ? rtnl_unlock+0xe/0x10
  6.485518]  ? addrconf_sysctl_forward+0x114/0x280
  6.485518]  ? dev_forward_change+0x140/0x140
  6.485518]  ? __fget_light+0x54/0x60
  6.485518]  __sys_sendmsg+0x5c/0xa0
  6.485518]  __x64_sys_sendmsg+0x1f/0x30
  6.485518]  do_syscall_64+0x5a/0x110
  6.485518]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  6.485518] RIP: 0033:0x7f2cb6153cb7
  6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 
3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 
ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48
  6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 
002e
  6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7
  6.485518] RDX:  RSI: 7ffe93a35cd0 RDI: 0008
  6.485518] RBP: 7ffe93a35cd0 R08:  R09: 
  6.485518] R10: 7f2cb6139ca0 R11: 0293 R12: 
  6.485518] R13: 5598b029e880 R14: 7ffe93a35e7c R15: 
  6.485518] Modules linked in: 

[Kernel-packages] [Bug 1935728] Re: [radeon] Mouse pointer randomly disappears - other mouse operations still work

[Kai-Heng Feng]

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

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

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

Title:
  [radeon] Mouse pointer randomly disappears - other mouse operations
  still work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The mouse pointer randomly dissappears (same behavior in ubuntu 20.04 LTS and 
ubuntu 20.10).
  When this occurs all other mouse operations still function
  - left/right click
  - scroll wheel
  - mouse position still moves

  Just the actual mouse pointer not visible.
  Only way to resolve is to restart the machine.
  Tried numerous ways to restart the mouse driver but nothing else successful

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-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: Sat Jul 10 14:45:22 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 
4670] [1002:9488] (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6]
  InstallationDate: Installed on 2021-07-05 (4 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Apple Inc. iMac10,1
  ProcKernelCmdLine: ro root=UUID=30ee9195-f382-4721-8655-6933b38f1842 
initrd=boot\initrd.img-5.8.0-59-generic
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 215.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F2268DC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268DC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268DC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268DC8:
  dmi.product.family: Mac
  dmi.product.name: iMac10,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/+bug/1935728/+subscriptions


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

[Kai-Heng Feng]

Does the issue happen when using `arecord` and `aplay`?

-- 
You 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:
  New
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 1945556] Re: Fix missing HDMI audio on Intel RKL

[Kai-Heng Feng]

** 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.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1945556

Title:
  Fix missing HDMI audio on Intel RKL

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Confirmed
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  HDMI audio is missing on Intel RKL.

  [Fix]
  Also use BIOS provided value for HDA link.

  [Test]
  HDMI audio is back after the fix gets applied.

  [Where problems could occur]
  Because this is a regression, this patch simply brings back the old
  behavior for RKL systems. There could be RKL systems get fixed by
  the offending commit, so this might break those hypothetical systems.

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


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

[Kernel-packages] [Bug 1947628] Re: VXLAN support is not present in kernel - Ubuntu 21.10 on Raspberry Pi 4 (64bit)

[Kai-Heng Feng]

** Package changed: linux (Ubuntu) => linux-raspi (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/1947628

Title:
  VXLAN support is not present in kernel - Ubuntu 21.10 on Raspberry Pi
  4 (64bit)

Status in linux-raspi package in Ubuntu:
  Incomplete

Bug description:
  Platform Information - Ubuntu 21.10, Linux  5.13.0-1008-raspi
  #9-Ubuntu SMP PREEMPT Wed Sep 29 08:27:44 UTC 2021 aarch64 aarch64
  aarch64 GNU/Linux

  
  The latest version of Ubuntu does not have VXLAN support.
  The following command confirms the same:
  modprobe vxlan 

  modprobe: FATAL: Module vxlan not found in directory
  /lib/modules/5.13.0-1008-raspi

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


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

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

[susew]

apport information

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

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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

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

[susew]

apport information

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

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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

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

[susew]

apport information

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

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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

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

[susew]

apport information

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

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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

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

[susew]

apport information

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

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

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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

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

[susew]

apport information

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

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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

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

[susew]

apport information

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

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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

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

[susew]

apport information

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

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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

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

[susew]

apport information

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

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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

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

[susew]

apport information

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

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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

[Kernel-packages] [Bug 1947853] Re: ubuntu20.04 crash

[susew]

apport information

** Tags added: apport-collected

** Description changed:

  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
+  crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.20.11-0ubuntu27.18
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CasperMD5CheckResult: skip
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2021-06-23 (120 days ago)
+ InstallationMedia:
+  
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lsusb:
+  Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
+  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ Lsusb-t:
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
+  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
+ MachineType: Alibaba Cloud Alibaba Cloud ECS
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=linux
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 cirrusdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
+ ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-77-generic N/A
+  linux-backports-modules-5.4.0-77-generic  N/A
+  linux-firmware1.187.15
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags:  focal
+ Uname: Linux 5.4.0-77-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 04/01/2014
+ dmi.bios.vendor: SeaBIOS
+ dmi.bios.version: 8c24b4c
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Alibaba Cloud
+ dmi.chassis.version: pc-i440fx-2.1
+ dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
+ dmi.product.name: Alibaba Cloud ECS
+ dmi.product.version: pc-i440fx-2.1
+ dmi.sys.vendor: Alibaba Cloud

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1947853/+attachment/5534746/+files/CRDA.txt

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ 

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

[susew]

apport information

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

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 19 11:18 seq
   crw-rw 1 root audio 116, 33 Oct 19 11:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-23 (120 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Alibaba Cloud Alibaba Cloud ECS
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=13843fcc-f592-4868-b87f-3784967cd0c4 ro vga=792 console=tty0 
console=ttyS0,115200n8 net.ifnames=0 noibrs quiet crashkernel=512M-:192M
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-77-generic N/A
   linux-backports-modules-5.4.0-77-generic  N/A
   linux-firmware1.187.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 8c24b4c
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alibaba Cloud
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr8c24b4c:bd04/01/2014:svnAlibabaCloud:pnAlibabaCloudECS:pvrpc-i440fx-2.1:cvnAlibabaCloud:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Alibaba Cloud ECS
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: Alibaba Cloud

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


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