[Kernel-packages] [Bug 1919007] Re: lowlatency kernel nvidia

[tele1234567891]

** Description changed:

  ={
  $ inxi -Fxxxrz
  System:Kernel: 5.8.0-44-lowlatency x86_64 bits: 64 compiler: N/A Desktop: 
MATE 1.24.0 info: mate-panel wm: marco 1.24.0
     dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 
20.04 focal
  Machine:   Type: Desktop Mobo: MSI model: B150M PRO-VDH (MS-7982) v: 1.0 
serial:  UEFI [Legacy]: American Megatrends
     v: 3.H0 date: 07/10/2018
  CPU:   Topology: Quad Core model: Intel Core i5-6400 bits: 64 type: MCP 
arch: Skylake-S rev: 3 L2 cache: 6144 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 21599
     Speed: 1842 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 1842 
2: 2103 3: 1923 4: 2615
  Graphics:  Device-1: NVIDIA GK106 [GeForce GTX 660] vendor: Gigabyte driver: 
nvidia v: 460.39 bus ID: 01:00.0
     chip ID: 10de:11c0
     Display: x11 server: X.Org 1.20.9 driver: nvidia unloaded: 
fbdev,modesetting,nouveau,vesa compositor: marco
     v: 1.24.0 resolution: 1920x1080~60Hz
     OpenGL: renderer: GeForce GTX 660/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39 
direct render: Yes
  ...
  Sensors:   System Temperatures: cpu: 44.5 C mobo: 29.8 C gpu: nvidia temp: 37 
C
     Fan Speeds (RPM): N/A gpu: nvidia fan: 36%
  Repos: No active apt repos in: /etc/apt/sources.list
     Active apt repos in: 
/etc/apt/sources.list.d/lutris-team-lutris-focal.list
     1: deb http://ppa.launchpad.net/lutris-team/lutris/ubuntu focal 
main
     Active apt repos in: 
/etc/apt/sources.list.d/official-dbgsym-repositories.list
     1: deb http://ddebs.ubuntu.com focal main restricted universe 
multiverse
     2: deb http://ddebs.ubuntu.com focal-updates main restricted 
universe multiverse
     Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list
     1: deb http://packages.linuxmint.com ulyssa main upstream import 
backport #id:linuxmint_main
     2: deb http://archive.ubuntu.com/ubuntu focal main restricted 
universe multiverse
     3: deb http://archive.ubuntu.com/ubuntu focal-updates main 
restricted universe multiverse
     4: deb http://archive.ubuntu.com/ubuntu focal-backports main 
restricted universe multiverse
     5: deb http://security.ubuntu.com/ubuntu/ focal-security main 
restricted universe multiverse
     6: deb http://archive.canonical.com/ubuntu/ focal partner
  Info:  Processes: 211 Uptime: 5h 30m Memory: 15.40 GiB used: 1.98 GiB 
(12.9%) Init: systemd v: 245 runlevel: 5 Compilers:
     gcc: 9.3.0 alt: 9 clang: 10.0.0-4ubuntu1 Shell: bash v: 5.0.17 
running in: mate-terminal inxi: 3.0.38
  =}
  
  
https://forums.linuxmint.com/viewtopic.php?f=49=307168=1907600=lowlatency+kernel+nvidia#p1907600
  
  I have the same problem.
  And I tried also report
  https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1918454
  
  but I don't know if it's in the right place.
  
  From " systemd-analyze plot > file.svg "
  I see that
  -
    sys-bus-pci-drivers-nvidia.device
    nvidia-persistenced.service
  -
  load after " getty.target " when not working.
  When worked for me, this was loaded faster.
  And "Ctrl+Alt+Backspace" it really helps.
  
  I suppose the services start randomly in systemd ,
  and more organized and constantly in init .
  
  I don't know how the driver or xorg works.
  Maybe you know how to debug the problem or where to report it?
+ 
+ 
+ **Edited**
+ When system worked correct I didn't notice the presence 
+ 
+   rtkit-daemon.service 
+   upower.service 
+ 
+ with nvidia services above. Maybe it's just a coincidence after update system.

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

Title:
  lowlatency kernel nvidia

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

Bug description:
  ={
  $ inxi -Fxxxrz
  System:Kernel: 5.8.0-44-lowlatency x86_64 bits: 64 compiler: N/A Desktop: 
MATE 1.24.0 info: mate-panel wm: marco 1.24.0
     dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 
20.04 focal
  Machine:   Type: Desktop Mobo: MSI model: B150M PRO-VDH (MS-7982) v: 1.0 
serial:  UEFI [Legacy]: American Megatrends
     v: 3.H0 date: 07/10/2018
  CPU:   Topology: Quad Core model: Intel Core i5-6400 bits: 64 type: MCP 
arch: Skylake-S rev: 3 L2 cache: 6144 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 21599
     Speed: 1842 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 1842 
2: 2103 3: 1923 4: 2615
  Graphics:  Device-1: NVIDIA GK106 [GeForce GTX 660] vendor: Gigabyte driver: 
nvidia v: 460.39 bus ID: 01:00.0
     chip ID: 

[Kernel-packages] [Bug 1919007] Re: lowlatency kernel nvidia

[tele1234567891]

** Description changed:

  ={
  $ inxi -Fxxxrz
- System:Kernel: 5.8.0-44-lowlatency x86_64 bits: 64 compiler: N/A Desktop: 
MATE 1.24.0 info: mate-panel wm: marco 1.24.0 
-dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 
20.04 focal 
- Machine:   Type: Desktop Mobo: MSI model: B150M PRO-VDH (MS-7982) v: 1.0 
serial:  UEFI [Legacy]: American Megatrends 
-v: 3.H0 date: 07/10/2018 
- CPU:   Topology: Quad Core model: Intel Core i5-6400 bits: 64 type: MCP 
arch: Skylake-S rev: 3 L2 cache: 6144 KiB 
-flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 21599 
-Speed: 1842 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 1842 
2: 2103 3: 1923 4: 2615 
- Graphics:  Device-1: NVIDIA GK106 [GeForce GTX 660] vendor: Gigabyte driver: 
nvidia v: 460.39 bus ID: 01:00.0 
-chip ID: 10de:11c0 
-Display: x11 server: X.Org 1.20.9 driver: nvidia unloaded: 
fbdev,modesetting,nouveau,vesa compositor: marco 
-v: 1.24.0 resolution: 1920x1080~60Hz 
-OpenGL: renderer: GeForce GTX 660/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39 
direct render: Yes 
+ System:Kernel: 5.8.0-44-lowlatency x86_64 bits: 64 compiler: N/A Desktop: 
MATE 1.24.0 info: mate-panel wm: marco 1.24.0
+    dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 
20.04 focal
+ Machine:   Type: Desktop Mobo: MSI model: B150M PRO-VDH (MS-7982) v: 1.0 
serial:  UEFI [Legacy]: American Megatrends
+    v: 3.H0 date: 07/10/2018
+ CPU:   Topology: Quad Core model: Intel Core i5-6400 bits: 64 type: MCP 
arch: Skylake-S rev: 3 L2 cache: 6144 KiB
+    flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 21599
+    Speed: 1842 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 1842 
2: 2103 3: 1923 4: 2615
+ Graphics:  Device-1: NVIDIA GK106 [GeForce GTX 660] vendor: Gigabyte driver: 
nvidia v: 460.39 bus ID: 01:00.0
+    chip ID: 10de:11c0
+    Display: x11 server: X.Org 1.20.9 driver: nvidia unloaded: 
fbdev,modesetting,nouveau,vesa compositor: marco
+    v: 1.24.0 resolution: 1920x1080~60Hz
+    OpenGL: renderer: GeForce GTX 660/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39 
direct render: Yes
  ...
- Sensors:   System Temperatures: cpu: 44.5 C mobo: 29.8 C gpu: nvidia temp: 37 
C 
-Fan Speeds (RPM): N/A gpu: nvidia fan: 36% 
- Repos: No active apt repos in: /etc/apt/sources.list 
-Active apt repos in: 
/etc/apt/sources.list.d/lutris-team-lutris-focal.list 
-1: deb http://ppa.launchpad.net/lutris-team/lutris/ubuntu focal 
main
-Active apt repos in: 
/etc/apt/sources.list.d/official-dbgsym-repositories.list 
-1: deb http://ddebs.ubuntu.com focal main restricted universe 
multiverse
-2: deb http://ddebs.ubuntu.com focal-updates main restricted 
universe multiverse
-Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
-1: deb http://packages.linuxmint.com ulyssa main upstream import 
backport #id:linuxmint_main
-2: deb http://archive.ubuntu.com/ubuntu focal main restricted 
universe multiverse
-3: deb http://archive.ubuntu.com/ubuntu focal-updates main 
restricted universe multiverse
-4: deb http://archive.ubuntu.com/ubuntu focal-backports main 
restricted universe multiverse
-5: deb http://security.ubuntu.com/ubuntu/ focal-security main 
restricted universe multiverse
-6: deb http://archive.canonical.com/ubuntu/ focal partner
- Info:  Processes: 211 Uptime: 5h 30m Memory: 15.40 GiB used: 1.98 GiB 
(12.9%) Init: systemd v: 245 runlevel: 5 Compilers: 
-gcc: 9.3.0 alt: 9 clang: 10.0.0-4ubuntu1 Shell: bash v: 5.0.17 
running in: mate-terminal inxi: 3.0.38
+ Sensors:   System Temperatures: cpu: 44.5 C mobo: 29.8 C gpu: nvidia temp: 37 
C
+    Fan Speeds (RPM): N/A gpu: nvidia fan: 36%
+ Repos: No active apt repos in: /etc/apt/sources.list
+    Active apt repos in: 
/etc/apt/sources.list.d/lutris-team-lutris-focal.list
+    1: deb http://ppa.launchpad.net/lutris-team/lutris/ubuntu focal 
main
+    Active apt repos in: 
/etc/apt/sources.list.d/official-dbgsym-repositories.list
+    1: deb http://ddebs.ubuntu.com focal main restricted universe 
multiverse
+    2: deb http://ddebs.ubuntu.com focal-updates main restricted 
universe multiverse
+    Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list
+    1: deb http://packages.linuxmint.com ulyssa main upstream import 
backport #id:linuxmint_main
+    2: deb http://archive.ubuntu.com/ubuntu focal main restricted 
universe multiverse
+    3: deb http://archive.ubuntu.com/ubuntu focal-updates main 
restricted universe multiverse
+    4: deb http://archive.ubuntu.com/ubuntu 

[Kernel-packages] [Bug 1919007] [NEW] lowlatency kernel nvidia

[tele1234567891]

Public bug reported:

={
$ inxi -Fxxxrz
System:Kernel: 5.8.0-44-lowlatency x86_64 bits: 64 compiler: N/A Desktop: 
MATE 1.24.0 info: mate-panel wm: marco 1.24.0 
   dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 
focal 
Machine:   Type: Desktop Mobo: MSI model: B150M PRO-VDH (MS-7982) v: 1.0 
serial:  UEFI [Legacy]: American Megatrends 
   v: 3.H0 date: 07/10/2018 
CPU:   Topology: Quad Core model: Intel Core i5-6400 bits: 64 type: MCP 
arch: Skylake-S rev: 3 L2 cache: 6144 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 21599 
   Speed: 1842 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 1842 2: 
2103 3: 1923 4: 2615 
Graphics:  Device-1: NVIDIA GK106 [GeForce GTX 660] vendor: Gigabyte driver: 
nvidia v: 460.39 bus ID: 01:00.0 
   chip ID: 10de:11c0 
   Display: x11 server: X.Org 1.20.9 driver: nvidia unloaded: 
fbdev,modesetting,nouveau,vesa compositor: marco 
   v: 1.24.0 resolution: 1920x1080~60Hz 
   OpenGL: renderer: GeForce GTX 660/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39 
direct render: Yes 
...
Sensors:   System Temperatures: cpu: 44.5 C mobo: 29.8 C gpu: nvidia temp: 37 C 
   Fan Speeds (RPM): N/A gpu: nvidia fan: 36% 
Repos: No active apt repos in: /etc/apt/sources.list 
   Active apt repos in: 
/etc/apt/sources.list.d/lutris-team-lutris-focal.list 
   1: deb http://ppa.launchpad.net/lutris-team/lutris/ubuntu focal main
   Active apt repos in: 
/etc/apt/sources.list.d/official-dbgsym-repositories.list 
   1: deb http://ddebs.ubuntu.com focal main restricted universe 
multiverse
   2: deb http://ddebs.ubuntu.com focal-updates main restricted 
universe multiverse
   Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
   1: deb http://packages.linuxmint.com ulyssa main upstream import 
backport #id:linuxmint_main
   2: deb http://archive.ubuntu.com/ubuntu focal main restricted 
universe multiverse
   3: deb http://archive.ubuntu.com/ubuntu focal-updates main 
restricted universe multiverse
   4: deb http://archive.ubuntu.com/ubuntu focal-backports main 
restricted universe multiverse
   5: deb http://security.ubuntu.com/ubuntu/ focal-security main 
restricted universe multiverse
   6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:  Processes: 211 Uptime: 5h 30m Memory: 15.40 GiB used: 1.98 GiB 
(12.9%) Init: systemd v: 245 runlevel: 5 Compilers: 
   gcc: 9.3.0 alt: 9 clang: 10.0.0-4ubuntu1 Shell: bash v: 5.0.17 
running in: mate-terminal inxi: 3.0.38
=}

https://forums.linuxmint.com/viewtopic.php?f=49=307168=1907600=lowlatency+kernel+nvidia#p1907600

I have the same problem.
And I tried also report 
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1918454

but I don't know if it's in the right place.

>From " systemd-analyze plot > file.svg "
I see that
-
  sys-bus-pci-drivers-nvidia.device
  nvidia-persistenced.service 
  rtkit-daemon.service 
  upower.service 
-
load after " getty.target " when not working.
When worked for me, this was loaded faster.
And "Ctrl+Alt+Backspace" it really helps.

I suppose the services start randomly in systemd ,
and more organized and constantly in init .

I don't know how the driver or xorg works.
Maybe you know how to debug the problem or where to report it?

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

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

Title:
  lowlatency kernel nvidia

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

Bug description:
  ={
  $ inxi -Fxxxrz
  System:Kernel: 5.8.0-44-lowlatency x86_64 bits: 64 compiler: N/A Desktop: 
MATE 1.24.0 info: mate-panel wm: marco 1.24.0 
 dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 
20.04 focal 
  Machine:   Type: Desktop Mobo: MSI model: B150M PRO-VDH (MS-7982) v: 1.0 
serial:  UEFI [Legacy]: American Megatrends 
 v: 3.H0 date: 07/10/2018 
  CPU:   Topology: Quad Core model: Intel Core i5-6400 bits: 64 type: MCP 
arch: Skylake-S rev: 3 L2 cache: 6144 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 21599 
 Speed: 1842 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 1842 
2: 2103 3: 1923 4: 2615 
  Graphics:  Device-1: NVIDIA GK106 [GeForce GTX 660] vendor: Gigabyte driver: 
nvidia v: 460.39 bus ID: 01:00.0 
 chip ID: 10de:11c0 
 Display: x11 server: X.Org 1.20.9 driver: nvidia unloaded: 
fbdev,modesetting,nouveau,vesa compositor: marco 
 v: 1.24.0 resolution: 

[Kernel-packages] [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected

[Date Huang]

After reading log in #14, and some code from cloud-init and maas
I still cannot find any code that will let cloud-init try to install 
flash-kernel wtih zfsutils-linux.
and it seems the error because squashfs didn't have any kernel installed.
So `linux-version` cannot find any kernel version to pass to flash-kernel to 
process postinst script.
`Can't find /boot/vmlinuz- (see /tmp/flash-kernel-no-kernel-error.log)` $kvers 
is empty.

and as I know, squashfs only for temp utils?
It will create an environment for curtin to install real system into disk
Am I correct?

Do you have any custom cloud-init config for xgene?


> RE: EFI-STUB - GRUB is the default way to boot Ubuntu on EFI systems. Users 
> can choose to boot using EFI-STUB, but they can also remove any Recommended 
> packages. Adding grub-efi-arm64 to Recommends will also get arm64 on-par with 
> amd64, which also recommends GRUB.

Got it.

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

Title:
  curtin: install flash-kernel in arm64 UEFI unexpected

Status in cloud-images:
  Incomplete
Status in curtin package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I used APM Mustang which flash-kernel supported in u-boot mode.
  But I used it with UEFI environment.
  It will cause fatal error when I used ARM64 ubuntu live server ISO to install 
system.

  In code[1], this will not install `flash-kernel` for APM Mustang because of 
UEFI.
  So that means code[2] will not disable `flash-kernel` in target system, only 
disable `update-initramfs`.

  When curtin execute to `install_kernel` stage, code[3,4] will not install 
`flash-kernel` either.
  But in code[5], it will install `linux-generic`.
  `linux-generic` has a long dependency tree and it will get `flash-kernel` in 
Recommended field.
  Apt by default will install Recommended package before kernel is installed.[6]
  So it will still execute `zz-flash-kernel` and `flash-kernel` when installing 
kernel.
  But system didn't create any `initrd.img` ever because curtin disable 
`update-initramfs` in code[2].
  This will cause that `flash-kernel` cannot find `initrd.img.` and fail 
when installing it.

  This issue didn't effect all ARM64 UEFI platform because `flash-kernel` 
didn't support them and skip.[7]
  I'm not sure which is best solution for this.
  But I think we should apply PR-27 in `flash-kernel`[8] for enhancement and 
fix curtin process with this patch both.

  If we only apply PR-27, it should work fine as well because it will be 
skipped when detecting UEFI
  and install `flash-kernel` before `disable_update_initranfs` in ARM platform 
without UEFI.[9]

  [Patch-1,2,3] might have side effect.
  Picking one patch for curtin should be enough.
  But I need your advice for this to determine which one is better for curtin.
  There are two categories
  1. avoid installing flash-kernel if no need, [Patch1,2]
  2. always install flash-kernel in arm/arm64 and make sure it be installed 
before code[2] [Patch3]
  (I will attach patch in reply.)

  Thanks a lot
  Regards,
  Date

  [1] 
https://github.com/canonical/curtin/blob/master/curtin/deps/__init__.py#L57-L58
  [2] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L1693-L1699
  [3] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L365-L370
  [4] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L311-L327
  [5] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L372-L374
  [6] https://github.com/Debian/apt/blob/master/apt-pkg/init.cc#L132
  [7] 
https://salsa.debian.org/installer-team/flash-kernel/-/blob/master/functions#L787
  [8] https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/27
  [9] curtin will insert `flash-kernel` into `REQUIRED_EXECUTABLES` when system 
is arm/arm64 without UEFI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions

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

[Kernel-packages] [Bug 1915063] Re: Windows 10 wil not install using qemu-system-x86_64

[Kai-Heng Feng]

** Package changed: linux (Ubuntu) => qemu (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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1912509] Re: usci_acpi USBC000:00: PPM init failed (-110)

[retro]

Hi Vincent, I am interested in buying that laptop. Currently it works
well or do you have a problem with this model?

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Kernel-packages] [Bug 1919003] Re: Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3

[Roger Fischer]

My initial conclusion may not have been correct.

I now think that the fix in iproute2 4.15.0-2ubuntu1.3 made the problem
more apparent.

The Network Name Resolution service is not actually failing. It is being
stopped and restarted (based on the logs).

So the real problem seems to be a very aggressive approach to restarting
the Network Name Resolution service.

In our case, the DHCPClient request is not getting a response, yet the
Network Name Resolution service is still being restarted.

Mar 13 03:43:32 em-vf-ns1 dhclient[3443]: DHCPDISCOVER on nsblk01 to 
255.255.255.255 port 67 interval 5 (xid=0xe499a07d)
Mar 13 03:43:37 em-vf-ns1 dhclient[3443]: No DHCPOFFERS received.
Mar 13 03:43:37 em-vf-ns1 dhclient[3443]: No working leases in persistent 
database - sleeping.

Mar 13 03:43:37 em-vf-ns1 systemd[1]: Stopping Network Name Resolution...
Mar 13 03:43:37 em-vf-ns1 systemd[1]: Stopped Network Name Resolution.
Mar 13 03:43:37 em-vf-ns1 systemd[1]: Starting Network Name Resolution...
Mar 13 03:43:37 em-vf-ns1 systemd[1]: Started Network Name Resolution.
Mar 13 03:43:37 em-vf-ns1 systemd[1]: Starting 
resolvconf-pull-resolved.service...
Mar 13 03:43:37 em-vf-ns1 systemd[1]: Started resolvconf-pull-resolved.service.

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

Title:
  Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3

Status in iproute2 package in Ubuntu:
  New

Bug description:
  The following is repeated periodically in the syslog:

  Feb 28 20:25:02 em-cel1 systemd[1]: Started Network Name Resolution.
  Feb 28 20:25:02 em-cel1 systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Feb 28 20:25:02 em-cel1 systemd[1]: Started resolvconf-pull-resolved.service.
  Feb 28 20:25:19 em-cel1 systemd[1]: Stopping Network Name Resolution...
  Feb 28 20:25:19 em-cel1 systemd[1]: Stopped Network Name Resolution.
  Feb 28 20:25:19 em-cel1 systemd[1]: Starting Network Name Resolution...

  There is no log anywhere to indicate why the service failed.

  The service stopped failing when we downgraded iproute2 from
  4.15.0-2ubuntu1.3 to 4.15.0-2ubuntu1.1.

  The DHCPClient seems to be involved in the chain of events.

  At the same frequency as the service failures, we do an ifup on a non-
  auto dhcp interface. The ifup results in a DHCP request, which in this
  case does not get a response (the link to the DHCP server is down.

  When we stop the process that does the periodic ifup, the service
  remains up (with iproute2 4.15.0-2ubuntu1.3).

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

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

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Shatadru Banerjee]

I did not mention brightness issue. With 5.11.3 the brightness does not
work flawlessly however there are more serious problems. 1. External
monitor not detected via HDMI, 2. still the wifi is not stable, 3.
cannot switch to nvidia.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  

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

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

Title:
  kernel 5.4.0-53 (amd64) won't shut down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever using the "Shutdown" button in Linux Mint 20 Cinnamon, laptop GUI 
disappears until only a white cursor on black background appears. Cursor does 
not blink. No other messages or text.
  Same when using "shutdown" in terminal.

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

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

[Kernel-packages] [Bug 1904339] Re: kernel 5.4.0-53 (amd64) won't shut down

[Colin Watson]

** Project changed: canonical-identity-provider => 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/1904339

Title:
  kernel 5.4.0-53 (amd64) won't shut down

Status in linux package in Ubuntu:
  New

Bug description:
  Whenever using the "Shutdown" button in Linux Mint 20 Cinnamon, laptop GUI 
disappears until only a white cursor on black background appears. Cursor does 
not blink. No other messages or text.
  Same when using "shutdown" in terminal.

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

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

[Kernel-packages] [Bug 1904339] [NEW] kernel 5.4.0-53 (amd64) won't shut down

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Whenever using the "Shutdown" button in Linux Mint 20 Cinnamon, laptop GUI 
disappears until only a white cursor on black background appears. Cursor does 
not blink. No other messages or text.
Same when using "shutdown" in terminal.

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


** Tags: shutdown
-- 
kernel 5.4.0-53 (amd64) won't shut down
https://bugs.launchpad.net/bugs/1904339
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 1919003] [NEW] Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3

[Roger Fischer]

Public bug reported:

The following is repeated periodically in the syslog:

Feb 28 20:25:02 em-cel1 systemd[1]: Started Network Name Resolution.
Feb 28 20:25:02 em-cel1 systemd[1]: Starting resolvconf-pull-resolved.service...
Feb 28 20:25:02 em-cel1 systemd[1]: Started resolvconf-pull-resolved.service.
Feb 28 20:25:19 em-cel1 systemd[1]: Stopping Network Name Resolution...
Feb 28 20:25:19 em-cel1 systemd[1]: Stopped Network Name Resolution.
Feb 28 20:25:19 em-cel1 systemd[1]: Starting Network Name Resolution...

There is no log anywhere to indicate why the service failed.

The service stopped failing when we downgraded iproute2 from
4.15.0-2ubuntu1.3 to 4.15.0-2ubuntu1.1.

The DHCPClient seems to be involved in the chain of events.

At the same frequency as the service failures, we do an ifup on a non-
auto dhcp interface. The ifup results in a DHCP request, which in this
case does not get a response (the link to the DHCP server is down.

When we stop the process that does the periodic ifup, the service
remains up (with iproute2 4.15.0-2ubuntu1.3).

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

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

Title:
  Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3

Status in iproute2 package in Ubuntu:
  New

Bug description:
  The following is repeated periodically in the syslog:

  Feb 28 20:25:02 em-cel1 systemd[1]: Started Network Name Resolution.
  Feb 28 20:25:02 em-cel1 systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Feb 28 20:25:02 em-cel1 systemd[1]: Started resolvconf-pull-resolved.service.
  Feb 28 20:25:19 em-cel1 systemd[1]: Stopping Network Name Resolution...
  Feb 28 20:25:19 em-cel1 systemd[1]: Stopped Network Name Resolution.
  Feb 28 20:25:19 em-cel1 systemd[1]: Starting Network Name Resolution...

  There is no log anywhere to indicate why the service failed.

  The service stopped failing when we downgraded iproute2 from
  4.15.0-2ubuntu1.3 to 4.15.0-2ubuntu1.1.

  The DHCPClient seems to be involved in the chain of events.

  At the same frequency as the service failures, we do an ifup on a non-
  auto dhcp interface. The ifup results in a DHCP request, which in this
  case does not get a response (the link to the DHCP server is down.

  When we stop the process that does the periodic ifup, the service
  remains up (with iproute2 4.15.0-2ubuntu1.3).

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

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

[Kernel-packages] [Bug 1918994] [NEW] general protection fault on Ubuntu 4.15.0-1103.114~16.04.1-azure 4.15.18

[Eli Corrales]

Public bug reported:

Hello

The following kernel tainted scenario have been observed in Azure VMs.
This happened some weeks after the kernel was upgraded from
4.15.0-1098-azure to 4.15.0-1103-azure. Now, the VMs have been updated
to kernel 1106 and the issue has not been observed. but want to confirm
if there is a bug for the 1103 kernel which is causing this problem:

NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.6 LTS"
VERSION_ID="16.04"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

# cat /proc/version_signature
Ubuntu 4.15.0-1103.114~16.04.1-azure 4.15.18

BOOT_IMAGE=/boot/vmlinuz-4.15.0-1103-azure
*
[2057238.731281] general protection fault:  [#1] SMP PTI
[2057238.734885] Modules linked in: symap_custom_4_15_0_1103_azure_x86_64(POE) 
symev_custom_4_15_0_1103_azure_x86_64(OE) dccp_diag dccp unix_diag 
af_packet_diag netlink_diag udp_diag tcp_diag inet_diag iptable_filter 
ip6table_filter ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner 
iptable_security xt_conntrack nf_conntrack ip_tables x_tables binfmt_misc cmac 
arc4 md4 nls_utf8 cifs ccm fscache nls_iso8859_1 mlx4_en mlx4_core kvm_intel 
hv_balloon pci_hyperv kvm irqbypass serio_raw joydev ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel
[2057239.148068]  hid_hyperv aes_x86_64 hyperv_fb crypto_simd cfbfillrect 
glue_helper cfbimgblt cryptd hid cfbcopyarea hv_netvsc pata_acpi 
hyperv_keyboard hv_utils [last unloaded: 
symevrm_custom_4_15_0_1103_azure_x86_64]
[2057239.285231] CPU: 7 PID: 2548 Comm: filebeat Tainted: P   OE
4.15.0-1103-azure #114~16.04.1-Ubuntu
[2057239.359930] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090008  12/07/2018
[2057239.443494] RIP: 0010:kmem_cache_alloc+0x7a/0x1c0
[2057239.514702] RSP: 0018:a2b44bb0f970 EFLAGS: 00010206
[2057239.587510] RAX: 2cbecca03c1aa960 RBX:  RCX: 
9336d8a3c5a0
[2057239.670716] RDX: 002dc13a RSI: 01011200 RDI: 
000251c0
[2057239.748088] RBP: a2b44bb0f9a0 R08: 93371fde51c0 R09: 
0002
[2057239.829346] R10:  R11:  R12: 
01011200
[2057239.908118] R13: 2cbecca03c1aa960 R14: 9336df002a80 R15: 
9336df002a80
[2057239.988090] FS:  7ff2d7fff700() GS:93371fdc() 
knlGS:
[2057240.080218] CS:  0010 DS:  ES:  CR0: 80050033
[2057240.160992] CR2: 7fe528002948 CR3: 00107c902002 CR4: 
003706e0
[2057240.244702] DR0:  DR1:  DR2: 

[2057240.335323] DR3:  DR6: fffe0ff0 DR7: 
0400
[2057240.416496] Call Trace:
[2057240.490398]  ? mempool_alloc_slab+0x15/0x20
[2057240.574478]  mempool_alloc_slab+0x15/0x20
[2057240.661848]  mempool_alloc+0x73/0x180
[2057240.740075]  ? mempool_alloc_slab+0x15/0x20
[2057240.819037]  ? mempool_alloc+0x73/0x180
[2057240.904391]  bvec_alloc+0x90/0xf0
[2057240.985346]  bio_alloc_bioset+0x13b/0x1e0
[2057241.065039]  ext4_bio_write_page+0x3e9/0x550
[2057241.148063]  mpage_submit_page+0x58/0x70
[2057241.228960]  mpage_process_page_bufs+0x10e/0x120
[2057241.317256]  mpage_prepare_extent_to_map+0x21f/0x2f0
[2057241.400777]  ext4_writepages+0x47d/0xe50
[2057241.484080]  do_writepages+0x1f/0x70
[2057241.572104]  ? ext4_mark_inode_dirty+0x1d0/0x1d0
[2057241.675375]  ? do_writepages+0x1f/0x70
[2057241.756087]  __filemap_fdatawrite_range+0xd4/0x110
[2057241.840087]  file_write_and_wait_range+0x5a/0xb0
[2057241.924041]  ext4_sync_file+0x11d/0x420
[2057242.008030]  vfs_fsync_range+0x51/0xb0
[2057242.096269]  do_fsync+0x3d/0x70
[2057242.180084]  SyS_fdatasync+0x13/0x20
[2057242.262207]  do_syscall_64+0x80/0x1e0
[2057242.344070]  entry_SYSCALL_64_after_hwframe+0x41/0xa6
[2057242.433441] RIP: 0033:0xc6edf0
[2057242.516094] RSP: 002b:00c000318d50 EFLAGS: 0206 ORIG_RAX: 
004b
[2057242.616068] RAX: ffda RBX: 00c4a000 RCX: 
00c6edf0
[2057242.712115] RDX:  RSI:  RDI: 
0003
[2057242.812071] RBP: 00c000318d90 R08:  R09: 

[2057242.902700] R10:  R11: 0206 R12: 
01a8
[2057242.992107] R13: 01a7 R14: 0200 R15: 

[2057243.090260] Code: 50 08 65 4c 03 05 0f b4 fc 5a 49 83 78 10 00 4d 8b 28 0f 
84 0b 01 00 00 4d 85 ed 0f 84 02 01 00 00 49 63 47 20 49 8b 3f 4c 01 e8 <48> 8b 
18 49 33 9f 40 01 00 00 48 89 c1 48 0f c9 4c 89 e8 48 31 
[2057243.268154] RIP: kmem_cache_alloc+0x7a/0x1c0 

[Kernel-packages] [Bug 1918987] [NEW] Groovy update: upstream stable patchset 2021-03-12

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2021-03-12

Ported from the following upstream stable releases:
v5.4.96, v5.10.14,
v5.4.97, v5.10.15

   from git://git.kernel.org/

net: fec: put child node on error path
net: octeontx2: Make sure the buffer is 128 byte aligned
stmmac: intel: Configure EHL PSE0 GbE and PSE1 GbE to 32 bits DMA addressing
net: dsa: bcm_sf2: put device node before return
net: switchdev: don't set port_obj_info->handled true when -EOPNOTSUPP
ibmvnic: Ensure that CRQ entry read are correctly ordered
iommu/io-pgtable-arm: Support coherency for Mali LPAE
drm/panfrost: Support cache-coherent integrations
arm64: dts: meson: Describe G12b GPU as coherent
arm64: Fix kernel address detection of __is_lm_address()
arm64: Do not pass tagged addresses to __is_lm_address()
ARM: 9025/1: Kconfig: CPU_BIG_ENDIAN depends on !LD_IS_LLD
iommu/vt-d: Do not use flush-queue when caching-mode is on
phy: cpcap-usb: Fix warning for missing regulator_disable
tools/power/x86/intel-speed-select: Set scaling_max_freq to base_frequency
tools/power/x86/intel-speed-select: Set higher of cpuinfo_max_freq or 
base_frequency
platform/x86: touchscreen_dmi: Add swap-x-y quirk for Goodix touchscreen on 
Estar Beauty HD tablet
platform/x86: intel-vbtn: Support for tablet mode on Dell Inspiron 7352
locking/lockdep: Avoid noinstr warning for DEBUG_LOCKDEP
x86: __always_inline __{rd,wr}msr()
scsi: scsi_transport_srp: Don't block target in failfast state
scsi: libfc: Avoid invoking response handler twice if ep is already completed
scsi: fnic: Fix memleak in vnic_dev_init_devcmd2
ALSA: hda - add Intel DG1 PCI and HDMI ids
ALSA: hda: Add Alderlake-S PCI ID and HDMI codec vid
ALSA: hda: Add AlderLake-P PCI ID and HDMI codec vid
objtool: Don't add empty symbols to the rbtree
mac80211: fix incorrect strlen of .write in debugfs
mac80211: fix fast-rx encryption check
scsi: ibmvfc: Set default timeout to avoid crash during migration
i2c: tegra: Create i2c_writesl_vi() to use with VI I2C for filling TX FIFO
udf: fix the problem that the disc content is not displayed
nvme: check the PRINFO bit before deciding the host buffer length
nvme-rdma: avoid request double completion for concurrent nvme_rdma_timeout
nvme-tcp: avoid request double completion for concurrent nvme_tcp_timeout
nvme-pci: allow use of cmb on v1.4 controllers
nvmet: set right status on error in id-ns handler
platform/x86: thinkpad_acpi: Add P53/73 firmware to fan_quirk_table for dual 
fan control
selftests/powerpc: Only test lwm/stmw on big endian
drm/amd/display: Update dram_clock_change_latency for DCN2.1
drm/amd/display: Change function decide_dp_link_settings to avoid infinite 
looping
drm/amd/display: Use hardware sequencer functions for PG control
objtool: Don't fail the kernel build on fatal errors
x86/cpu: Add Lakefield, Alder Lake and Rocket Lake models to the to Intel CPU 
family
x86/cpu: Add another Alder Lake CPU to the Intel family
kthread: Extract KTHREAD_IS_PER_CPU
workqueue: Restrict affinity change to rescuer
Revert "Revert "block: end bio with BLK_STS_AGAIN in case of non-mq devs and 
REQ_NOWAIT""
ACPI: thermal: Do not call acpi_thermal_check() directly
UBUNTU: upstream stable to v5.4.96, v5.10.14
USB: serial: cp210x: add pid/vid for WSDA-200-USB
USB: serial: cp210x: add new VID/PID for supporting Teraoka AD2000
USB: serial: option: Adding support for Cinterion MV31
usb: host: xhci-plat: add priv quirk for skip PHY initialization
usb: host: xhci: mvebu: make USB 3.0 PHY optional for Armada 3720
USB: gadget: legacy: fix an error code in eth_bind()
usb: gadget: aspeed: add missing of_node_put
USB: usblp: don't call usb_set_interface if there's a single alt
usb: renesas_usbhs: Clear pipe running flag in usbhs_pkt_pop()
usb: dwc2: Fix endpoint direction check in ep_from_windex
usb: dwc3: fix clock issue during resume in OTG mode
usb: xhci-mtk: fix unreleased bandwidth data
usb: xhci-mtk: skip dropping bandwidth of unchecked endpoints
usb: xhci-mtk: break loop when find the endpoint to drop
ARM: OMAP1: OSK: fix ohci-omap breakage
arm64: dts: qcom: c630: keep both touchpad devices enabled
arm64: dts: amlogic: meson-g12: Set FL-adj property value
arm64: dts: rockchip: fix vopl iommu irq on px30
arm64: dts: rockchip: Use only supported PCIe link speed on Pinebook Pro
ARM: dts: stm32: Connect card-detect signal on DHCOM
ARM: dts: stm32: Disable WP on DHCOM uSD slot
um: virtio: free vu_dev only with the contained struct device
arm64: dts: meson: 

[Kernel-packages] [Bug 1899776] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

[surya]

It didn't work initially. But on building kernel with a patch given, it
started working fine.

https://launchpadlibrarian.net/500948605/0303-pinctrl-amd2.patch

Thanks for your supports.

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

Title:
   Lenovo ThinkBook 14-IML Touchpad not showing up in
  /proc/bus/input/devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Exactly the same issue as #1853277, in Groovy (5.8.0-22-generic
  #23-Ubuntu) but was advised to report a new bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-22-generic 5.8.0-22.23
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2131 F pulseaudio
   /dev/snd/controlC1:  tim2131 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Oct 14 13:15:38 2020
  InstallationDate: Installed on 2020-06-03 (132 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20RV
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-22-generic 
root=UUID=21f0ab04-8421-49d1-8ad3-39fea6ea8a74 ro rootflags=subvol=@ quiet 
splash i8042.nopnp=1 pci=nocrs vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-22-generic N/A
   linux-backports-modules-5.8.0-22-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-14 (0 days ago)
  dmi.bios.date: 06/19/2020
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CJCN29WW
  dmi.board.name: LVA/LVAB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrCJCN29WW:bd06/19/2020:br1.29:efr1.31:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr:
  dmi.product.family: Lenovo ThinkBook 14-IML
  dmi.product.name: 20RV
  dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML
  dmi.product.version: Lenovo ThinkBook 14-IML
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1861053] Re: no fatrace output in focal

[Seth Arnold]

I'm sorry I lost track of this bug.

fatrace is still acting strangely for me:

$ uname -a
Linux millbarge 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux
$ apt policy fatrace
fatrace:
  Installed: 0.13-2
  Candidate: 0.13-2
  Version table:
 *** 0.13-2 500
500 http://192.168.0.22/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
$ sudo fatrace
bash(3168468): RCO /snap/lxd/19766/etc/bash_completion.d/snap.lxd.lxc
bash(3168587): O /snap/lxd/19766/etc/bash_completion.d/snap.lxd.lxc
bash(3168587): RC /snap/lxd/19766/etc/bash_completion.d/snap.lxd.lxc


Those three bash_completion accesses were from opening three new
terminals, with three new bash sessions. Within one of the bash sessions
I ran cat /etc/passwd ; cat /tmp/poc.c ; cat /var/log/syslog -- none of
these files, nor processes used to access the files, showed up in
fatrace output.

Thanks

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

Title:
  no fatrace output in focal

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

Bug description:
  Hello, fatrace in focal doesn't seem to work for me in focal.

  Start fatrace in one terminal, and perform file operations in another
  terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.

  sarnold@millbarge:~$ sudo fatrace
  [sudo] password for sarnold: 
  ^Csarnold@millbarge:~$ sudo strace -yy fatrace
  execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
  brk(NULL)   = 0x55c9a1947000
  arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid 
argument)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
  mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) = 
0x7f3539b15000
  close(3)  = 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 
3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  fstat(3, {st_mode=S_IFREG|0755, 
st_size=2025032, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f3539b13000
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 
3, 0) = 0x7f3539922000
  mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x25000) = 0x7f3539947000
  mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x19d000) = 0x7f3539abf000
  mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1e6000) = 0x7f3539b09000
  mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
  mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
  mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
  mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
  munmap(0x7f3539b15000, 71040)   = 0
  getpid()= 120700
  fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) = 
3
  brk(NULL)   = 0x55c9a1947000
  brk(0x55c9a1968000) = 0x55c9a1968000
  openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) = 
4
  fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 
1024
  access("sysfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("proc", F_OK)= -1 ENOENT (No such file or 
directory)
  access("udev", F_OK)= -1 ENOENT (No such file or 
directory)
  access("devpts", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("rpool/ROOT/ubuntu", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("securityfs", F_OK)  = -1 ENOENT (No 

[Kernel-packages] [Bug 1912371] Re: [MIR] flashrom + libftdi

[William Wilson]

I have reviewed flashrom along with fwupd and I don't see anything that
looks like it will cause problems. The flashrom documentation recommends
using vendors' flashing utilities when possible for laptops, and there
is a link to that page of the documentation in the manpage.

I have attached a debdiff to this comment that addresses several other concerns 
about this MIR. The attached debdiff
  1) Adds the build time unit tests to the meson build
  2) Adds a simple test script that operates on an emulated
 chip without sudo privileges. This runs as an autopkgtest
  3) Removes the warning about command line syntax change
 from the manpage
  4) Adds a comment on the stability of this program to the manpage
  5) Adds a .symbols file for libflashrom1

** Patch added: "flashrom MIR"
   
https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+attachment/5476160/+files/lp1912371.debdiff

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

Title:
  [MIR] flashrom + libftdi

Status in flashrom package in Ubuntu:
  New
Status in libftdi package in Ubuntu:
  New

Bug description:
  [Summary]
  Further review will be needed. The Package does not have a test suite that 
runs as autopkgtest.

  [Availability]
  Currently in universe.

  [Duplication]
  There is no other package in main providing the same functionality.

  [Rationale]
  fwupd depends on libflashrom1 for its flashrom plugin, something that's 
required to update Coreboot firmware.

  [Security]
  No CVE's, but due to the nature of the package security should review.

  [Quality Assurance]
  Package builds and runs easily

  [Dependencies]
  N/A

  [Standards Compliance]
  Complies with FHS, though the organization of files in the source package 
could be organized better.

  [Common blockers]
  flashrom does NOT have a test suite that runs at build time.
  flashrom does NOT have a test suite that runs as autopkgtest.

  [Maintenance]
  Actively maintained - https://github.com/flashrom/flashrom
  Packaging - https://salsa.debian.org/myczko-guest/flashrom.git

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

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

[Kernel-packages] [Bug 1915063] Re: Windows 10 wil not install using qemu-system-x86_64

[Mark Pearson]

We believe that the latest version of Windows doesn't play nice with the
older version of QEMU - it seems Windows is broken somewhere between
4.2.0-2 and 5.0.0-6 on AMD Ryzen based processors (which is what we have
on the P620).

What are the recommendations for the best way for a Ubuntu customer to
get going again, with an updated version of QEMU?

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

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected

[dann frazier]

Unfortunately dropping flash-kernel from cloud-images causes xgene-uboot
deployment failures, see attached log.


** Changed in: cloud-images
   Status: New => Incomplete

** Attachment added: 
"log_m400_failed_deploy_focal-ms10-35-mcdivittB0-kernel.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918427/+attachment/5476159/+files/log_m400_failed_deploy_focal-ms10-35-mcdivittB0-kernel.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/1918427

Title:
  curtin: install flash-kernel in arm64 UEFI unexpected

Status in cloud-images:
  Incomplete
Status in curtin package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I used APM Mustang which flash-kernel supported in u-boot mode.
  But I used it with UEFI environment.
  It will cause fatal error when I used ARM64 ubuntu live server ISO to install 
system.

  In code[1], this will not install `flash-kernel` for APM Mustang because of 
UEFI.
  So that means code[2] will not disable `flash-kernel` in target system, only 
disable `update-initramfs`.

  When curtin execute to `install_kernel` stage, code[3,4] will not install 
`flash-kernel` either.
  But in code[5], it will install `linux-generic`.
  `linux-generic` has a long dependency tree and it will get `flash-kernel` in 
Recommended field.
  Apt by default will install Recommended package before kernel is installed.[6]
  So it will still execute `zz-flash-kernel` and `flash-kernel` when installing 
kernel.
  But system didn't create any `initrd.img` ever because curtin disable 
`update-initramfs` in code[2].
  This will cause that `flash-kernel` cannot find `initrd.img.` and fail 
when installing it.

  This issue didn't effect all ARM64 UEFI platform because `flash-kernel` 
didn't support them and skip.[7]
  I'm not sure which is best solution for this.
  But I think we should apply PR-27 in `flash-kernel`[8] for enhancement and 
fix curtin process with this patch both.

  If we only apply PR-27, it should work fine as well because it will be 
skipped when detecting UEFI
  and install `flash-kernel` before `disable_update_initranfs` in ARM platform 
without UEFI.[9]

  [Patch-1,2,3] might have side effect.
  Picking one patch for curtin should be enough.
  But I need your advice for this to determine which one is better for curtin.
  There are two categories
  1. avoid installing flash-kernel if no need, [Patch1,2]
  2. always install flash-kernel in arm/arm64 and make sure it be installed 
before code[2] [Patch3]
  (I will attach patch in reply.)

  Thanks a lot
  Regards,
  Date

  [1] 
https://github.com/canonical/curtin/blob/master/curtin/deps/__init__.py#L57-L58
  [2] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L1693-L1699
  [3] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L365-L370
  [4] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L311-L327
  [5] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L372-L374
  [6] https://github.com/Debian/apt/blob/master/apt-pkg/init.cc#L132
  [7] 
https://salsa.debian.org/installer-team/flash-kernel/-/blob/master/functions#L787
  [8] https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/27
  [9] curtin will insert `flash-kernel` into `REQUIRED_EXECUTABLES` when system 
is arm/arm64 without UEFI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions

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

[Kernel-packages] [Bug 1899776] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

[surya]

Hi, I tried all the mentioned kernels on my lenovo ideapad gaming 3 and
I can see the touchpad in devices list but none of the solution worked
even the one in the previous thread too.

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

Title:
   Lenovo ThinkBook 14-IML Touchpad not showing up in
  /proc/bus/input/devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Exactly the same issue as #1853277, in Groovy (5.8.0-22-generic
  #23-Ubuntu) but was advised to report a new bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-22-generic 5.8.0-22.23
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2131 F pulseaudio
   /dev/snd/controlC1:  tim2131 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Oct 14 13:15:38 2020
  InstallationDate: Installed on 2020-06-03 (132 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20RV
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-22-generic 
root=UUID=21f0ab04-8421-49d1-8ad3-39fea6ea8a74 ro rootflags=subvol=@ quiet 
splash i8042.nopnp=1 pci=nocrs vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-22-generic N/A
   linux-backports-modules-5.8.0-22-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-14 (0 days ago)
  dmi.bios.date: 06/19/2020
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CJCN29WW
  dmi.board.name: LVA/LVAB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrCJCN29WW:bd06/19/2020:br1.29:efr1.31:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr:
  dmi.product.family: Lenovo ThinkBook 14-IML
  dmi.product.name: 20RV
  dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML
  dmi.product.version: Lenovo ThinkBook 14-IML
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1918974] [NEW] Focal update: v5.4.102 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.4.102 upstream stable release
   from git://git.kernel.org/

vmlinux.lds.h: add DWARF v5 sections
kvm: x86: replace kvm_spec_ctrl_test_value with runtime test on the host
debugfs: be more robust at handling improper input in debugfs_lookup()
debugfs: do not attempt to create a new file before the filesystem is initalized
kdb: Make memory allocations more robust
PCI: qcom: Use PHY_REFCLK_USE_PAD only for ipq8064
PCI: Decline to resize resources if boot config must be preserved
virt: vbox: Do not use wait_event_interruptible when called from kernel context
bfq: Avoid false bfq queue merging
ALSA: usb-audio: Fix PCM buffer allocation in non-vmalloc mode
MIPS: vmlinux.lds.S: add missing PAGE_ALIGNED_DATA() section
random: fix the RNDRESEEDCRNG ioctl
ath10k: Fix error handling in case of CE pipe init failure
Bluetooth: btqcomsmd: Fix a resource leak in error handling paths in the probe 
function
Bluetooth: hci_uart: Fix a race for write_work scheduling
Bluetooth: Fix initializing response id after clearing struct
ARM: dts: exynos: correct PMIC interrupt trigger level on Artik 5
ARM: dts: exynos: correct PMIC interrupt trigger level on Monk
ARM: dts: exynos: correct PMIC interrupt trigger level on Rinato
ARM: dts: exynos: correct PMIC interrupt trigger level on Spring
ARM: dts: exynos: correct PMIC interrupt trigger level on Arndale Octa
ARM: dts: exynos: correct PMIC interrupt trigger level on Odroid XU3 family
arm64: dts: exynos: correct PMIC interrupt trigger level on TM2
arm64: dts: exynos: correct PMIC interrupt trigger level on Espresso
memory: mtk-smi: Fix PM usage counter unbalance in mtk_smi ops
bpf: Add bpf_patch_call_args prototype to include/linux/bpf.h
bpf: Avoid warning when re-casting __bpf_call_base into __bpf_call_base_args
arm64: dts: allwinner: A64: properly connect USB PHY to port 0
arm64: dts: allwinner: H6: properly connect USB PHY to port 0
arm64: dts: allwinner: Drop non-removable from SoPine/LTS SD card
arm64: dts: allwinner: H6: Allow up to 150 MHz MMC bus frequency
arm64: dts: allwinner: A64: Limit MMC2 bus frequency to 150 MHz
cpufreq: brcmstb-avs-cpufreq: Free resources in error path
cpufreq: brcmstb-avs-cpufreq: Fix resource leaks in ->remove()
ACPICA: Fix exception code class checks
usb: gadget: u_audio: Free requests only after callback
Bluetooth: drop HCI device reference before return
Bluetooth: Put HCI device if inquiry procedure interrupts
memory: ti-aemif: Drop child node when jumping out loop
ARM: dts: Configure missing thermal interrupt for 4430
usb: dwc2: Do not update data length if it is 0 on inbound transfers
usb: dwc2: Abort transaction after errors with unknown reason
usb: dwc2: Make "trimming xfer length" a debug message
staging: rtl8723bs: wifi_regd.c: Fix incorrect number of regulatory rules
ARM: dts: armada388-helios4: assign pinctrl to LEDs
ARM: dts: armada388-helios4: assign pinctrl to each fan
arm64: dts: armada-3720-turris-mox: rename u-boot mtd partition to a53-firmware
Bluetooth: btusb: Fix memory leak in btusb_mtk_wmt_recv
arm64: dts: msm8916: Fix reserved and rfsa nodes unit address
ARM: s3c: fix fiq for clang IAS
soc: aspeed: snoop: Add clock control logic
bpf_lru_list: Read double-checked variable once without lock
ath9k: fix data bus crash when setting nf_override via debugfs
ibmvnic: Set to CLOSED state even on error
bnxt_en: reverse order of TX disable and carrier off
xen/netback: fix spurious event detection for common event case
mac80211: fix potential overflow when multiplying to u32 integers
bpf: Fix bpf_fib_lookup helper MTU check for SKB ctx
tcp: fix SO_RCVLOWAT related hangs under mem pressure
net: axienet: Handle deferred probe on clock properly
cxgb4/chtls/cxgbit: Keeping the max ofld immediate data size same in cxgb4 and 
ulds
b43: N-PHY: Fix the update of coef for the PHY revision >= 3case
ibmvnic: add memory barrier to protect long term buffer
ibmvnic: skip send_request_unmap for timeout reset
net: amd-xgbe: Reset the PHY rx data path when mailbox command timeout
net: amd-xgbe: Fix NETDEV WATCHDOG transmit queue timeout warning
net: amd-xgbe: Reset link when the link never comes back
net: amd-xgbe: Fix network fluctuations when using 1G BELFUSE SFP
net: mvneta: Remove per-cpu queue mapping for Armada 3700
fbdev: aty: SPARC64 requires FB_ATY_CT
drm/gma500: Fix error return code in psb_driver_load()
gma500: clean up error handling in init
drm/fb-helper: Add missed unlocks in setcmap_legacy()
crypto: sun4i-ss - linearize buffers content must be kept
crypto: sun4i-ss - 

[Kernel-packages] [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected

[dann frazier]

** Attachment added: "curtin_userdata_ubuntu_arm64_generic_focal_somehostname"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918427/+attachment/5476155/+files/curtin_userdata_ubuntu_arm64_generic_focal_somehostname

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

Title:
  curtin: install flash-kernel in arm64 UEFI unexpected

Status in cloud-images:
  New
Status in curtin package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I used APM Mustang which flash-kernel supported in u-boot mode.
  But I used it with UEFI environment.
  It will cause fatal error when I used ARM64 ubuntu live server ISO to install 
system.

  In code[1], this will not install `flash-kernel` for APM Mustang because of 
UEFI.
  So that means code[2] will not disable `flash-kernel` in target system, only 
disable `update-initramfs`.

  When curtin execute to `install_kernel` stage, code[3,4] will not install 
`flash-kernel` either.
  But in code[5], it will install `linux-generic`.
  `linux-generic` has a long dependency tree and it will get `flash-kernel` in 
Recommended field.
  Apt by default will install Recommended package before kernel is installed.[6]
  So it will still execute `zz-flash-kernel` and `flash-kernel` when installing 
kernel.
  But system didn't create any `initrd.img` ever because curtin disable 
`update-initramfs` in code[2].
  This will cause that `flash-kernel` cannot find `initrd.img.` and fail 
when installing it.

  This issue didn't effect all ARM64 UEFI platform because `flash-kernel` 
didn't support them and skip.[7]
  I'm not sure which is best solution for this.
  But I think we should apply PR-27 in `flash-kernel`[8] for enhancement and 
fix curtin process with this patch both.

  If we only apply PR-27, it should work fine as well because it will be 
skipped when detecting UEFI
  and install `flash-kernel` before `disable_update_initranfs` in ARM platform 
without UEFI.[9]

  [Patch-1,2,3] might have side effect.
  Picking one patch for curtin should be enough.
  But I need your advice for this to determine which one is better for curtin.
  There are two categories
  1. avoid installing flash-kernel if no need, [Patch1,2]
  2. always install flash-kernel in arm/arm64 and make sure it be installed 
before code[2] [Patch3]
  (I will attach patch in reply.)

  Thanks a lot
  Regards,
  Date

  [1] 
https://github.com/canonical/curtin/blob/master/curtin/deps/__init__.py#L57-L58
  [2] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L1693-L1699
  [3] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L365-L370
  [4] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L311-L327
  [5] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L372-L374
  [6] https://github.com/Debian/apt/blob/master/apt-pkg/init.cc#L132
  [7] 
https://salsa.debian.org/installer-team/flash-kernel/-/blob/master/functions#L787
  [8] https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/27
  [9] curtin will insert `flash-kernel` into `REQUIRED_EXECUTABLES` when system 
is arm/arm64 without UEFI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions

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

[Kernel-packages] [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected

[dann frazier]

In case it helps, attached is the MAAS preseed I used for testing the
PPA kernel w/ the updated Recommends. I also removed flash-kernel from
the corresponding MAAS cloud image by locally unsquashfs/purge flash-
kernel/mksquashfs and dd'ing back over the existing image.

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  curtin: install flash-kernel in arm64 UEFI unexpected

Status in cloud-images:
  New
Status in curtin package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I used APM Mustang which flash-kernel supported in u-boot mode.
  But I used it with UEFI environment.
  It will cause fatal error when I used ARM64 ubuntu live server ISO to install 
system.

  In code[1], this will not install `flash-kernel` for APM Mustang because of 
UEFI.
  So that means code[2] will not disable `flash-kernel` in target system, only 
disable `update-initramfs`.

  When curtin execute to `install_kernel` stage, code[3,4] will not install 
`flash-kernel` either.
  But in code[5], it will install `linux-generic`.
  `linux-generic` has a long dependency tree and it will get `flash-kernel` in 
Recommended field.
  Apt by default will install Recommended package before kernel is installed.[6]
  So it will still execute `zz-flash-kernel` and `flash-kernel` when installing 
kernel.
  But system didn't create any `initrd.img` ever because curtin disable 
`update-initramfs` in code[2].
  This will cause that `flash-kernel` cannot find `initrd.img.` and fail 
when installing it.

  This issue didn't effect all ARM64 UEFI platform because `flash-kernel` 
didn't support them and skip.[7]
  I'm not sure which is best solution for this.
  But I think we should apply PR-27 in `flash-kernel`[8] for enhancement and 
fix curtin process with this patch both.

  If we only apply PR-27, it should work fine as well because it will be 
skipped when detecting UEFI
  and install `flash-kernel` before `disable_update_initranfs` in ARM platform 
without UEFI.[9]

  [Patch-1,2,3] might have side effect.
  Picking one patch for curtin should be enough.
  But I need your advice for this to determine which one is better for curtin.
  There are two categories
  1. avoid installing flash-kernel if no need, [Patch1,2]
  2. always install flash-kernel in arm/arm64 and make sure it be installed 
before code[2] [Patch3]
  (I will attach patch in reply.)

  Thanks a lot
  Regards,
  Date

  [1] 
https://github.com/canonical/curtin/blob/master/curtin/deps/__init__.py#L57-L58
  [2] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L1693-L1699
  [3] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L365-L370
  [4] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L311-L327
  [5] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L372-L374
  [6] https://github.com/Debian/apt/blob/master/apt-pkg/init.cc#L132
  [7] 
https://salsa.debian.org/installer-team/flash-kernel/-/blob/master/functions#L787
  [8] https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/27
  [9] curtin will insert `flash-kernel` into `REQUIRED_EXECUTABLES` when system 
is arm/arm64 without UEFI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions

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

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

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

Title:
  curtin: install flash-kernel in arm64 UEFI unexpected

Status in cloud-images:
  New
Status in curtin package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I used APM Mustang which flash-kernel supported in u-boot mode.
  But I used it with UEFI environment.
  It will cause fatal error when I used ARM64 ubuntu live server ISO to install 
system.

  In code[1], this will not install `flash-kernel` for APM Mustang because of 
UEFI.
  So that means code[2] will not disable `flash-kernel` in target system, only 
disable `update-initramfs`.

  When curtin execute to `install_kernel` stage, code[3,4] will not install 
`flash-kernel` either.
  But in code[5], it will install `linux-generic`.
  `linux-generic` has a long dependency tree and it will get `flash-kernel` in 
Recommended field.
  Apt by default will install Recommended package before kernel is installed.[6]
  So it will still execute `zz-flash-kernel` and `flash-kernel` when installing 
kernel.
  But system didn't create any `initrd.img` ever because curtin disable 
`update-initramfs` in code[2].
  This will cause that `flash-kernel` cannot find `initrd.img.` and fail 
when installing it.

  This issue didn't effect all ARM64 UEFI platform because `flash-kernel` 
didn't support them and skip.[7]
  I'm not sure which is best solution for this.
  But I think we should apply PR-27 in `flash-kernel`[8] for enhancement and 
fix curtin process with this patch both.

  If we only apply PR-27, it should work fine as well because it will be 
skipped when detecting UEFI
  and install `flash-kernel` before `disable_update_initranfs` in ARM platform 
without UEFI.[9]

  [Patch-1,2,3] might have side effect.
  Picking one patch for curtin should be enough.
  But I need your advice for this to determine which one is better for curtin.
  There are two categories
  1. avoid installing flash-kernel if no need, [Patch1,2]
  2. always install flash-kernel in arm/arm64 and make sure it be installed 
before code[2] [Patch3]
  (I will attach patch in reply.)

  Thanks a lot
  Regards,
  Date

  [1] 
https://github.com/canonical/curtin/blob/master/curtin/deps/__init__.py#L57-L58
  [2] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L1693-L1699
  [3] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L365-L370
  [4] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L311-L327
  [5] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L372-L374
  [6] https://github.com/Debian/apt/blob/master/apt-pkg/init.cc#L132
  [7] 
https://salsa.debian.org/installer-team/flash-kernel/-/blob/master/functions#L787
  [8] https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/27
  [9] curtin will insert `flash-kernel` into `REQUIRED_EXECUTABLES` when system 
is arm/arm64 without UEFI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions

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

[Kernel-packages] [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected

[dann frazier]

I tested this locally by creating a MAAS preseed that adds my PPA. And
it works sort of. The kernel no longer causes flash-kernel to be
installed, but unfortunately flash-kernel is *pre-baked* in the arm*
cloud images, so we'd have to remove it from them too.

RE: EFI-STUB - GRUB is the default way to boot Ubuntu on EFI systems.
Users can choose to boot using EFI-STUB, but they can also remove any
Recommended packages. Adding grub-efi-arm64 to Recommends will also get
arm64 on-par with amd64, which also recommends GRUB.

** Also affects: cloud-images
   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/1918427

Title:
  curtin: install flash-kernel in arm64 UEFI unexpected

Status in cloud-images:
  New
Status in curtin package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I used APM Mustang which flash-kernel supported in u-boot mode.
  But I used it with UEFI environment.
  It will cause fatal error when I used ARM64 ubuntu live server ISO to install 
system.

  In code[1], this will not install `flash-kernel` for APM Mustang because of 
UEFI.
  So that means code[2] will not disable `flash-kernel` in target system, only 
disable `update-initramfs`.

  When curtin execute to `install_kernel` stage, code[3,4] will not install 
`flash-kernel` either.
  But in code[5], it will install `linux-generic`.
  `linux-generic` has a long dependency tree and it will get `flash-kernel` in 
Recommended field.
  Apt by default will install Recommended package before kernel is installed.[6]
  So it will still execute `zz-flash-kernel` and `flash-kernel` when installing 
kernel.
  But system didn't create any `initrd.img` ever because curtin disable 
`update-initramfs` in code[2].
  This will cause that `flash-kernel` cannot find `initrd.img.` and fail 
when installing it.

  This issue didn't effect all ARM64 UEFI platform because `flash-kernel` 
didn't support them and skip.[7]
  I'm not sure which is best solution for this.
  But I think we should apply PR-27 in `flash-kernel`[8] for enhancement and 
fix curtin process with this patch both.

  If we only apply PR-27, it should work fine as well because it will be 
skipped when detecting UEFI
  and install `flash-kernel` before `disable_update_initranfs` in ARM platform 
without UEFI.[9]

  [Patch-1,2,3] might have side effect.
  Picking one patch for curtin should be enough.
  But I need your advice for this to determine which one is better for curtin.
  There are two categories
  1. avoid installing flash-kernel if no need, [Patch1,2]
  2. always install flash-kernel in arm/arm64 and make sure it be installed 
before code[2] [Patch3]
  (I will attach patch in reply.)

  Thanks a lot
  Regards,
  Date

  [1] 
https://github.com/canonical/curtin/blob/master/curtin/deps/__init__.py#L57-L58
  [2] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L1693-L1699
  [3] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L365-L370
  [4] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L311-L327
  [5] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L372-L374
  [6] https://github.com/Debian/apt/blob/master/apt-pkg/init.cc#L132
  [7] 
https://salsa.debian.org/installer-team/flash-kernel/-/blob/master/functions#L787
  [8] https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/27
  [9] curtin will insert `flash-kernel` into `REQUIRED_EXECUTABLES` when system 
is arm/arm64 without UEFI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions

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

[Kernel-packages] [Bug 1861053] Re: no fatrace output in focal

[Martin Pitt]

** Changed in: fatrace (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/1861053

Title:
  no fatrace output in focal

Status in fatrace package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, fatrace in focal doesn't seem to work for me in focal.

  Start fatrace in one terminal, and perform file operations in another
  terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.

  sarnold@millbarge:~$ sudo fatrace
  [sudo] password for sarnold: 
  ^Csarnold@millbarge:~$ sudo strace -yy fatrace
  execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
  brk(NULL)   = 0x55c9a1947000
  arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid 
argument)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
  mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) = 
0x7f3539b15000
  close(3)  = 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 
3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  fstat(3, {st_mode=S_IFREG|0755, 
st_size=2025032, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f3539b13000
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 
3, 0) = 0x7f3539922000
  mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x25000) = 0x7f3539947000
  mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x19d000) = 0x7f3539abf000
  mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1e6000) = 0x7f3539b09000
  mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
  mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
  mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
  mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
  munmap(0x7f3539b15000, 71040)   = 0
  getpid()= 120700
  fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) = 
3
  brk(NULL)   = 0x55c9a1947000
  brk(0x55c9a1968000) = 0x55c9a1968000
  openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) = 
4
  fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 
1024
  access("sysfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("proc", F_OK)= -1 ENOENT (No such file or 
directory)
  access("udev", F_OK)= -1 ENOENT (No such file or 
directory)
  access("devpts", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("rpool/ROOT/ubuntu", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("securityfs", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("cgroup2", F_OK) = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("pstore", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("efivarfs", F_OK)= -1 ENOENT (No such file or 
directory)
  read(4, "de=700 0 0\ncgroup /sys/fs/cgroup"..., 1024) = 
1024
  access("none", F_OK)= -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  

[Kernel-packages] [Bug 1916486] Re: zfs_zrele_async can cause txg sync deadlocks

[Heitor Alves de Siqueira]

Verified for Xenial, using the ZFS test suite. I don't think Xenial
ships zfs-test, so I pulled it from upstream and ran it against the DKMS
drivers. No new regressions were reported.

ubuntu@z-rotomvm27:~$ dpkg -l | grep zfs-dkms
ii  zfs-dkms  0.6.5.6-0ubuntu29 
  amd64Native OpenZFS filesystem kernel modules for Linux


** Tags added: verification-done-xenial

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

Title:
  zfs_zrele_async can cause txg sync deadlocks

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Bionic:
  Fix Committed
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Groovy:
  Fix Committed
Status in zfs-linux source package in Hirsute:
  Fix Released
Status in zfs-linux package in Debian:
  New

Bug description:
  [Impact]
  TXG sync stalls, causing ZFS workloads to hang indefinitely

  [Description]
  For certain ZFS workloads, we can see hung task timeouts in the kernel logs 
due to a transaction group deadlock. Userspace process will hang and display 
stack traces similar to the one below:
  [49181.619711] clnt_server D0 21699  28868 0x0320
  [49181.619715] Call Trace:
  [49181.619725]  __schedule+0x24e/0x880
  [49181.619730]  schedule+0x2c/0x80
  [49181.619750]  cv_wait_common+0x11e/0x140 [spl]
  [49181.619763]  ? wait_woken+0x80/0x80
  [49181.619775]  __cv_wait+0x15/0x20 [spl]
  [49181.619872]  zil_commit.part.14+0x80/0x8c0 [zfs]
  [49181.619884]  ? _cond_resched+0x19/0x40
  [49181.619887]  ? mutex_lock+0x12/0x40
  [49181.619959]  zil_commit+0x17/0x20 [zfs]
  [49181.620026]  zfs_fsync+0x77/0xe0 [zfs]
  [49181.620093]  zpl_fsync+0x68/0xa0 [zfs]
  [49181.620100]  vfs_fsync_range+0x51/0xb0
  [49181.620105]  do_fsync+0x3d/0x70
  [49181.620109]  SyS_fsync+0x10/0x20
  [49181.620114]  do_syscall_64+0x73/0x130
  [49181.620119]  entry_SYSCALL_64_after_hwframe+0x41/0xa6

  We also might see a kworker thread blocking in the zfs writeback/evict path:
  [49181.881570] kworker/u17:3   D0  4915  2 0x8000
  [49181.881576] Workqueue: writeback wb_workfn (flush-zfs-10)
  [49181.881577] Call Trace:
  [49181.881580]  __schedule+0x24e/0x880
  [49181.881582]  ? atomic_t_wait+0x60/0x60
  [49181.881584]  schedule+0x2c/0x80
  [49181.881588]  bit_wait+0x11/0x60
  [49181.881592]  __wait_on_bit+0x4c/0x90
  [49181.881596]  ? atomic_t_wait+0x60/0x60
  [49181.881599]  __inode_wait_for_writeback+0xb9/0xf0
  [49181.881601]  ? bit_waitqueue+0x40/0x40
  [49181.881605]  inode_wait_for_writeback+0x26/0x40
  [49181.881609]  evict+0xb5/0x1a0
  [49181.881611]  iput+0x19c/0x230
  [49181.881648]  zfs_iput_async+0x1d/0x80 [zfs]
  [49181.881682]  zfs_get_data+0x1d4/0x2a0 [zfs]
  [49181.881718]  zil_commit.part.14+0x640/0x8c0 [zfs]
  [49181.881752]  zil_commit+0x17/0x20 [zfs]
  [49181.881784]  zpl_writepages+0xd5/0x160 [zfs]
  [49181.881787]  do_writepages+0x4b/0xe0
  [49181.881790]  __writeback_single_inode+0x45/0x350
  [49181.881792]  ? __writeback_single_inode+0x45/0x350
  [49181.881794]  writeback_sb_inodes+0x1d7/0x530
  [49181.881796]  wb_writeback+0xfb/0x300
  [49181.881799]  wb_workfn+0xad/0x400
  [49181.881800]  ? wb_workfn+0xad/0x400
  [49181.881803]  ? __switch_to_asm+0x35/0x70
  [49181.881809]  process_one_work+0x1de/0x420
  [49181.881811]  worker_thread+0x32/0x410
  [49181.881813]  kthread+0x121/0x140
  [49181.881815]  ? process_one_work+0x420/0x420
  [49181.881817]  ? kthread_create_worker_on_cpu+0x70/0x70
  [49181.881819]  ret_from_fork+0x35/0x40

  This is caused by a race between ZFS writeback and evict threads,
  usually during a transaction group sync operation. It's possible to
  have two iput() threads racing for the same inode: one of them
  scheduled async and the other executed synchronously as part of the
  writeback path. If the writeback thread tries to evict the inode while
  the async thread is running, it might re-enter the block layer for the
  same inode due to ZFS counters being in an inconsistent state. This
  then causes the kworker thread to stall the writeback, which in turn
  prevents the transaction group sync to complete and locks other ZFS
  threads.

  This is fixed by the upstream commit:
  - Fix zrele race in zrele_async that can cause hang (43eaef6de817) [0]

  [Test Case]
  Being a race condition, this issue has been hard to reproduce consistently. 
This has been reported on heavy I/O workloads, mixing file creation and 
deletion. We have some reports both from upstream and from Ubuntu users that 
this is usually reproducible on e.g. heavy SQL workloads or on complex 
ccache-enabled builds [1].

  [0] https://github.com/openzfs/zfs/pull/11530
  [1] https://github.com/openzfs/zfs/issues/11527

  [Regression Potential]
  The 

[Kernel-packages] [Bug 1916486] Re: zfs_zrele_async can cause txg sync deadlocks

[Heitor Alves de Siqueira]

Verified for Groovy, through the ZFS test suite. No new regressions were
reported.

ubuntu@racah:/usr/share/zfs$ dpkg -l | grep zfs-dkms
ii  zfs-dkms 0.8.4-1ubuntu11.2   
all  OpenZFS filesystem kernel modules for Linux


** Tags added: verification-done-groovy

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

Title:
  zfs_zrele_async can cause txg sync deadlocks

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Bionic:
  Fix Committed
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Groovy:
  Fix Committed
Status in zfs-linux source package in Hirsute:
  Fix Released
Status in zfs-linux package in Debian:
  New

Bug description:
  [Impact]
  TXG sync stalls, causing ZFS workloads to hang indefinitely

  [Description]
  For certain ZFS workloads, we can see hung task timeouts in the kernel logs 
due to a transaction group deadlock. Userspace process will hang and display 
stack traces similar to the one below:
  [49181.619711] clnt_server D0 21699  28868 0x0320
  [49181.619715] Call Trace:
  [49181.619725]  __schedule+0x24e/0x880
  [49181.619730]  schedule+0x2c/0x80
  [49181.619750]  cv_wait_common+0x11e/0x140 [spl]
  [49181.619763]  ? wait_woken+0x80/0x80
  [49181.619775]  __cv_wait+0x15/0x20 [spl]
  [49181.619872]  zil_commit.part.14+0x80/0x8c0 [zfs]
  [49181.619884]  ? _cond_resched+0x19/0x40
  [49181.619887]  ? mutex_lock+0x12/0x40
  [49181.619959]  zil_commit+0x17/0x20 [zfs]
  [49181.620026]  zfs_fsync+0x77/0xe0 [zfs]
  [49181.620093]  zpl_fsync+0x68/0xa0 [zfs]
  [49181.620100]  vfs_fsync_range+0x51/0xb0
  [49181.620105]  do_fsync+0x3d/0x70
  [49181.620109]  SyS_fsync+0x10/0x20
  [49181.620114]  do_syscall_64+0x73/0x130
  [49181.620119]  entry_SYSCALL_64_after_hwframe+0x41/0xa6

  We also might see a kworker thread blocking in the zfs writeback/evict path:
  [49181.881570] kworker/u17:3   D0  4915  2 0x8000
  [49181.881576] Workqueue: writeback wb_workfn (flush-zfs-10)
  [49181.881577] Call Trace:
  [49181.881580]  __schedule+0x24e/0x880
  [49181.881582]  ? atomic_t_wait+0x60/0x60
  [49181.881584]  schedule+0x2c/0x80
  [49181.881588]  bit_wait+0x11/0x60
  [49181.881592]  __wait_on_bit+0x4c/0x90
  [49181.881596]  ? atomic_t_wait+0x60/0x60
  [49181.881599]  __inode_wait_for_writeback+0xb9/0xf0
  [49181.881601]  ? bit_waitqueue+0x40/0x40
  [49181.881605]  inode_wait_for_writeback+0x26/0x40
  [49181.881609]  evict+0xb5/0x1a0
  [49181.881611]  iput+0x19c/0x230
  [49181.881648]  zfs_iput_async+0x1d/0x80 [zfs]
  [49181.881682]  zfs_get_data+0x1d4/0x2a0 [zfs]
  [49181.881718]  zil_commit.part.14+0x640/0x8c0 [zfs]
  [49181.881752]  zil_commit+0x17/0x20 [zfs]
  [49181.881784]  zpl_writepages+0xd5/0x160 [zfs]
  [49181.881787]  do_writepages+0x4b/0xe0
  [49181.881790]  __writeback_single_inode+0x45/0x350
  [49181.881792]  ? __writeback_single_inode+0x45/0x350
  [49181.881794]  writeback_sb_inodes+0x1d7/0x530
  [49181.881796]  wb_writeback+0xfb/0x300
  [49181.881799]  wb_workfn+0xad/0x400
  [49181.881800]  ? wb_workfn+0xad/0x400
  [49181.881803]  ? __switch_to_asm+0x35/0x70
  [49181.881809]  process_one_work+0x1de/0x420
  [49181.881811]  worker_thread+0x32/0x410
  [49181.881813]  kthread+0x121/0x140
  [49181.881815]  ? process_one_work+0x420/0x420
  [49181.881817]  ? kthread_create_worker_on_cpu+0x70/0x70
  [49181.881819]  ret_from_fork+0x35/0x40

  This is caused by a race between ZFS writeback and evict threads,
  usually during a transaction group sync operation. It's possible to
  have two iput() threads racing for the same inode: one of them
  scheduled async and the other executed synchronously as part of the
  writeback path. If the writeback thread tries to evict the inode while
  the async thread is running, it might re-enter the block layer for the
  same inode due to ZFS counters being in an inconsistent state. This
  then causes the kworker thread to stall the writeback, which in turn
  prevents the transaction group sync to complete and locks other ZFS
  threads.

  This is fixed by the upstream commit:
  - Fix zrele race in zrele_async that can cause hang (43eaef6de817) [0]

  [Test Case]
  Being a race condition, this issue has been hard to reproduce consistently. 
This has been reported on heavy I/O workloads, mixing file creation and 
deletion. We have some reports both from upstream and from Ubuntu users that 
this is usually reproducible on e.g. heavy SQL workloads or on complex 
ccache-enabled builds [1].

  [0] https://github.com/openzfs/zfs/pull/11530
  [1] https://github.com/openzfs/zfs/issues/11527

  [Regression Potential]
  The patch has been tested in the ZFS test suite and in production 
environments, so the potential for further regressions 

[Kernel-packages] [Bug 1916486] Re: zfs_zrele_async can cause txg sync deadlocks

[Heitor Alves de Siqueira]

Verified for Focal, through the ZFS test suite. No new regressions were
reported.

ubuntu@z-rotomvm29:/usr/share/zfs$ dpkg -l | rg zfs-dkms
ii  zfs-dkms 0.8.3-1ubuntu12.7 
all  OpenZFS filesystem kernel modules for Linux


** Tags added: verification-done-focal

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

Title:
  zfs_zrele_async can cause txg sync deadlocks

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Bionic:
  Fix Committed
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Groovy:
  Fix Committed
Status in zfs-linux source package in Hirsute:
  Fix Released
Status in zfs-linux package in Debian:
  New

Bug description:
  [Impact]
  TXG sync stalls, causing ZFS workloads to hang indefinitely

  [Description]
  For certain ZFS workloads, we can see hung task timeouts in the kernel logs 
due to a transaction group deadlock. Userspace process will hang and display 
stack traces similar to the one below:
  [49181.619711] clnt_server D0 21699  28868 0x0320
  [49181.619715] Call Trace:
  [49181.619725]  __schedule+0x24e/0x880
  [49181.619730]  schedule+0x2c/0x80
  [49181.619750]  cv_wait_common+0x11e/0x140 [spl]
  [49181.619763]  ? wait_woken+0x80/0x80
  [49181.619775]  __cv_wait+0x15/0x20 [spl]
  [49181.619872]  zil_commit.part.14+0x80/0x8c0 [zfs]
  [49181.619884]  ? _cond_resched+0x19/0x40
  [49181.619887]  ? mutex_lock+0x12/0x40
  [49181.619959]  zil_commit+0x17/0x20 [zfs]
  [49181.620026]  zfs_fsync+0x77/0xe0 [zfs]
  [49181.620093]  zpl_fsync+0x68/0xa0 [zfs]
  [49181.620100]  vfs_fsync_range+0x51/0xb0
  [49181.620105]  do_fsync+0x3d/0x70
  [49181.620109]  SyS_fsync+0x10/0x20
  [49181.620114]  do_syscall_64+0x73/0x130
  [49181.620119]  entry_SYSCALL_64_after_hwframe+0x41/0xa6

  We also might see a kworker thread blocking in the zfs writeback/evict path:
  [49181.881570] kworker/u17:3   D0  4915  2 0x8000
  [49181.881576] Workqueue: writeback wb_workfn (flush-zfs-10)
  [49181.881577] Call Trace:
  [49181.881580]  __schedule+0x24e/0x880
  [49181.881582]  ? atomic_t_wait+0x60/0x60
  [49181.881584]  schedule+0x2c/0x80
  [49181.881588]  bit_wait+0x11/0x60
  [49181.881592]  __wait_on_bit+0x4c/0x90
  [49181.881596]  ? atomic_t_wait+0x60/0x60
  [49181.881599]  __inode_wait_for_writeback+0xb9/0xf0
  [49181.881601]  ? bit_waitqueue+0x40/0x40
  [49181.881605]  inode_wait_for_writeback+0x26/0x40
  [49181.881609]  evict+0xb5/0x1a0
  [49181.881611]  iput+0x19c/0x230
  [49181.881648]  zfs_iput_async+0x1d/0x80 [zfs]
  [49181.881682]  zfs_get_data+0x1d4/0x2a0 [zfs]
  [49181.881718]  zil_commit.part.14+0x640/0x8c0 [zfs]
  [49181.881752]  zil_commit+0x17/0x20 [zfs]
  [49181.881784]  zpl_writepages+0xd5/0x160 [zfs]
  [49181.881787]  do_writepages+0x4b/0xe0
  [49181.881790]  __writeback_single_inode+0x45/0x350
  [49181.881792]  ? __writeback_single_inode+0x45/0x350
  [49181.881794]  writeback_sb_inodes+0x1d7/0x530
  [49181.881796]  wb_writeback+0xfb/0x300
  [49181.881799]  wb_workfn+0xad/0x400
  [49181.881800]  ? wb_workfn+0xad/0x400
  [49181.881803]  ? __switch_to_asm+0x35/0x70
  [49181.881809]  process_one_work+0x1de/0x420
  [49181.881811]  worker_thread+0x32/0x410
  [49181.881813]  kthread+0x121/0x140
  [49181.881815]  ? process_one_work+0x420/0x420
  [49181.881817]  ? kthread_create_worker_on_cpu+0x70/0x70
  [49181.881819]  ret_from_fork+0x35/0x40

  This is caused by a race between ZFS writeback and evict threads,
  usually during a transaction group sync operation. It's possible to
  have two iput() threads racing for the same inode: one of them
  scheduled async and the other executed synchronously as part of the
  writeback path. If the writeback thread tries to evict the inode while
  the async thread is running, it might re-enter the block layer for the
  same inode due to ZFS counters being in an inconsistent state. This
  then causes the kworker thread to stall the writeback, which in turn
  prevents the transaction group sync to complete and locks other ZFS
  threads.

  This is fixed by the upstream commit:
  - Fix zrele race in zrele_async that can cause hang (43eaef6de817) [0]

  [Test Case]
  Being a race condition, this issue has been hard to reproduce consistently. 
This has been reported on heavy I/O workloads, mixing file creation and 
deletion. We have some reports both from upstream and from Ubuntu users that 
this is usually reproducible on e.g. heavy SQL workloads or on complex 
ccache-enabled builds [1].

  [0] https://github.com/openzfs/zfs/pull/11530
  [1] https://github.com/openzfs/zfs/issues/11527

  [Regression Potential]
  The patch has been tested in the ZFS test suite and in production 
environments, so the potential for further 

[Kernel-packages] [Bug 1916486] Re: zfs_zrele_async can cause txg sync deadlocks

[Heitor Alves de Siqueira]

Verified for Bionic, through the ZFS test suite. No new regressions were
reported, and results of the test suite are the same as for the previous
version.

ubuntu@z-rotomvm28:/usr/share/zfs$ dpkg -l |grep zfs-dkms
ii  zfs-dkms   0.7.5-1ubuntu16.11   
   all  OpenZFS filesystem kernel modules for Linux

** Tags added: verification-done-bionic

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

Title:
  zfs_zrele_async can cause txg sync deadlocks

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Bionic:
  Fix Committed
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Groovy:
  Fix Committed
Status in zfs-linux source package in Hirsute:
  Fix Released
Status in zfs-linux package in Debian:
  New

Bug description:
  [Impact]
  TXG sync stalls, causing ZFS workloads to hang indefinitely

  [Description]
  For certain ZFS workloads, we can see hung task timeouts in the kernel logs 
due to a transaction group deadlock. Userspace process will hang and display 
stack traces similar to the one below:
  [49181.619711] clnt_server D0 21699  28868 0x0320
  [49181.619715] Call Trace:
  [49181.619725]  __schedule+0x24e/0x880
  [49181.619730]  schedule+0x2c/0x80
  [49181.619750]  cv_wait_common+0x11e/0x140 [spl]
  [49181.619763]  ? wait_woken+0x80/0x80
  [49181.619775]  __cv_wait+0x15/0x20 [spl]
  [49181.619872]  zil_commit.part.14+0x80/0x8c0 [zfs]
  [49181.619884]  ? _cond_resched+0x19/0x40
  [49181.619887]  ? mutex_lock+0x12/0x40
  [49181.619959]  zil_commit+0x17/0x20 [zfs]
  [49181.620026]  zfs_fsync+0x77/0xe0 [zfs]
  [49181.620093]  zpl_fsync+0x68/0xa0 [zfs]
  [49181.620100]  vfs_fsync_range+0x51/0xb0
  [49181.620105]  do_fsync+0x3d/0x70
  [49181.620109]  SyS_fsync+0x10/0x20
  [49181.620114]  do_syscall_64+0x73/0x130
  [49181.620119]  entry_SYSCALL_64_after_hwframe+0x41/0xa6

  We also might see a kworker thread blocking in the zfs writeback/evict path:
  [49181.881570] kworker/u17:3   D0  4915  2 0x8000
  [49181.881576] Workqueue: writeback wb_workfn (flush-zfs-10)
  [49181.881577] Call Trace:
  [49181.881580]  __schedule+0x24e/0x880
  [49181.881582]  ? atomic_t_wait+0x60/0x60
  [49181.881584]  schedule+0x2c/0x80
  [49181.881588]  bit_wait+0x11/0x60
  [49181.881592]  __wait_on_bit+0x4c/0x90
  [49181.881596]  ? atomic_t_wait+0x60/0x60
  [49181.881599]  __inode_wait_for_writeback+0xb9/0xf0
  [49181.881601]  ? bit_waitqueue+0x40/0x40
  [49181.881605]  inode_wait_for_writeback+0x26/0x40
  [49181.881609]  evict+0xb5/0x1a0
  [49181.881611]  iput+0x19c/0x230
  [49181.881648]  zfs_iput_async+0x1d/0x80 [zfs]
  [49181.881682]  zfs_get_data+0x1d4/0x2a0 [zfs]
  [49181.881718]  zil_commit.part.14+0x640/0x8c0 [zfs]
  [49181.881752]  zil_commit+0x17/0x20 [zfs]
  [49181.881784]  zpl_writepages+0xd5/0x160 [zfs]
  [49181.881787]  do_writepages+0x4b/0xe0
  [49181.881790]  __writeback_single_inode+0x45/0x350
  [49181.881792]  ? __writeback_single_inode+0x45/0x350
  [49181.881794]  writeback_sb_inodes+0x1d7/0x530
  [49181.881796]  wb_writeback+0xfb/0x300
  [49181.881799]  wb_workfn+0xad/0x400
  [49181.881800]  ? wb_workfn+0xad/0x400
  [49181.881803]  ? __switch_to_asm+0x35/0x70
  [49181.881809]  process_one_work+0x1de/0x420
  [49181.881811]  worker_thread+0x32/0x410
  [49181.881813]  kthread+0x121/0x140
  [49181.881815]  ? process_one_work+0x420/0x420
  [49181.881817]  ? kthread_create_worker_on_cpu+0x70/0x70
  [49181.881819]  ret_from_fork+0x35/0x40

  This is caused by a race between ZFS writeback and evict threads,
  usually during a transaction group sync operation. It's possible to
  have two iput() threads racing for the same inode: one of them
  scheduled async and the other executed synchronously as part of the
  writeback path. If the writeback thread tries to evict the inode while
  the async thread is running, it might re-enter the block layer for the
  same inode due to ZFS counters being in an inconsistent state. This
  then causes the kworker thread to stall the writeback, which in turn
  prevents the transaction group sync to complete and locks other ZFS
  threads.

  This is fixed by the upstream commit:
  - Fix zrele race in zrele_async that can cause hang (43eaef6de817) [0]

  [Test Case]
  Being a race condition, this issue has been hard to reproduce consistently. 
This has been reported on heavy I/O workloads, mixing file creation and 
deletion. We have some reports both from upstream and from Ubuntu users that 
this is usually reproducible on e.g. heavy SQL workloads or on complex 
ccache-enabled builds [1].

  [0] https://github.com/openzfs/zfs/pull/11530
  [1] https://github.com/openzfs/zfs/issues/11527

  [Regression Potential]
  The patch has been tested in 

[Kernel-packages] [Bug 1912905] Re: Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server image

[Dave Jones]

Due to a missing brcmfmac43455-sdio.raspberrypi,4-compute-module.txt
alias in linux-firmware-raspi2. The CM4's we'd encountered so far (and
which had been tested for WiFi compatibility were all requesting
brcmfmac43456-sdio.raspberrypi,4-compute-module.txt (note 43455 vs
43456) but it appears there's a couple of board revisions out there.
I'll add the necessary alias in linux-firmware-raspi2 for hirsute, then
we can see about SRU'ing this.

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

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

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

Title:
  Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server
  image

Status in linux-firmware-raspi2 package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in linux-firmware-raspi2 source package in Focal:
  New
Status in linux-raspi source package in Focal:
  Confirmed
Status in linux-firmware-raspi2 source package in Groovy:
  New
Status in linux-raspi source package in Groovy:
  Confirmed
Status in linux-firmware-raspi2 source package in Hirsute:
  New
Status in linux-raspi source package in Hirsute:
  New

Bug description:
  [Description]
  Can't find WLAN device on Raspberry Pi CM4L with 20.10 armhf preinstall 
server image.
  This only happens on armhf image.

  [Steps to reproduce]
  1. Flash image 
http://cdimage.ubuntu.com/ubuntu/releases/groovy/release/ubuntu-20.10-preinstalled-server-armhf+raspi.img.xz
  2. Boot into system
  5. Check wireless device using "ip a"

  [Expected result]
  Can't find WLAN device

  [Actual result]
  WLAN device works fine

  [Additional information]
  Hardware: RPI-CM4L
  Kernel Version: 5.8.0-1006-raspi, 5.8.0-1012-raspi, 5.8.0-1013-raspi

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

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

[Kernel-packages] [Bug 1917958] Re: Latest linux-generic package (kernel 4.15.0-136) doesn't work on HyperV Gen2 VM

[Marcelo Cerri]

Hi, Luiz.

Can you test if the same problem happens with the version in bionic-
proposed?

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

Title:
  Latest linux-generic package (kernel 4.15.0-136) doesn't work on
  HyperV Gen2 VM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 18.04 LTS 1&2 (so far tested), either when deploying a new
  VM (which pulls the latest linux-generic) or rebooting a VM (which
  updated the linux-generic under the cover which installs 4.15.0-136)
  will prevent the VM to boot.

  After reboot, will get stuck on /dev/sdX: clean, x / y files, k / m
  blocks.

  Using grub, selecting an older kernel, allow the VM to book without
  any issues.

  I manually installed kernel 4.15.0-135, however the issue doesn't
  repro.

  Finally I've verified that this repro on both Server 2016 and Server
  2019 versions of Windows...

  Output of /proc/version_signature (both on Server 2016/2019)
  Ubuntu 4.15.0-29.31-generic 4.15.18

  lspci -vnvn reported empty on this VM.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Screen goes black randomly after upgrade from Xubuntu 18.04.5 LTS to
  Xubuntu 20.04.2 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded to 20.04.2 LTS I've had a problem (about once a day)
  with my screen going black. The computer is not unresponsive, but the
  only way to wake the screen up is to close and open the laptop lid.
  External screen is not affected.

  I'm on a HP Elitebook 820 notebook.

  Searched journalctl and dmesg logs but I can't find anything relevant
  there, so suspecting this has to do with a change of display driver
  and/or settings in the new version.

  Please contact me if more info would be helpful. Wish you a great day!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-66-generic 5.4.0-66.74
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a  1350 F pulseaudio
   /dev/snd/controlC1:  a  1350 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Mar 12 15:26:46 2021
  HibernationDevice: RESUME=UUID=add5c1ba-194d-4f4d-af77-7049d2c84b9a
  InstallationDate: Installed on 2017-09-23 (1266 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 820 G1
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=be312993-03d0-453d-97c0-f598bedc47ae ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2021-01-13 (58 days ago)
  dmi.bios.date: 10/04/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.03
  dmi.board.name: 1991
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.48
  dmi.chassis.asset.tag: CNU3459W62
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.03:bd10/04/2013:svnHewlett-Packard:pnHPEliteBook820G1:pvrA3009DD10203:rvnHewlett-Packard:rn1991:rvrKBCVersion15.48:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 820 G1
  dmi.product.sku: D7V73AV
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1918714] Re: Fix close/open corner cases

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2021-March/118033.html

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

Title:
  Fix close/open corner cases

Status in linux package in Ubuntu:
  Invalid
Status in linux-azure-4.15 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure-4.15 source package in Bionic:
  In Progress

Bug description:
  SRU Justification

  [Impact]
  Microsoft has asked for these 3 patches to be applied to the linux-azure-4.15 
kernel.
  The code has changed significantly from 4.15 to 5.6, so the patches are
  quite different then current upstream. Hopefully I've captured the intent
  if not the function in those patches.

  [1] - Correct corner case where a close operation does not complete.
  [2] - Fix a race when an OPEN is cancelled.
  [3] - Fix a panic when allocating memory when a spinlock is held.

  
  [Test Case]
  none

  [Potential regression]
  These patches are all intended to accommodate boundary conditions. You 
shouldn't
  experience any regression under normal use.

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

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

[Kernel-packages] [Bug 1918940] [NEW] Screen goes black randomly after upgrade from Xubuntu 18.04.5 LTS to Xubuntu 20.04.2 LTS

[AlexW]

Public bug reported:

Since I upgraded to 20.04.2 LTS I've had a problem (about once a day)
with my screen going black. The computer is not unresponsive, but the
only way to wake the screen up is to close and open the laptop lid.
External screen is not affected.

I'm on a HP Elitebook 820 notebook.

Searched journalctl and dmesg logs but I can't find anything relevant
there, so suspecting this has to do with a change of display driver
and/or settings in the new version.

Please contact me if more info would be helpful. Wish you a great day!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-66-generic 5.4.0-66.74
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Uname: Linux 5.4.0-66-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  a  1350 F pulseaudio
 /dev/snd/controlC1:  a  1350 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Fri Mar 12 15:26:46 2021
HibernationDevice: RESUME=UUID=add5c1ba-194d-4f4d-af77-7049d2c84b9a
InstallationDate: Installed on 2017-09-23 (1266 days ago)
InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Hewlett-Packard HP EliteBook 820 G1
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=be312993-03d0-453d-97c0-f598bedc47ae ro text
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-66-generic N/A
 linux-backports-modules-5.4.0-66-generic  N/A
 linux-firmware1.187.9
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2021-01-13 (58 days ago)
dmi.bios.date: 10/04/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.03
dmi.board.name: 1991
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.48
dmi.chassis.asset.tag: CNU3459W62
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.03:bd10/04/2013:svnHewlett-Packard:pnHPEliteBook820G1:pvrA3009DD10203:rvnHewlett-Packard:rn1991:rvrKBCVersion15.48:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 820 G1
dmi.product.sku: D7V73AV
dmi.product.version: A3009DD10203
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug focal

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

Title:
  Screen goes black randomly after upgrade from Xubuntu 18.04.5 LTS to
  Xubuntu 20.04.2 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded to 20.04.2 LTS I've had a problem (about once a day)
  with my screen going black. The computer is not unresponsive, but the
  only way to wake the screen up is to close and open the laptop lid.
  External screen is not affected.

  I'm on a HP Elitebook 820 notebook.

  Searched journalctl and dmesg logs but I can't find anything relevant
  there, so suspecting this has to do with a change of display driver
  and/or settings in the new version.

  Please contact me if more info would be helpful. Wish you a great day!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-66-generic 5.4.0-66.74
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a  1350 F pulseaudio
   /dev/snd/controlC1:  a  1350 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Mar 12 15:26:46 2021
  HibernationDevice: RESUME=UUID=add5c1ba-194d-4f4d-af77-7049d2c84b9a
  InstallationDate: Installed on 2017-09-23 (1266 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 820 G1
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=be312993-03d0-453d-97c0-f598bedc47ae ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2021-01-13 (58 days ago)
  dmi.bios.date: 10/04/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.03
  dmi.board.name: 1991
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.48
  dmi.chassis.asset.tag: CNU3459W62
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.03:bd10/04/2013:svnHewlett-Packard:pnHPEliteBook820G1:pvrA3009DD10203:rvnHewlett-Packard:rn1991:rvrKBCVersion15.48:cvnHewlett-Packard:ct10:cvr:
  

[Kernel-packages] [Bug 1912905] Re: Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server image

[Juerg Haefliger]

Doesn't work on Focal with kernel 5.4 either. Both arm64 and armhf.

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

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

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

Title:
  Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server
  image

Status in linux-firmware-raspi2 package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in linux-firmware-raspi2 source package in Focal:
  New
Status in linux-raspi source package in Focal:
  Confirmed
Status in linux-firmware-raspi2 source package in Groovy:
  New
Status in linux-raspi source package in Groovy:
  Confirmed

Bug description:
  [Description]
  Can't find WLAN device on Raspberry Pi CM4L with 20.10 armhf preinstall 
server image.
  This only happens on armhf image.

  [Steps to reproduce]
  1. Flash image 
http://cdimage.ubuntu.com/ubuntu/releases/groovy/release/ubuntu-20.10-preinstalled-server-armhf+raspi.img.xz
  2. Boot into system
  5. Check wireless device using "ip a"

  [Expected result]
  Can't find WLAN device

  [Actual result]
  WLAN device works fine

  [Additional information]
  Hardware: RPI-CM4L
  Kernel Version: 5.8.0-1006-raspi, 5.8.0-1012-raspi, 5.8.0-1013-raspi

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

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

[Kernel-packages] [Bug 1912905] Re: Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server image

[Juerg Haefliger]

So on arm64 this works by accident because the kernel loads the fw file:
brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt

[   11.512059] brcmfmac: F1 signature read @0x1800=0x15264345
[   11.530710] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio 
for chip BCM4345/6
[   11.540495] usbcore: registered new interface driver brcmfmac
[   11.781454] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio 
for chip BCM4345/6
[   11.802739] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 23 
2020 02:19:54 version 7.45.206 (r725000 CY) FWID 01-88ee44ea


But on armhf it tries to load a non-existing fw file:
brcm/brcmfmac43455-sdio.raspberrypi,4-compute-module.txt


[   11.212993] brcmfmac: F1 signature read @0x1800=0x15264345
[   11.255150] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio 
for chip BCM4345/6
[   11.264126] usbcore: registered new interface driver brcmfmac
[   11.287281] brcmfmac mmc1:0001:1: Direct firmware load for 
brcm/brcmfmac43455-sdio.raspberrypi,4-compute-module.txt failed with error -2
[   11.301774] brcmfmac mmc1:0001:1: Direct firmware load for 
brcm/brcmfmac43455-sdio.txt failed with error -2
[   12.333944] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 
0x50


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

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

Title:
  Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server
  image

Status in linux-firmware-raspi2 package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in linux-firmware-raspi2 source package in Groovy:
  New
Status in linux-raspi source package in Groovy:
  Confirmed

Bug description:
  [Description]
  Can't find WLAN device on Raspberry Pi CM4L with 20.10 armhf preinstall 
server image.
  This only happens on armhf image.

  [Steps to reproduce]
  1. Flash image 
http://cdimage.ubuntu.com/ubuntu/releases/groovy/release/ubuntu-20.10-preinstalled-server-armhf+raspi.img.xz
  2. Boot into system
  5. Check wireless device using "ip a"

  [Expected result]
  Can't find WLAN device

  [Actual result]
  WLAN device works fine

  [Additional information]
  Hardware: RPI-CM4L
  Kernel Version: 5.8.0-1006-raspi, 5.8.0-1012-raspi, 5.8.0-1013-raspi

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

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

[Kernel-packages] [Bug 1917842] Re: Fix Lenovo ThinkStation P620 rear audio

[Kai-Heng Feng]

** Tags removed: verification-needed-focal
** Tags added: verification-done-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/1917842

Title:
  Fix Lenovo ThinkStation P620 rear audio

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Rear audio on Lenovo ThinkStation P620 stops working on newer kernel.

  [Fix]
  Use helper to the correct way to disable USB autosuspend. 

  [Test]
  With the patch applied, the rear audio on Lenovo ThinkStation P620 works
  again.

  [Where problems could occur]
  In a rather unlikely case, if any USB audio wrongly shared same device
  ID with P620' USB audios, this patch will disable autosuspend on it.
  However, it won't bring any functional impact.

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

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

[Kernel-packages] [Bug 1918927] [NEW] focal/linux-raspi: Upstream raspberrypi patchset 2021-03-02

[Juerg Haefliger]

Public bug reported:


Upstream raspberrypi patchset 2021-03-02

   Ported from the following raspberrypi branch:
  rpi-5.4.y

from https://github.com/raspberrypi/linux.git

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

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

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

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

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

Title:
  focal/linux-raspi: Upstream raspberrypi patchset 2021-03-02

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Focal:
  New

Bug description:
  
  Upstream raspberrypi patchset 2021-03-02

 Ported from the following raspberrypi branch:
rpi-5.4.y

  from https://github.com/raspberrypi/linux.git

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

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

[Kernel-packages] [Bug 1916811] Re: package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error exit

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to
  install/upgrade: installed nvidia-dkms-460 package post-installation
  script subprocess returned error exit status 10

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

Bug description:
  Just doing a package update through synaptic and this one failed.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-460 460.39-0ubuntu0.20.04.1
  Uname: Linux 5.10.17-051017-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb 24 17:54:25 2021
  ErrorMessage: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2020-05-24 (276 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: nvidia-graphics-drivers-460
  Title: package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: Upgraded to focal on 2021-02-17 (7 days ago)

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

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

[Kernel-packages] [Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM

[Po-Hsu Lin]

** Changed in: linux-kvm (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
  on B/C/D KVM

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Bionic:
  Fix Released
Status in linux-kvm source package in Cosmic:
  Won't Fix
Status in linux-kvm source package in Disco:
  Fix Released

Bug description:
  == SRU Justification ==
  Security team requires the CONFIG_LOCK_DOWN_KERNEL to be enabled in all of 
our kernels.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1811981-kvm-lockdown/
  This issue can be verified with test_410_config_lock_down_kernel
  test from q-r-t, the test will pass with the patched kernel.

  == Regression Potential ==
  Low, we already have this config enabled in the generic kernel.

  
  == Original bug report ==
  Kernel Version: 4.15.0-44.47

  This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
  Power8 and Power9

  FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
  Ensure kernel efi lockdown is enabled
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2668, in 
test_410_config_lock_down_kernel
  self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
    File "./test-kernel-security.py", line 207, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel 
config

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1811981/+subscriptions

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

[Kernel-packages] [Bug 1812159] Re: q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels

[Po-Hsu Lin]

** Changed in: linux-kvm (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM
  kernels

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Xenial:
  Fix Released
Status in linux-kvm source package in Bionic:
  Fix Released
Status in linux-kvm source package in Cosmic:
  Won't Fix
Status in linux-kvm source package in Disco:
  Fix Released

Bug description:
  == SRU Justification ==
  Security team requires the SCHED_STACK_END_CHECK config to be enabled
  on all of our kernel.

  The test_380_config_sched_stack_end_check test from q-r-t will fail on
  all the KVM kernels.

  Copied from the config help text:
  This option checks for a stack overrun on calls to schedule(). If the
  stack end location is found to be over written always panic as the
  content of the corrupted region can no longer be trusted. This is to
  ensure no erroneous behaviour occurs which could result in data
  corruption or a sporadic crash at a later stage once the region is
  examined. The runtime overhead introduced is minimal.

  == Test ==
  Test kernels could be found here: 
  https://people.canonical.com/~phlin/kernel/lp-1812159-kvm-sched-check/
  This issue case be verified with the test_380_config_sched_stack_end_check 
test from q-r-t, the test will pass with the patched kernel.

  == Regression Potential ==
  Low, the introduced runtime overhead is minimal, and it's already enabled in 
the generic kernel.

  == Original Bug report ==
  The test_380_config_sched_stack_end_check test failed on the Bionic
  KVM kernel

   FAIL: test_380_config_sched_stack_end_check 
(__main__.KernelSecurityConfigTest)
   Ensure SCHED_STACK_END_CHECK is set
   --
   Traceback (most recent call last):
   File "./test-kernel-security.py", line 2628, in 
test_380_config_sched_stack_end_check
   self.assertKernelConfig('SCHED_STACK_END_CHECK', expected)
   File "./test-kernel-security.py", line 207, in assertKernelConfig
   self.assertKernelConfigSet(name)
   File "./test-kernel-security.py", line 194, in assertKernelConfigSet
   '%s option was expected to be set in the kernel config' % name)
   AssertionError: SCHED_STACK_END_CHECK option was expected to be set in the 
kernel config

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 06:44:41 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1812796] Re: TRACE_syscall.ptrace_syscall_dropped in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC

[Po-Hsu Lin]

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

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

Title:
  TRACE_syscall.ptrace_syscall_dropped in seccomp from
  ubuntu_kernel_selftests failed on B/C PowerPC

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  == SRU Justification ==
  The TRACE_syscall.ptrace_syscall_dropped test in seccomp from 
ubuntu_kernel_selftests will fail on a Power8 node with B/C kernel.

  [ RUN  ] TRACE_syscall.ptrace_syscall_dropped
  seccomp_bpf.c:1808:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) == 
syscall(286) (18446744073709551615)
  TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13
  [ FAIL ] TRACE_syscall.ptrace_syscall_dropped

  == Fix ==
  * ed5f1326 (selftests/seccomp: Enhance per-arch ptrace syscall skip tests)

  This patch can be cherry-picked into B/C, and it's already in Disco.
  The ptrace_syscall_dropped will be changed into ptrace_syscall_faked, and a 
new ptrace_syscall_errno test will be added.

  == Test ==
  Patch tested with different arch (amd64 / power8 / arm64 / i386), the new 
test will pass on them except for PowerPC.

  Although the faked (bug 1829363) and errno (bug 1829359) test will
  fail on PowerPC, it's actually helping us to nail down a real issue in
  our kernel.

  == Regression Potential ==
  Low, changes limited to the testing tool in the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 22 04:30 seq
   crw-rw 1 root audio 116, 33 Jan 22 04:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: ppc64el
  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 Jan 22 06:09:34 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
  ProcLoadAvg: 0.13 0.34 0.23 1/1487 35882
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:43:28 UTC 
2018
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.694 GHz (cpu 152)
   max: 3.694 GHz (cpu 1)
   avg: 3.694 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

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

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

[Kernel-packages] [Bug 1813118] Re: alignment test in powerpc from ubuntu_kernel_selftests failed on B/C Power9

[Po-Hsu Lin]

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

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

Title:
  alignment test in powerpc from ubuntu_kernel_selftests failed on B/C
  Power9

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  == Justification ==
  The copy_unaligned / paste_unaligned / paste_last_unaligned test in 
powerpc/alignment will fail on a Power9 node as which implements ISA 3.0B, but 
the test was designed base on ISA 3.0.

  From the commit message:
  This is a test of the ISA 3.0 "copy" instruction. That instruction has
  an L field, which if set to 1 specifies that "the instruction
  identifies the beginning of a move group" (pp 858). That's also
  referred to as "copy first" vs "copy".

  In ISA 3.0B the copy instruction does not have an L field, and the
  corresponding bit in the instruction must be set to 1.

  This test is generating a "copy" instruction, not a "copy first", and
  so on Power9 (which implements 3.0B), this results in an illegal
  instruction.

  So just drop the test entirely. We still have copy_first_unaligned to
  test the "copy first" behaviour.

  == Fix ==
  * 83039f22 (selftests/powerpc: Remove Power9 copy_unaligned test)

  Patch can be cherry-picked into C, for Bionic it needs patches for bug
  1828935 to land first (8d191587) to make it a clean cherry-pick.

  It's already landed in D and onward.

  == Test ==
  Tested on a Power9 server with Cosmic, the broken tests will be removed 
correctly.

  == Regression Potential ==
  Low.
  Code change limited to testing tools and just removing broken tests. We still 
have copy_first_unaligned to test the "copy first" behaviour.

  == Original Bug Report ==
  This issue was only spotted on Power9 system "balter", for Power8 system, it 
has passed (skipped, and marked as passed) with this test:

   TAP version 13
   selftests: copy_unaligned
   
   test: test_copy_unaligned
   tags: git_version:unknown
   !! child died by signal 4
   failure: test_copy_unaligned
   not ok 1..1 selftests: copy_unaligned [FAIL]
   selftests: copy_first_unaligned
   
   test: test_copy_first_unaligned
   tags: git_version:unknown
   success: test_copy_first_unaligned
   ok 1..2 selftests: copy_first_unaligned [PASS]
   selftests: paste_unaligned
   
   test: test_paste_unaligned
   tags: git_version:unknown
   !! child died by signal 4
   failure: test_paste_unaligned
   not ok 1..3 selftests: paste_unaligned [FAIL]
   selftests: paste_last_unaligned
   
   test: test_paste_last_unaligned
   tags: git_version:unknown
   !! child died by signal 4
   failure: test_paste_last_unaligned
   not ok 1..4 selftests: paste_last_unaligned [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 06:50 seq
   crw-rw 1 root audio 116, 33 Jan 24 06:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: ppc64el
  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: Thu Jan 24 07:05:20 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro 
console=hvc0
  ProcLoadAvg: 1.24 0.89 0.66 3/1412 8319
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3876 00:17:569 0 EOF
   2: FLOCK  ADVISORY  WRITE 3556 00:17:497 0 EOF
   3: FLOCK  ADVISORY  WRITE 4090 00:17:596 0 EOF
   4: POSIX  ADVISORY  WRITE 3955 00:17:571 0 EOF
   5: POSIX  ADVISORY  WRITE 1823 00:17:348 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 

[Kernel-packages] [Bug 1824794] Re: acct01 in ubuntu_ltp_syscalls reported as a failure with B-KVM

[Po-Hsu Lin]

Issue fixed upstream, it will be skipped without any error now:

<<>>
tag=acct01 stime=1615542850
cmdline="acct01"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1291: TINFO: Timeout per run is 0h 05m 00s
acct01.c:75: TCONF: acct() system call isn't configured in kernel

Summary:
passed   0
failed   0
broken   0
skipped  1
warnings 0


** Changed in: ubuntu-kernel-tests
   Status: Triaged => Fix Released

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

Title:
  acct01 in ubuntu_ltp_syscalls reported as a failure with B-KVM

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid

Bug description:
  This test was skipped in the ltp syscalls test, due to unmatched
  configs.

  However the ltp test suite will treat it as a failure, it's better to
  figure out how to skip this.

  <<>>
  tag=acct01 stime=1555326506
  cmdline="acct01"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  incrementing stop
  acct01.c:70: CONF: acct() system call isn't configured in kernel
  safe_macros.c:360: WARN: acct01.c:96: unlink(./tmpfile) failed: ENOENT
  safe_macros.c:360: WARN: acct01.c:97: unlink(test_file_eloop1) failed: ENOENT

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 2
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=36 corefile=no
  cutime=0 cstime=0
  <<>>
  INFO: ltp-pan reported some tests FAIL

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

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

[Kernel-packages] [Bug 1833935] Re: Handle overflow in proc_get_long of sysctl

[Po-Hsu Lin]

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

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

Title:
  Handle overflow in proc_get_long of sysctl

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  == SRU Justification ==
  With the upper / lower boundary confined in bug 1834310, the file-max
  is still suffering with overflow issue.

  This is because the simple_strtoul() used in proc_get_long() to parse
  user input explicitly ignores overflows. So when you tried to put 2^64
  into file-max, it will:
  # echo 18446744073709551616 > /proc/sys/fs/file-max
  # cat /proc/sys/fs/file-max
  0

  Which will cause your system to silently die behind your back.

  This issue was reported by the case 1 of the sysctl02 test in LTP:
  sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0

  
  == Fix ==
  * 7f2923c4 (sysctl: handle overflow in proc_get_long)

  A new strtoul_lenient() was introduced here to solve this issue, with
  extra check to notify userspace with -EINVAL.

  This patch can be cherry-picked into B/C/D/E, it needs some content
  adjustment for X.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1833935-proc_get_long/

  The attempt to set file-max to 2^64 will be rejected:
  $ sudo sysctl -w -q fs.file-max=18446744073709551616
  sysctl: setting key "fs.file-max": Invalid argument

  Tested and passed with these kernels on AMD64 KVM nodes.

  == Regression Potential ==
  Low, the newly introduced function strtoul_lenient() is just for
  proc_get_long here.

  
  == Original bug report ==
  Test complains about apparmor enabled.
  As it's enabled by default, I think we might need to disable this test.

  Furthermore, this test will need kallsyms to be enabled, which is not
  for KVM kernels.

  <<>>
  tag=sysctl02_sh stime=1561360893
  cmdline="sysctl02.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  sysctl02 1 TINFO: timeout per run is 0h 5m 0s
  sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0
  sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 
18446744073709551615
  sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 
9223372036854775808
  sysctl02 4 TCONF: /proc/kallsyms not enabled
  sysctl02 4 TINFO: AppArmor enabled, this may affect test results
  sysctl02 4 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 
(requires super/root)
  sysctl02 4 TINFO: loaded AppArmor profiles: none

  Summary:
  passed   0
  failed   3
  skipped  1
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=33 corefile=no
  cutime=2 cstime=1
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15
  ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20
  Uname: Linux 4.18.0-1015-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Mon Jun 24 07:21:41 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1834310] Re: Handle overflow for file-max

[Po-Hsu Lin]

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

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

Title:
  Handle overflow for file-max

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  == SRU Justification ==
  Currently, when writing 2^64-1 or 2^63 into file-max: 
     echo 18446744073709551616 > /proc/sys/fs/file-max

  Will make the system stuck with "Too many open files in system" error
  within seconds.

  The upper and lower limit need to be defined properly to avoid this.
  (The case for passing 2^64 will be addressed in bug 1833935)

  This failure was reported by the case 2 and 3 of the sysctl02 test in LTP:
  sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 
18446744073709551615
  sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 
9223372036854775808

  == Fix ==
  * 32a5ad9c sysctl: handle overflow for file-max
  * 9002b214 kernel/sysctl.c: fix out-of-bounds access when setting file-max

  These patches can be cherry-picked into B/C.
  They have already been applied in X/D from stable update process.

  == Test ==
  Test kernel could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1834310-file-max/

  Tested OK on KVM nodes with the following command (extracted from the
  sysctl02 test case in LTP):
    $ cat /proc/sys/fs/file-max
    $ sudo sysctl -w -q fs.file-max=18446744073709551615
    $ cat /proc/sys/fs/file-max
    $ sudo sysctl -w -q fs.file-max=9223372036854775808
    $ cat /proc/sys/fs/file-max

  All three file-max output should be identical with the patched kernel.

  This is because the file-max value is parsed via
  __do_proc_doulongvec_minmax(), which does not report error when min or
  max are exceeded but it will just keep the old value instead.

  == Regression Potential ==
  Low, just adding boundaries to the file-max.
  And it's been applied in some of our kernels for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-52-generic 4.15.0-52.56
  ProcVersionSignature: User Name 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 25 11:03 seq
   crw-rw 1 root audio 116, 33 Jun 25 11:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  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 Jun 25 11:04:55 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=6f08d1c2-d443-47ee-97ca-2aeb1bf53f35 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-52-generic N/A
   linux-backports-modules-4.15.0-52-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1696558] Re: Enable CONFIG_SECURITY_DMESG_RESTRICT

[Po-Hsu Lin]

Mark Xenial as Won't fix like others.


** Changed in: linux-aws (Ubuntu Xenial)
   Status: In Progress => Won't Fix

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

Title:
  Enable CONFIG_SECURITY_DMESG_RESTRICT

Status in linux-aws package in Ubuntu:
  Won't Fix
Status in linux-aws source package in Trusty:
  Won't Fix
Status in linux-aws source package in Xenial:
  Won't Fix
Status in linux-aws source package in Bionic:
  Won't Fix
Status in linux-aws source package in Disco:
  Won't Fix

Bug description:
  There is a request to enable the following for linux-aws.

  config SECURITY_DMESG_RESTRICT
  bool "Restrict unprivileged access to the kernel syslog"
  default n
  help
This enforces restrictions on unprivileged users reading the kernel
syslog via dmesg(8).

If this option is not selected, no restrictions will be enforced
unless the dmesg_restrict sysctl is explicitly set to (1).

If you are unsure how to answer this question, answer N.

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

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

[Kernel-packages] [Bug 1909428] Re: eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with unexpected operator on F-5.8

[Po-Hsu Lin]

https://lists.ubuntu.com/archives/kernel-team/2021-March/118019.html

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

Title:
  eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with
  unexpected operator on F-5.8

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Impact] 
  The fail check in the end of powerpc/eeh/eeh-basic.sh script will complain 
about "unexpected operator"

  This is caused by the following line in the script:
$ test "$failed" == 0
/bin/sh: 4: test: 0: unexpected operator

  [Fix]
  * 3db380570af705 ("selftests/powerpc: Make the test check in eeh-basic.sh 
posix compliant")

  This is affecting F/G/H and can be cherry-picked for all of them.

  [Test case]
  Run the eeh-basic.sh script in tools/testing/selftests/powerpc/eeh/
  This error message should be gone.

  [Where problems could occur]
  This fix is limited to PowerPC testing tool, it's unlike to cause any issue.

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

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

[Kernel-packages] [Bug 1903596] Re: stack trace in kernel

[Po-Hsu Lin]

$ git tag --contains 427d5838e99632e9218eae752009c873cade89ac
Ubuntu-5.10.0-12.13
Ubuntu-5.10.0-13.14
Ubuntu-5.10.0-14.15
Ubuntu-5.10.0-15.16
Ubuntu-5.11.0-11.12

In hirsute already. Closing this bug.

** Changed in: linux (Ubuntu Hirsute)
 Assignee: Po-Hsu Lin (cypressyew) => (unassigned)

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

Title:
  stack trace in kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  Whenever a buggy NAPI driver returns more than its budget, it will
  trigger a stack trace warning with:
  WARN_ON_ONCE(work > weight);

  The warning message looks like this :
  WARNING: CPU: 2 PID: 0 at 
/build/linux-hwe-ymdo11/linux-hwe-4.15.0/net/core/dev.c:5672 
net_rx_action+0x276/0x3b0

  This is not very useful for debugging purpose, since it does not tell
  you what's going on there.

  == Fix ==
  * 427d5838e996 ("net: napi: remove useless stack trace")

  This patch will emit a message giving the function name, and a
  descriptive message like:
  NAPI poll function ath10k_pci_napi_poll+0x0/0x120 [ath10k_pci] returned 
0, exceeding its budget of 64.

  This patch is a clean-cherry for all the releases except Xenial.
  For Xenial it will need to be applied with -C1

  == Test ==
  Test kernels can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1903596-napi-warnon/

  Please note that even though I tried to reproduce this on a XPS 13
  9360 mentioned in this bug report that shipped with Atheros QCA6174
  [168c:003e] wireless card, but I can't trigger this warning message.
  The bug opener is also unable to test this due to some other reasons.

  Howeve I did tried to trigger this warning forcibly by putting it
  outside the if statement with the test kernels in the following link
  to make sure it won't cause some other problem.

  https://people.canonical.com/~phlin/kernel/lp-1903596-napi-warnon
  /force-to-warn/

  == Where problems could occur ==
  For this bug itself, this patch does not really solve the problem
  but it will provide more debug information for developers in the
  future (and since this is just a warning message, it should be fine).
  We can expect to see more a detailed report against ath10k driver
  in the future on launchpad.


  == Original Bug Report ==
  This appears to be a problem in the ath10k module. I am not sure what it is 
exactly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-122-generic 4.15.0-122.124~16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.26
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  9 13:35:54 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2020-11-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1916468] Re: powerpc/eeh-basic.sh in kselftest make P8 node stopped working

[Po-Hsu Lin]

** Tags added: ubuntu-kernel-selftests

** Tags added: 5.4 focal ppc64el

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

Title:
  powerpc/eeh-basic.sh in kselftest make P8 node stopped working

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  When trying to run this test on P8 node entei with Focal kernel, it will try 
to break 4 devices on Focal, and one of them is using the AHCI driver which 
doesn't support error recovery:

  $ sudo ./eeh-basic.sh
  :00:00.0, Skipped: bridge
  0001:00:00.0, Skipped: bridge
  0020:00:00.0, Skipped: bridge
  0021:00:00.0, Skipped: bridge
  0021:01:00.0, Skipped: bridge
  0021:02:01.0, Skipped: bridge
  0021:02:08.0, Skipped: bridge
  0021:02:09.0, Skipped: bridge
  0021:02:0a.0, Skipped: bridge
  0021:02:0b.0, Skipped: bridge
  0021:02:0c.0, Skipped: bridge
  0021:0d:00.0, Added
  0021:0e:00.0, Added
  0021:0f:00.0, Skipped: bridge
  0021:10:00.0, Added
  0022:00:00.0, Skipped: bridge
  0022:01:00.0, Added
  Found 4 breakable devices...
  Breaking 0021:0d:00.0...
  0021:0d:00.0, waited 0/60
  0021:0d:00.0, waited 1/60
  0021:0d:00.0, waited 2/60
  0021:0d:00.0, waited 3/60
  0021:0d:00.0, waited 4/60
  0021:0d:00.0, waited 5/60
  0021:0d:00.0, waited 6/60
  0021:0d:00.0, waited 7/60
  0021:0d:00.0, waited 8/60
  0021:0d:00.0, Recovered after 9 seconds
  Breaking 0021:0e:00.0...
  0021:0e:00.0, waited 0/60
  0021:0e:00.0, waited 1/60
  ./eeh-basic.sh: 74: sleep: Input/output error
  0021:0e:00.0, waited 2/60
  ./eeh-basic.sh: 74: sleep: Input/output error
  
  ./eeh-basic.sh: 74: sleep: Input/output error
  0021:0e:00.0, waited 59/60
  ./eeh-basic.sh: 74: sleep: Input/output error
  0021:0e:00.0, waited 60/60
  ./eeh-basic.sh: 74: sleep: Input/output error
  0021:0e:00.0, Failed to recover!
  Breaking 0021:10:00.0...
  Skipping 0021:10:00.0, Initial PE state is not ok
  Breaking 0022:01:00.0...
  Skipping 0022:01:00.0, Initial PE state is not ok
  3 devices failed to recover (4 tested)
  ./eeh-basic.sh: 81: lspci: Input/output error
  ./eeh-basic.sh: 81: diff: Input/output error
  ./eeh-basic.sh: 82: rm: Input/output error
  ./eeh-basic.sh: 84: test: 3: unexpected operator

  With the driver failed to recovery, the system will start acting up.
  $ ls
  ls: command not found

  And drop into a read-only state

  [Fixes]
  * bbe9064f30f06e ("selftests/eeh: Skip ahci adapters")

  This is only affecting Focal and it can be cherry-picked.

  [Test case]
  Run the eeh-basic.sh script in tools/testing/selftests/powerpc/eeh/ on the 
affected P8 node, the test should pass without any issue.

  [Where problems could occur]
  This fix is limited to PowerPC testing tool, it should not cause any issue.

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

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

[Kernel-packages] [Bug 1918886] Re: after upgrade to ubuntu 14.04, system not restarting and touchpad not working

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  after upgrade to ubuntu 14.04, system not restarting and touchpad not
  working

Status in linux-signed package in Ubuntu:
  New

Bug description:
  after upgrade to ubuntu 14.04 from ubuntu 12.04, the system is not
  restarting, however after quickly pressing esc i can run the system on
  F11 (hp recovery) mode , but in that the touchpad is not working

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-170-generic 3.13.0-170.220
  Uname: Linux 3.13.0-170-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 12 12:58:15 2021
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130722-08:34
  LiveMediaBuild: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130722-08:34
  SourcePackage: linux-signed

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

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

[Kernel-packages] [Bug 1917829] Re: alsa/hda: the hdmi audio dosn't work on TGL machines

[Hui Wang]

Plugged 2 monitors into the Dell dock, and plug the dock to the dell TGL
machines, we could see 2 hdmi audio devices, all worked well.

verified done.


** Tags removed: verification-needed-focal
** Tags added: verification-done-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/1917829

Title:
  alsa/hda: the hdmi audio dosn't work on TGL machines

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

Bug description:
  [Impact]
  On the TGL machines, we plug a dp mst hub to the thunderbolt port,
  and plug a hdmi/dp monitor to the dp mst hub, then check the
  gnome-sound-setting, could not find the hdmi/dp audio device.

  [Fix]
  backport a patch from upstream, this patch change to assign
  the pcm slot dynamically on TGL macines.

  [Test]
  On 2 lenovo and dell TGL machines, plug dp mst hub and plug
  2 monitors to the hub or to the machine hdmi/dp ports, check
  the gnome-sound-setting, there are 2 hdmi/dp audio devices.
  and they all could output sound.

  
  [Where problems could occur]
  After this change, the hdmi audio device number starts from 0, 1, ...,
  while without this change, the hdmi audio device number is fix
  mapped, it could be 3 or 5 directly. So if there is some userspace
  applications depends on the fix mapped hdmi audio device, these
  applicatons could not work on TGL machines.

  So far, we don't know if those applications exists or not, but I
  could confirm the ubuntu audio stack builds on the alsa-lib and
  pulseaudio, this change will not affect the applications based
  on the alsa-lib and pulseaudio.

  And I already tested audio functions under ubuntu on the TGL machines,
  there is no regression.

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

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

[Kernel-packages] [Bug 1918886] [NEW] after upgrade to ubuntu 14.04, system not restarting and touchpad not working

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

after upgrade to ubuntu 14.04 from ubuntu 12.04, the system is not
restarting, however after quickly pressing esc i can run the system on
F11 (hp recovery) mode , but in that the touchpad is not working

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-170-generic 3.13.0-170.220
Uname: Linux 3.13.0-170-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 12 12:58:15 2021
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130722-08:34
LiveMediaBuild: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130722-08:34
SourcePackage: linux-signed

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


** Tags: amd64 apport-bug
-- 
after upgrade to ubuntu 14.04, system not restarting and touchpad not working 
https://bugs.launchpad.net/bugs/1918886
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-signed 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 1918887] Re: after upgrade to ubuntu 14.04, system not restarting and touchpad not working

[Chris Guiver]

I just noticed the linked https://wiki.ubuntu.com/Releases refers to
14.04 as still being supported.

Ubuntu 14.04 LTS reached EOL on April 25, 2019.
Ubuntu 14.04 ESM (LTS with extended support) is still supported until April 
2022.

** Package changed: 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/1918887

Title:
  after upgrade to ubuntu 14.04, system not restarting and touchpad not
  working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrade to ubuntu 14.04 from ubuntu 12.04, the system is not
  restarting, however after quickly pressing esc i can run the system on
  F11 (hp recovery) mode , but in that the touchpad is not working

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-170-generic 3.13.0-170.220
  Uname: Linux 3.13.0-170-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 12 12:58:15 2021
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130722-08:34
  LiveMediaBuild: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130722-08:34
  SourcePackage: linux-signed

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

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