[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12-rc7/amd64/

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

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

Title:
  AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dear developers, please let me thank you for all your hard work first
  of all, I'm a big fan of yours!

  On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which
  seem to be connected to the amdgpu kernel module:

  1. Amdgpu kernel module loads correctly during boot, but VESA Xorg
  module is loaded instead of AMDGPU Xorg module during X startup. This
  results in non-accelerated X and high CPU load.

  - This situation is always reproducible.

  - I'm experiencing it with all kernel versions in between
  5.4.0-47-generic and 5.4.0-67-generic inclusive.

  - The situation escalates more with newer kernel version. For
  5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and
  I just get black screen.

  - I have found a workaround after many days of googling and testing. AMDGPU 
Xorg module is loaded correctly if and only if I disable AMD ACP by means of 
the following kernel boot parameter:
  amdgpu.ip_block_mask=0xfdff

  - Acceleration is ok with kernels where AMD ACP is disabled by default
  (linux-image-linuxlite-5.6.0 for example)

  
  2. The 2nd problem I'm facing is with non functioning hibernation after I 
"fixed" the X acceleration. Hibernation image does not seem to get created, 
screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module 
is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by 
means of "nomodeset" and go just with VESA module.

  - always reproducible but tested only with 5.4.0-67-generic

  
  Thank you and best regards,
  Radek

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-67-generic 5.4.0-67.75
  ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
  Uname: Linux 5.4.0-67-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  radek  1513 F pulseaudio
   /dev/snd/controlC0:  radek  1513 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Mar 21 15:22:29 2021
  HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic 
root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 
nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff 
no_console_suspend
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-67-generic N/A
   linux-backports-modules-5.4.0-67-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.20
  dmi.board.name: FM2A68M-HD+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1922807] Re: Touchbad on HP Probook not working at all

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12-rc7/amd64/

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

Title:
  Touchbad on HP Probook not working at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have a fresh installation of Ubuntu (Ubuntu 20.04.2 LTS, Release: 20.04) on 
one partition of my HP Probook. The other partition is Win10 Pro. 
  From the first moments on the touchpad didn't work. But then i could solve 
the issue and it worked fine for a while:
  sudo apt remove xserver-xorg-input-synaptics

  Then i installed VirtualBox and also installed some additional
  dependencies:

  sudo apt-get install -y build-essential zlibc zlib1g-dev ruby ruby-dev
  openssl libxslt-dev libxml2-dev libssl-dev libreadline6
  libreadline6-dev libyaml-dev libsqlite3-dev sqlite3

  sudo apt-get install -y build-essential zlibc zlib1g-dev ruby ruby-dev
  openssl libxslt1-dev libxml2-dev libssl-dev libreadline7 libreadline-
  dev libyaml-dev libsqlite3-dev sqlite3

  I also installed ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) 
[x86_64-linux-gnu] 
  and GCC via:
  sudo apt install build-essential

  Now my touchpad doesn't work and i can't remove synaptics again, because its 
not even installed.
  I also tried editing the grub file:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nopnp"
  and also tried:
  GRUB_CMDLINE_LIN UX_DEFAULT="quiet splash psmouse.proto=bare"
  GRUB_CMDLINE_LINUX="i8042.reset i8042.nomux i8042.nopnp i8042.noloop"

  The devices-list proc/bus/input/devices is attached to this report but
  unfortunately, there is no touchpad listed.

  
  And here is the xinput list:
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Surface Mobile Mouseid=16   [slave  pointer 
 (2)]
  ⎜   ↳ MX Keys Consumer Controlid=18   [slave  pointer 
 (2)]
  ⎜   ↳ MX Keys Mouse   id=20   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ HP HD Camera: HP HD Camera  id=10   [slave  
keyboard (3)]
  ↳ HP HD Camera: HP IR Camera  id=11   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=13   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=14   [slave  
keyboard (3)]
  ↳ Surface Mobile Mouse Keyboard   id=15   [slave  
keyboard (3)]
  ↳ MX Keys Keyboardid=17   [slave  
keyboard (3)]
  ↳ MX Keys Consumer Controlid=19   [slave  
keyboard (3)]

  I am thankful for any help.
  Kind regards,
  ente187
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  emre   2097 F pulseaudio
   /dev/snd/controlC0:  emre   2097 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-03-24 (17 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP ProBook x360 435 G7
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=cd5cae68-0cc1-4876-8a87-6b0cc7e067bf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-43-generic N/A
   linux-backports-modules-5.8.0-43-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/27/2020
  dmi.bios.release: 3.0
  dmi.bios.vendor: HP
  dmi.bios.version: S80 Ver. 01.03.00
  dmi.board.name: 8735
  dmi.board.vendor: HP
  dmi.board.version: 

[Kernel-packages] [Bug 1923515] Re: [Dell XPS 15 9500] New touchpad detected as "PS/2 Logitech Wheel Mouse"

[Kai-Heng Feng]

Possible to test Windows? Because I've seen several other XPS 9500
touchpads work just fine.

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

Title:
  [Dell XPS 15 9500] New touchpad detected as "PS/2 Logitech Wheel
  Mouse"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been using Ubuntu 20.04 on a Dell XPS 15 9550. The laptop's
  touchpad had a hardware defect common to the model (nicknamed
  "wobble") so Dell sent a tech to replace it. The new touchpad looks
  identical to the original but the kernel doesn't correctly detect it.
  The device does work, but appears to the kernel as a "PS/2 Logitech
  Wheel Mouse," which prevents the use of features like two-finger
  scrolling, disabling tap to click, and palm detection.

  A good summary of my troubleshooting steps are here:
  
https://askubuntu.com/questions/1330555/touchpad-detected-as-ps-2-logitech-wheel-mouse-dell-xps-15-ubuntu-20-04

  Importantly, I've tried a mainline kernel downloaded from Ubuntu
  (5.11.12 and a 5.12.0 release candidate, whereas the current version
  is a 5.8.0). I've also tried two bootable USB drives containing Ubuntu
  20.04 and 21.04 (release candidate). Nothing has changed the device
  detection or behavior. The issue is identical in the default Ubuntu
  desktop and in Plasma. There are no touchpad settings in the UEFI
  BIOS.

  Per the touchpad detection instructions, I've attached the output of 
/proc/bus/input/devices, Xorg.0.log, and the `xinput --list` command. My 
suspicion is that Dell has ordered a brand new touchpad model for which there 
is no kernel driver; looking at the logs, the previous model was an elantech, 
but I'm not sure if the new one is as well.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edholden   1571 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-11 (183 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. XPS 15 9500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=a8be5c03-8499-4474-932d-725877e9cc6c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2020
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0RDX6T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd12/24/2020:br1.6:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0RDX6T:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9500
  dmi.product.sku: 097D
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware

[Kai-Heng Feng]

Ian, can you please file a new bug? Thanks.

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

Title:
  Support for loading Broadcom bluetooth firmware

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux source package in Saucy:
  Fix Released
Status in linux source package in Trusty:
  Confirmed

Bug description:
  Broadcom bluetooth chips require a tool called patchram uploader [1]
  to load firmware. This applies to at least BCM20702 and BCM43142.
  Although some of the devices have an OTPROM that contains required
  firmware, but it is found that these devices would not have HFP/HSP
  support unless a upgraded firmware is loaded via patchram uploader.

  This tool requires hci device to do the firmware loading, but this may
  cause some race condition between patchram tool and bluetoothd or
  something that also works on hci interface.

  Also it needs some hooks to make firmware loads after bootup, s3,  s4,
  rfkill, and device hotplug events. Implement this loader in kernel
  module would make things more easier.

  [1] http://marc.info/?l=linux-bluetooth=132039175324993=2

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

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

[Kernel-packages] [Bug 1892816] Re: memory-hotplug test from ubuntu_kernel_selftests failed on X-4.4 / X-4.15 / B-4.15 / F-5.4 ARM64 (execution permission issue)

[Po-Hsu Lin]

This is disabled intentionally:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=e24a4b63b

I think we can SKIP this test so it won't complain about this anymore.

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

Title:
  memory-hotplug test from ubuntu_kernel_selftests failed on X-4.4 /
  X-4.15 / B-4.15 / F-5.4 ARM64 (execution permission issue)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on 4.15.0-114.115~16.04.1, test failed with:

./mem-on-off-test.sh -r 2 && echo "selftests: memory-hotplug [PASS]" || 
echo "selftests: memory-hotplug [FAIL]"
/bin/sh: 1: ./mem-on-off-test.sh: Permission denied
selftests: memory-hotplug [FAIL]

  Note that this test was marked as passed (test skipped) with
  4.15.0-112.113~16.04.1 on both ThunderX and Moonshot node:

  skip all tests: memory hotplug is not supported
  selftests: memory-hotplug [PASS]

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

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

[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

[Yuan-Chen Cheng]

per quick test, we need focal/apt 2.0.5 to fix this issue.

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

Title:
  unexpected error pop-up after 'apt install nvidia-driver-455'

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu info:

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52)
  Release 20.04

  Full reproduce step

  1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first 
place, without all i386 pkg installed.
  2. run update-manager to do upgrade.
  3. it will show error after download deb and didn't upgrade anything.

  Per test with the command to do the upgrade, it will have an extra
  error message, but it will just upgrade and install recommended i386
  debs.

  The error msgs are:

  E: Could not configure 'libc6:i386'.
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  Short way to get the error:
  # apt-get install libgcc-s1:i386 --dry-run
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 
gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16
libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 
libunistring2:i386
  Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
  The following NEW packages will be installed:
gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 
libunistring2:i386
  The following packages will be upgraded:
libc6
  1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded.
  Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates 
[amd64])
  Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) []
  Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) []
  Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386])
  Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386])
  Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  E: Could not configure 'libc6:i386'. 
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  For now, we think the above Error is the root cause of update-manager
  failure.

  ---

  This happens as upgrade package nvidia-driver-455 from
  455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1.

  for more detail, please check the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions

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

[James Hennig]

The solution has been found and should have been rather obvious in the
first place... Just try a different distribution.

I decided to try out Linux Mint 20.1 and have been testing it for the
past ~6 hours, completely stock (except for all updates installed), no
kernel modifications or GRUB options and it works every time on bootup
with the touchpad. I am rather surprised that such a relatively old
kernel (5.4) works with this new-ish laptop. Perhaps this was why I was
so falsely focused on having newer kernels available in a distribution
in the first place.

I even tried 40 consecutive reboots whilst messing with the touchpad as
the machine was booting and it still worked every time. Let it be known
that the fix for the Lenovo IdeaPad 3 14ADA05 is to simply install Linux
Mint. I have to imagine that other Ubuntu-based installs also work with
this particular laptop, especially since it says "Fix Released" under
Ubuntu and Ubuntu-related distributions.

As far as Manjaro goes, also let it be known that something was
introduced after Kernel 5.9.16-1 which breaks the ability for the
touchpad to reliably work with this laptop. My best educated guess is
that something is loaded too early or too late during bootup which gets
jumbled up at random. No idea what that could possibly be, but I hope
that Manjaro devs might take note. I know that at least @Helmut Stult
might still be looking in this thread.

I consider this fixed for my laptop :)

-- 
You 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:
  Fix Released
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 Button

[Kernel-packages] [Bug 1672819] Re: exec'ing a setuid binary from a threaded program sometimes fails to setuid

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => High

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

Title:
  exec'ing a setuid binary from a threaded program sometimes fails to
  setuid

Status in Linux:
  Confirmed
Status in golang-1.6 package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in golang-1.6 source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in golang-1.6 source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released
Status in golang-1.6 source package in Zesty:
  Invalid
Status in linux source package in Zesty:
  Fix Released

Bug description:
  == SRU template for golang-1.6 ==

  [Impact]
  The kernel bug reported below means that occasionally (maybe 1 in 1000 times) 
the snapd -> snap-confine exec that is part of a snap execution fails to take 
the setuid bit on the snap-confine binary into account which means that the 
execution fails. This is extremely confusing for the user of the snap who just 
sees a permission denied error with no explanation.

  The kernel bug has been fixed in Xenial+ but not all users of snapd are on 
xenial+ kernels (they might be on trusty or another distribution entirely).
  Backporting this fix will mean that the snapd in the core snap will get the 
workaround next time it is built and because the snapd in trusty or the other 
distro will re-exec into the snapd in the core snap before execing 
snap-confine, users should not see the above behaviour.

  [Test case]
  This will be a bit tricky as the kernel bug has been fixed. A xenial 
container on a trusty host/VM should do the trick. The test case from 
https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813 should be 
sufficient to demonstrate the bug and then, once golang-1.6 has been upgraded 
from proposed, the fix.

  [Regression potential]
  If there is a bug in the patch it could cause deadlocks in currently working 
programs. But the patch is pretty simple and has passed review upstream so I 
think it should be OK.

  == SRU REQUEST XENIAL, YAKKETY, ZESTY ==

  Due to two race conditions in check_unsafe_exec(),  exec'ing a setuid
  binary from a threaded program sometimes fails to setuid.

  == Fix ==

  Sauce patch for Xenial, Yakkety + Zesty:

  https://lists.ubuntu.com/archives/kernel-team/2017-May/084102.html

  This fix re-executes the unsafe check if there is a discrepancy
  between the expected fs count and the found count during the racy
  window during thread exec or exit.  This re-check occurs very
  infrequently and saves a lot of addition locking on per thread
  structures that would make performance of fork/exec/exit prohibitively
  expensive.

  == Test case ==

  See the example C code in the patch, https://lists.ubuntu.com/archives
  /kernel-team/2017-May/084102.html

  Run the test code as follows: for i in $(seq 1000); do ./a; done

  With the patch, no messages are emitted, without the patch, one sees a
  message:

  "Failed, got euid 1000 (expecting 0)"

  ..which shows the setuid program failed the check_unsafe_exec()
  because of the race.

  == Regression potential ==

  breaking existing safe exec semantics.

  

  This can be reproduced with
  https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813

  With that, and go 1.8, if you run “make” and then

  for i in `seq 99`; do ./a_go; done

  you'll see a variable number of ”GOT 1000” (or whatever your user id
  is). If you don't, add one or two more 9s on there.

  That's a simple go reproducer. You can also use “a_p” instead of
  “a_go” to see one that only uses pthreads. “a_c” is a C version that
  does *not* reproduce the issue.

  But it's not pthreads: if in a_go.go you comment out the “import "C"”,
  you'll still see the “GOT 1000” messages, in a static binary that uses
  no pthreads, just clone(2). You'll also see a bunch of warnings
  because it's not properly handling an EAGAIN from clone, but that's
  unrelated.

  If you pin the process to a single thread using taskset, you don't get
  the issue from a_go; a_p continues to reproduce the issue. In some
  virtualized environments we haven't been able to reproduce the issue
  either (e.g. some aws instances), but kvm works (you need -smp to see
  the issue from a_go).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   john   2354 F...m pulseaudio
   /dev/snd/controlC0:  john   2354 F pulseaudio
  

[Kernel-packages] [Bug 1924623] Re: Bluetooth headset pairing issue (HOCO ES32 PLUS)

[Daniel van Vugt]

** Summary changed:

- Bluetooth headset pairing issue
+ Bluetooth headset pairing issue (HOCO ES32 PLUS)

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

Title:
  Bluetooth headset pairing issue (HOCO ES32 PLUS)

Status in bluez package in Ubuntu:
  New

Bug description:
  I am unable to connect a HOCO ES32 PLUS bluetooth headset. Device is
  visible and in pairable mode, but after running:

  bluetoothctl

  [bluetooth]# show
  Controller 04:33:C2:AA:17:60 (public)
   Name: mykyt
   Alias: mykyt
   Class: 0x001c010c
   Powered: yes
   Discoverable: yes
   DiscoverableTimeout: 0x
   Pairable: yes
   UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
   UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
   UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
   UUID: Vendor specific   (5005--1000-8000-0002ee01)
   UUID: Headset AG(1112--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
   UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
   UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
   Modalias: usb:v1D6Bp0246d0535
   Discovering: yes
  Advertising Features:
   ActiveInstances: 0x00
   SupportedInstances: 0x05
   SupportedIncludes: tx-power
   SupportedIncludes: appearance
   SupportedIncludes: local-name
   SupportedSecondaryChannels: 1M
   SupportedSecondaryChannels: 2M
   SupportedSecondaryChannels: Coded

  i get:

  Failed to pair: org.bluez.Error.AuthenticationTimeout

  or

  Failed to pair: org.bluez.Error.AuthenticationCanceled

  or

  Failed to pair: org.bluez.Error.Failed

  I tried every single solution i was able to find for similar problems,
  including changing controller mode to bredr, reinstalling pulseaudio,
  unblocking rfkill, checking if my device is in pairable mode, using
  blueman and so on.

  The fact is, bluetooth is working on my laptop (I can connect to my
  phone and my other bluetooth headset MEIZU EP51) and also my headset
  HOCO ES32 PLUS is working and is able to connect to my phone and my
  other laptop DELL INSPIRON 7359 which is running on ubuntu 18.04.

  I really hope you can help me. Please tell me if you need more information 
and I will provide it.
  Thank you!
  --

  lsb_release -rd

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  apt-cache policy bluez

  bluez:
    Installed: 5.53-0ubuntu3
    Candidate: 5.53-0ubuntu3
    Version table:
   *** 5.53-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  --

  Expected behavior:

  After turning on bluetooth and clicking on device name in settings ->
  bluetooth device is connecting and pairing successfully.

  Current behavior:

  Pairing fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 00:28:19 2021
  InstallationDate: Installed on 2020-08-27 (231 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Swift SF314-57G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=59c2b478-ae5a-4c28-8c13-6b3721fe1f3b ro nouveau.modeset=0 quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2020
  dmi.bios.release: 1.14
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 

[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

[Yuan-Chen Cheng]

For completeness, apt pkg  versions in focal are

focal: 2.0.2
focal-security: 2.0.2ubuntu0.2
focal-update 2.0.5

If 2.0.2ubuntu0.2 can cover this, then we are all clear, since it will
be upgraded by unattended upgrade.

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

Title:
  unexpected error pop-up after 'apt install nvidia-driver-455'

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu info:

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52)
  Release 20.04

  Full reproduce step

  1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first 
place, without all i386 pkg installed.
  2. run update-manager to do upgrade.
  3. it will show error after download deb and didn't upgrade anything.

  Per test with the command to do the upgrade, it will have an extra
  error message, but it will just upgrade and install recommended i386
  debs.

  The error msgs are:

  E: Could not configure 'libc6:i386'.
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  Short way to get the error:
  # apt-get install libgcc-s1:i386 --dry-run
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 
gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16
libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 
libunistring2:i386
  Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
  The following NEW packages will be installed:
gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 
libunistring2:i386
  The following packages will be upgraded:
libc6
  1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded.
  Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates 
[amd64])
  Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) []
  Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) []
  Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386])
  Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386])
  Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  E: Could not configure 'libc6:i386'. 
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  For now, we think the above Error is the root cause of update-manager
  failure.

  ---

  This happens as upgrade package nvidia-driver-455 from
  455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1.

  for more detail, please check the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions

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

[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Dan Streetman]

i uploaded, but then saw dannf had already uploaded too a few hours
ago...sorry for the duplicate uploads!

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

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Focal:
  Confirmed
Status in makedumpfile source package in Groovy:
  Confirmed
Status in makedumpfile source package in Hirsute:
  Fix Released
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  [Impact]

  On arm64 and kernels 5.4+ makedumpfile fails.

  Upstream patches solve this bug :

  [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option
  
https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab

  [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  
https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183

  [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  
https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583

  [Test Case]

  OS: Ubuntu 20.04 LTS
  kernel: 5.4.0-21-generic
  arch:arm64
  Description:
  When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test 
steps are as follows:
  # echo 1> / proc / sys / kernel / sysrq
  # echo c> / proc / sysrq-trigger
  The error logs are as follows:
  [   26.599161] kdump-tools[653]: Starting kdump-tools:
  [   26.612761] kdump-tools[659]: Starting kdump-tools:
  [   26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/2020050
  [   26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/2020050
  [   26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and 
VA Bits 47 not supported
  [   26.678199] kdump-tools[676]: get_machdep_info_arm64
  [   26.692518] kdump-tools[659]: get_machdep_info_arm64
  [   26.852221] hns3 :7d:00.0: get link status cmd failed -16

  [   94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * 
kdump-tools: saved vmcore in /var/crash/202005061048
  [   94.435510] kdump-tools[659]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/202005061048/dmesg.202005061048
  [   94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and 
VA Bits 47 not supported
  [   94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine 
platform config values
  [   94.485912] kdump-tools[688]: makedumpfile Failed.
  [   94.500760] kdump-tools[659]:  * kdump-tools: makedumpfile --dump-dmesg 
failed. dmesg content will be unavailable
  [   94.520225] kdump-tools[659]:  * kdump-tools: failed to save dmesg content 
in /var/crash/202005061048
  [   94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400
  [   94.564597] kdump-tools[692]: Rebooting.
  [   94.678709] reboot: Restarting systemlpc uart init Done

  [Regression Potential]

  Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage 
option
  removes get_elf_loads function this function was only used with --mem-usage 
option
  , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19)
  the information needed is in vmcoreinfo
  Any regression potential would affect the --mem-usage only

  Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  arm64 only
  make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing 
VA_BITS
  does not work on Linux 5.4 and later.
  Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, 
however
  this way of calculation breaks after 5.4. This commit gets the VA_BITS from 
vmcoreinfo
  and as a safeguard it uses the old way of deriving VA_BITS only if reading 
from vmcoreinfo doesn't work.

  From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later 
use later kernel so not
  great regression potentional and if any it would only affect arm64.

  Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  arm64 only
  Linux 5.4 and later kernels for arm64 changed the kernel VA space
  arrangement and introduced 52-bit kernel VAs by merging branch
  commit b333b0ba2346.  Support 5.9+ kernels with vmcoreinfo entries
  and 5.4+ kernels with best guessing.

  This patch makes adjustemnt to properly calculate vabits_actual, 
max_physmem_bits, page_offset
  Any regression potential would affect only arm64 and the calculation of the 
above variables.

  [Other]

  For H only the 3 commits are needed and they cherry-pick.

  For G and F the 3rd commit does not apply and an extra commit is
  needed :

  commit da0d25ffa585c9a1adb94562c815daa393b1ee5e
  

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Ubuntu/Win 10 dual boot ASUS Ryzen 4900 ROG notebook.

  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04

  Touchpad works on Win 10. Touchpad does not work on Ubuntu 21.04. I
  tried several kernel variants and drivers such as libinput default,
  synaptics touchpad, touchegg and libinput-gestures. I was earlier on
  LTS version, just migrated to dev version of 21.04 in search of
  solution.

  Some combination could get touchpad working perfectly well. After
  reboot, it ceased working and I simply could not get the combination
  working.

  sudo apt-cache policy pkgname 
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-14-lowlatency 5.11.0-14.15
  ProcVersionSignature: Ubuntu 5.11.0-14.15-lowlatency 5.11.12
  Uname: Linux 5.11.0-14-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ognanasekaran   6261 F pulseaudio
   /dev/snd/controlC1:  ognanasekaran   6261 F pulseaudio
   /dev/snd/controlC0:  ognanasekaran   6261 F pulseaudio
   /dev/snd/controlC3:  ognanasekaran   6261 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 04:23:44 2021
  InstallationDate: Installed on 2021-03-27 (19 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA502IV_GA502IV
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-lowlatency 
root=UUID=38ec9242-bede-4035-b25e-2edf25f980a4 ro recovery nomodeset 
dis_ucode_ldr
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-14-lowlatency N/A
   linux-backports-modules-5.11.0-14-lowlatency  N/A
   linux-firmware1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GA502IV.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GA502IV
  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.ec.firmware.release: 3.13
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGA502IV.211:bd12/30/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA502IV_GA502IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA502IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG Zephyrus G15
  dmi.product.name: ROG Zephyrus G15 GA502IV_GA502IV
  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/1924626/+subscriptions

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

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

[Gnanasekaran]

Public bug reported:

I have a Ubuntu/Win 10 dual boot ASUS Ryzen 4900 ROG notebook.

Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04

Touchpad works on Win 10. Touchpad does not work on Ubuntu 21.04. I
tried several kernel variants and drivers such as libinput default,
synaptics touchpad, touchegg and libinput-gestures. I was earlier on
LTS version, just migrated to dev version of 21.04 in search of
solution.

Some combination could get touchpad working perfectly well. After
reboot, it ceased working and I simply could not get the combination
working.

sudo apt-cache policy pkgname 
N: Unable to locate package pkgname

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-14-lowlatency 5.11.0-14.15
ProcVersionSignature: Ubuntu 5.11.0-14.15-lowlatency 5.11.12
Uname: Linux 5.11.0-14-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  ognanasekaran   6261 F pulseaudio
 /dev/snd/controlC1:  ognanasekaran   6261 F pulseaudio
 /dev/snd/controlC0:  ognanasekaran   6261 F pulseaudio
 /dev/snd/controlC3:  ognanasekaran   6261 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 16 04:23:44 2021
InstallationDate: Installed on 2021-03-27 (19 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA502IV_GA502IV
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-lowlatency 
root=UUID=38ec9242-bede-4035-b25e-2edf25f980a4 ro recovery nomodeset 
dis_ucode_ldr
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-14-lowlatency N/A
 linux-backports-modules-5.11.0-14-lowlatency  N/A
 linux-firmware1.197
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
dmi.bios.date: 12/30/2020
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GA502IV.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GA502IV
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.ec.firmware.release: 3.13
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGA502IV.211:bd12/30/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA502IV_GA502IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA502IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG Zephyrus G15
dmi.product.name: ROG Zephyrus G15 GA502IV_GA502IV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug hirsute

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  New

Bug description:
  I have a Ubuntu/Win 10 dual boot ASUS Ryzen 4900 ROG notebook.

  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04

  Touchpad works on Win 10. Touchpad does not work on Ubuntu 21.04. I
  tried several kernel variants and drivers such as libinput default,
  synaptics touchpad, touchegg and libinput-gestures. I was earlier on
  LTS version, just migrated to dev version of 21.04 in search of
  solution.

  Some combination could get touchpad working perfectly well. After
  reboot, it ceased working and I simply could not get the combination
  working.

  sudo apt-cache policy pkgname 
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-14-lowlatency 5.11.0-14.15
  ProcVersionSignature: Ubuntu 5.11.0-14.15-lowlatency 5.11.12
  Uname: Linux 5.11.0-14-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ognanasekaran   6261 F pulseaudio
   /dev/snd/controlC1:  ognanasekaran   6261 F pulseaudio
   /dev/snd/controlC0:  ognanasekaran   6261 F pulseaudio
   /dev/snd/controlC3:  ognanasekaran   6261 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 04:23:44 2021
  InstallationDate: Installed on 2021-03-27 (19 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA502IV_GA502IV
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-lowlatency 
root=UUID=38ec9242-bede-4035-b25e-2edf25f980a4 ro recovery nomodeset 
dis_ucode_ldr
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-14-lowlatency N/A
   linux-backports-modules-5.11.0-14-lowlatency  N/A
   linux-firmware1.197
  

[Kernel-packages] [Bug 1924623] Re: Bluetooth headset pairing issue

[Mykyta]

** Description changed:

  I am unable to connect a HOCO ES32 PLUS bluetooth headset. Device is
  visible and in pairable mode, but after running:
  
  bluetoothctl
  
  [bluetooth]# show
  Controller 04:33:C2:AA:17:60 (public)
-   Name: mykyt
-   Alias: mykyt
-   Class: 0x001c010c
-   Powered: yes
-   Discoverable: yes
-   DiscoverableTimeout: 0x
-   Pairable: yes
-   UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
-   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
-   UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
-   UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
-   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
-   UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
-   UUID: Vendor specific   (5005--1000-8000-0002ee01)
-   UUID: Headset AG(1112--1000-8000-00805f9b34fb)
-   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
-   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
-   UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
-   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
-   UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
-   UUID: Headset   (1108--1000-8000-00805f9b34fb)
-   UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
-   UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
-   Modalias: usb:v1D6Bp0246d0535
-   Discovering: yes
+  Name: mykyt
+  Alias: mykyt
+  Class: 0x001c010c
+  Powered: yes
+  Discoverable: yes
+  DiscoverableTimeout: 0x
+  Pairable: yes
+  UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
+  UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
+  UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
+  UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
+  UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
+  UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
+  UUID: Vendor specific   (5005--1000-8000-0002ee01)
+  UUID: Headset AG(1112--1000-8000-00805f9b34fb)
+  UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
+  UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
+  UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
+  UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
+  UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
+  UUID: Headset   (1108--1000-8000-00805f9b34fb)
+  UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
+  UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
+  Modalias: usb:v1D6Bp0246d0535
+  Discovering: yes
  Advertising Features:
-   ActiveInstances: 0x00
-   SupportedInstances: 0x05
-   SupportedIncludes: tx-power
-   SupportedIncludes: appearance
-   SupportedIncludes: local-name
-   SupportedSecondaryChannels: 1M
-   SupportedSecondaryChannels: 2M
-   SupportedSecondaryChannels: Coded
- 
+  ActiveInstances: 0x00
+  SupportedInstances: 0x05
+  SupportedIncludes: tx-power
+  SupportedIncludes: appearance
+  SupportedIncludes: local-name
+  SupportedSecondaryChannels: 1M
+  SupportedSecondaryChannels: 2M
+  SupportedSecondaryChannels: Coded
  
  i get:
  
  Failed to pair: org.bluez.Error.AuthenticationTimeout
  
  or
  
  Failed to pair: org.bluez.Error.AuthenticationCanceled
  
+ or
  
- I tried every single solution i was able to find for similar problems, 
including changing controller mode to bredr, reinstalling pulseaudio, 
unblocking rfkill, checking if my device is in pairable mode, using blueman and 
so on. 
+ Failed to pair: org.bluez.Error.Failed
+ 
+ I tried every single solution i was able to find for similar problems,
+ including changing controller mode to bredr, reinstalling pulseaudio,
+ unblocking rfkill, checking if my device is in pairable mode, using
+ blueman and so on.
  
  The fact is, bluetooth is working on my laptop (I can connect to my
  phone and my other bluetooth headset MEIZU EP51) and also my headset
  HOCO ES32 PLUS is working and is able to connect to my phone and my
  other laptop DELL INSPIRON 7359 which is running on ubuntu 18.04.
  
  I really hope you can help me. Please tell me if you need more information 
and I will provide it.
  Thank you!
  --
  
  lsb_release -rd
  
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  
- 
  apt-cache policy bluez
  
  bluez:
-   Installed: 5.53-0ubuntu3
-   Candidate: 5.53-0ubuntu3
-   

[Kernel-packages] [Bug 1924623] [NEW] Bluetooth headset pairing issue

[Mykyta]

Public bug reported:

I am unable to connect a HOCO ES32 PLUS bluetooth headset. Device is
visible and in pairable mode, but after running:

bluetoothctl

[bluetooth]# show
Controller 04:33:C2:AA:17:60 (public)
 Name: mykyt
 Alias: mykyt
 Class: 0x001c010c
 Powered: yes
 Discoverable: yes
 DiscoverableTimeout: 0x
 Pairable: yes
 UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
 UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
 UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
 UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
 UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
 UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
 UUID: Vendor specific   (5005--1000-8000-0002ee01)
 UUID: Headset AG(1112--1000-8000-00805f9b34fb)
 UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
 UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
 UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
 UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
 UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
 UUID: Headset   (1108--1000-8000-00805f9b34fb)
 UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
 UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
 Modalias: usb:v1D6Bp0246d0535
 Discovering: yes
Advertising Features:
 ActiveInstances: 0x00
 SupportedInstances: 0x05
 SupportedIncludes: tx-power
 SupportedIncludes: appearance
 SupportedIncludes: local-name
 SupportedSecondaryChannels: 1M
 SupportedSecondaryChannels: 2M
 SupportedSecondaryChannels: Coded

i get:

Failed to pair: org.bluez.Error.AuthenticationTimeout

or

Failed to pair: org.bluez.Error.AuthenticationCanceled

or

Failed to pair: org.bluez.Error.Failed

I tried every single solution i was able to find for similar problems,
including changing controller mode to bredr, reinstalling pulseaudio,
unblocking rfkill, checking if my device is in pairable mode, using
blueman and so on.

The fact is, bluetooth is working on my laptop (I can connect to my
phone and my other bluetooth headset MEIZU EP51) and also my headset
HOCO ES32 PLUS is working and is able to connect to my phone and my
other laptop DELL INSPIRON 7359 which is running on ubuntu 18.04.

I really hope you can help me. Please tell me if you need more information and 
I will provide it.
Thank you!
--

lsb_release -rd

Description:Ubuntu 20.04.2 LTS
Release:20.04

apt-cache policy bluez

bluez:
  Installed: 5.53-0ubuntu3
  Candidate: 5.53-0ubuntu3
  Version table:
 *** 5.53-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

--

Expected behavior:

After turning on bluetooth and clicking on device name in settings ->
bluetooth device is connecting and pairing successfully.

Current behavior:

Pairing fails.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-49-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 16 00:28:19 2021
InstallationDate: Installed on 2020-08-27 (231 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Acer Swift SF314-57G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=59c2b478-ae5a-4c28-8c13-6b3721fe1f3b ro nouveau.modeset=0 quiet 
splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2020
dmi.bios.release: 1.14
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.14
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Floris_IL
dmi.board.vendor: IL
dmi.board.version: V1.14
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd05/06/2020:br1.14:efr1.14:svnAcer:pnSwiftSF314-57G:pvrV1.14:rvnIL:rnFloris_IL:rvrV1.14:cvnAcer:ct10:cvrChassisVersion:
dmi.product.family: Swift 3
dmi.product.name: Swift SF314-57G
dmi.product.sku: 
dmi.product.version: V1.14
dmi.sys.vendor: Acer
hciconfig:
 hci0:  Type: Primary  Bus: USB
  BD Address: 04:33:C2:AA:17:60  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING PSCAN
  RX bytes:39055 acl:127 sco:0 events:3605 errors:0
  TX bytes:791744 acl:182 sco:0 commands:3327 errors:0
mtime.conffile..etc.bluetooth.network.conf: 2021-04-15T23:51:23.664531

** Affects: bluez (Ubuntu)
 Importance: 

[Kernel-packages] [Bug 1919342] Re: Stylus and touchscreen not working in kernel 5.8.0-45

[eldad]

Upgrading today a Thinkpad X1-Yoga (gen 1) to:
5.8.0-50-generic #56~20.04.1-Ubuntu SMP Mon Apr 12 21:46:35 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux

Resolved.

Many thanks!

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

Title:
  Stylus and touchscreen not working in kernel 5.8.0-45

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After an update from 16th March 2021, the stylus for Acer Spin 5
  stopped working and wasn't charging.

  Returning to version 5.8.0-43 fixed the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.30
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 16 16:12:45 2021
  InstallationDate: Installed on 2020-12-23 (82 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1923638] Re: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11

[Launchpad Bug Tracker]

This bug was fixed in the package evdi - 1.9.1-1ubuntu1

---
evdi (1.9.1-1ubuntu1) hirsute; urgency=medium

  * New upstream release 1.9.1
  * Fix build with Linux 5.11 (LP: #1923638)
- 
debian/patches/0001-Merge-branch-private-dczerwik-enable-cursor-ioctl-in.patch
- debian/patches/0002-Add-support-for-5.11-and-5.12-kernels.patch

 -- Paolo Pisati   Thu, 01 Apr 2021 14:24:23
+

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

Title:
  [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11

Status in evdi package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  evdi-dkms in hirsute cannot be used with the 5.11 kernel in hirsute as
  it will fail to build. Upstream updates for 5.11 proved problematic,
  and a working set of updates became available in the upstream project
  only recently. Unfortunately these updates are difficult to backport
  due to upstream changes, and if they are backported the kernel team
  has no access to hardware to confirm that the backports function as
  intended. Therefore the safest course of action seems to be to move
  forward to the latest upstream evdi release plus they fixes for 5.11
  from git, which has been tested by a number of evdi users already.

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

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

[Kernel-packages] [Bug 1924611] [NEW] setting extended attribute may cause memory leak

[Thadeu Lima de Souza Cascardo]

Public bug reported:

[Impact]
A memory leak may happen when an error happens when setting extended attributes.

[Fix]
The issue was introduced by an improper backport, so the fix is specific to 
Ubuntu, so a SAUCE patch.

[Test case]
Test setting attribute under a user namespace.

[Regression potential]
A double free bug might be introduced. Or setting extended attributes might 
fail.

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

** Affects: linux-gke-5.3 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-5.6 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-raspi2-5.3 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Xenial)
 Importance: Critical
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: linux-gke-5.3 (Ubuntu Xenial)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-5.6 (Ubuntu Xenial)
 Importance: Undecided
 Status: Invalid

** Affects: linux-raspi2-5.3 (Ubuntu Xenial)
 Importance: Undecided
 Status: Invalid

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

** Affects: linux-gke-5.3 (Ubuntu Bionic)
 Importance: Critical
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: Triaged

** Affects: linux-oem-5.6 (Ubuntu Bionic)
 Importance: Undecided
 Status: Invalid

** Affects: linux-raspi2-5.3 (Ubuntu Bionic)
 Importance: Critical
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

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

** Affects: linux-gke-5.3 (Ubuntu Focal)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-5.6 (Ubuntu Focal)
 Importance: Critical
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: Triaged

** Affects: linux-raspi2-5.3 (Ubuntu Focal)
 Importance: Undecided
 Status: Invalid

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

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

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

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

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

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

** Changed in: linux-oem-5.6 (Ubuntu)
   Status: New => Invalid

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

** Changed in: linux-oem-5.6 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: New => Triaged

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Importance: Undecided => Critical

** Changed in: linux-oem-5.6 (Ubuntu Focal)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

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

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

** Changed in: linux-oem-5.6 (Ubuntu Bionic)
   Status: New => Invalid

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

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

** Changed in: linux-gke-5.3 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-gke-5.3 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-gke-5.3 (Ubuntu Focal)
   Status: New => Invalid

** Changed in: linux-gke-5.3 (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: linux-gke-5.3 (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: linux-gke-5.3 (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux-raspi2-5.3 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-raspi2-5.3 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-raspi2-5.3 (Ubuntu Focal)
   Status: New => Invalid

** Changed in: linux-raspi2-5.3 (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: linux-raspi2-5.3 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux-raspi2-5.3 (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  setting extended attribute may cause memory leak

Status in linux package in 

[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ioanna Alifieraki]

Debdiff for Bionic V2.

** Patch added: "lp1879214_bionic_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5488489/+files/lp1879214_bionic_v2.debdiff

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

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Focal:
  Confirmed
Status in makedumpfile source package in Groovy:
  Confirmed
Status in makedumpfile source package in Hirsute:
  Fix Released
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  [Impact]

  On arm64 and kernels 5.4+ makedumpfile fails.

  Upstream patches solve this bug :

  [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option
  
https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab

  [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  
https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183

  [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  
https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583

  [Test Case]

  OS: Ubuntu 20.04 LTS
  kernel: 5.4.0-21-generic
  arch:arm64
  Description:
  When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test 
steps are as follows:
  # echo 1> / proc / sys / kernel / sysrq
  # echo c> / proc / sysrq-trigger
  The error logs are as follows:
  [   26.599161] kdump-tools[653]: Starting kdump-tools:
  [   26.612761] kdump-tools[659]: Starting kdump-tools:
  [   26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/2020050
  [   26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/2020050
  [   26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and 
VA Bits 47 not supported
  [   26.678199] kdump-tools[676]: get_machdep_info_arm64
  [   26.692518] kdump-tools[659]: get_machdep_info_arm64
  [   26.852221] hns3 :7d:00.0: get link status cmd failed -16

  [   94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * 
kdump-tools: saved vmcore in /var/crash/202005061048
  [   94.435510] kdump-tools[659]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/202005061048/dmesg.202005061048
  [   94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and 
VA Bits 47 not supported
  [   94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine 
platform config values
  [   94.485912] kdump-tools[688]: makedumpfile Failed.
  [   94.500760] kdump-tools[659]:  * kdump-tools: makedumpfile --dump-dmesg 
failed. dmesg content will be unavailable
  [   94.520225] kdump-tools[659]:  * kdump-tools: failed to save dmesg content 
in /var/crash/202005061048
  [   94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400
  [   94.564597] kdump-tools[692]: Rebooting.
  [   94.678709] reboot: Restarting systemlpc uart init Done

  [Regression Potential]

  Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage 
option
  removes get_elf_loads function this function was only used with --mem-usage 
option
  , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19)
  the information needed is in vmcoreinfo
  Any regression potential would affect the --mem-usage only

  Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  arm64 only
  make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing 
VA_BITS
  does not work on Linux 5.4 and later.
  Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, 
however
  this way of calculation breaks after 5.4. This commit gets the VA_BITS from 
vmcoreinfo
  and as a safeguard it uses the old way of deriving VA_BITS only if reading 
from vmcoreinfo doesn't work.

  From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later 
use later kernel so not
  great regression potentional and if any it would only affect arm64.

  Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  arm64 only
  Linux 5.4 and later kernels for arm64 changed the kernel VA space
  arrangement and introduced 52-bit kernel VAs by merging branch
  commit b333b0ba2346.  Support 5.9+ kernels with vmcoreinfo entries
  and 5.4+ kernels with best guessing.

  This patch makes adjustemnt to properly calculate vabits_actual, 
max_physmem_bits, page_offset
  Any regression potential would affect only arm64 and the calculation of the 
above variables.

  [Other]

  For H only the 3 commits are needed and they cherry-pick.

  For G and F the 3rd commit does not apply and 

[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ioanna Alifieraki]

Debdiff for Focal V2.

** Patch added: "lp1879214_focal_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5488488/+files/lp1879214_focal_v2.debdiff

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

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Focal:
  Confirmed
Status in makedumpfile source package in Groovy:
  Confirmed
Status in makedumpfile source package in Hirsute:
  Fix Released
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  [Impact]

  On arm64 and kernels 5.4+ makedumpfile fails.

  Upstream patches solve this bug :

  [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option
  
https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab

  [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  
https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183

  [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  
https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583

  [Test Case]

  OS: Ubuntu 20.04 LTS
  kernel: 5.4.0-21-generic
  arch:arm64
  Description:
  When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test 
steps are as follows:
  # echo 1> / proc / sys / kernel / sysrq
  # echo c> / proc / sysrq-trigger
  The error logs are as follows:
  [   26.599161] kdump-tools[653]: Starting kdump-tools:
  [   26.612761] kdump-tools[659]: Starting kdump-tools:
  [   26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/2020050
  [   26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/2020050
  [   26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and 
VA Bits 47 not supported
  [   26.678199] kdump-tools[676]: get_machdep_info_arm64
  [   26.692518] kdump-tools[659]: get_machdep_info_arm64
  [   26.852221] hns3 :7d:00.0: get link status cmd failed -16

  [   94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * 
kdump-tools: saved vmcore in /var/crash/202005061048
  [   94.435510] kdump-tools[659]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/202005061048/dmesg.202005061048
  [   94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and 
VA Bits 47 not supported
  [   94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine 
platform config values
  [   94.485912] kdump-tools[688]: makedumpfile Failed.
  [   94.500760] kdump-tools[659]:  * kdump-tools: makedumpfile --dump-dmesg 
failed. dmesg content will be unavailable
  [   94.520225] kdump-tools[659]:  * kdump-tools: failed to save dmesg content 
in /var/crash/202005061048
  [   94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400
  [   94.564597] kdump-tools[692]: Rebooting.
  [   94.678709] reboot: Restarting systemlpc uart init Done

  [Regression Potential]

  Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage 
option
  removes get_elf_loads function this function was only used with --mem-usage 
option
  , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19)
  the information needed is in vmcoreinfo
  Any regression potential would affect the --mem-usage only

  Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  arm64 only
  make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing 
VA_BITS
  does not work on Linux 5.4 and later.
  Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, 
however
  this way of calculation breaks after 5.4. This commit gets the VA_BITS from 
vmcoreinfo
  and as a safeguard it uses the old way of deriving VA_BITS only if reading 
from vmcoreinfo doesn't work.

  From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later 
use later kernel so not
  great regression potentional and if any it would only affect arm64.

  Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  arm64 only
  Linux 5.4 and later kernels for arm64 changed the kernel VA space
  arrangement and introduced 52-bit kernel VAs by merging branch
  commit b333b0ba2346.  Support 5.9+ kernels with vmcoreinfo entries
  and 5.4+ kernels with best guessing.

  This patch makes adjustemnt to properly calculate vabits_actual, 
max_physmem_bits, page_offset
  Any regression potential would affect only arm64 and the calculation of the 
above variables.

  [Other]

  For H only the 3 commits are needed and they cherry-pick.

  For G and F the 3rd commit does not apply and an 

[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ioanna Alifieraki]

Debdiff for Groovy V2.

** Patch added: "lp1879214_groovy_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5488487/+files/lp1879214_groovy_v2.debdiff

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

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Focal:
  Confirmed
Status in makedumpfile source package in Groovy:
  Confirmed
Status in makedumpfile source package in Hirsute:
  Fix Released
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  [Impact]

  On arm64 and kernels 5.4+ makedumpfile fails.

  Upstream patches solve this bug :

  [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option
  
https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab

  [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  
https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183

  [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  
https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583

  [Test Case]

  OS: Ubuntu 20.04 LTS
  kernel: 5.4.0-21-generic
  arch:arm64
  Description:
  When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test 
steps are as follows:
  # echo 1> / proc / sys / kernel / sysrq
  # echo c> / proc / sysrq-trigger
  The error logs are as follows:
  [   26.599161] kdump-tools[653]: Starting kdump-tools:
  [   26.612761] kdump-tools[659]: Starting kdump-tools:
  [   26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/2020050
  [   26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/2020050
  [   26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and 
VA Bits 47 not supported
  [   26.678199] kdump-tools[676]: get_machdep_info_arm64
  [   26.692518] kdump-tools[659]: get_machdep_info_arm64
  [   26.852221] hns3 :7d:00.0: get link status cmd failed -16

  [   94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * 
kdump-tools: saved vmcore in /var/crash/202005061048
  [   94.435510] kdump-tools[659]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/202005061048/dmesg.202005061048
  [   94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and 
VA Bits 47 not supported
  [   94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine 
platform config values
  [   94.485912] kdump-tools[688]: makedumpfile Failed.
  [   94.500760] kdump-tools[659]:  * kdump-tools: makedumpfile --dump-dmesg 
failed. dmesg content will be unavailable
  [   94.520225] kdump-tools[659]:  * kdump-tools: failed to save dmesg content 
in /var/crash/202005061048
  [   94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400
  [   94.564597] kdump-tools[692]: Rebooting.
  [   94.678709] reboot: Restarting systemlpc uart init Done

  [Regression Potential]

  Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage 
option
  removes get_elf_loads function this function was only used with --mem-usage 
option
  , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19)
  the information needed is in vmcoreinfo
  Any regression potential would affect the --mem-usage only

  Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  arm64 only
  make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing 
VA_BITS
  does not work on Linux 5.4 and later.
  Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, 
however
  this way of calculation breaks after 5.4. This commit gets the VA_BITS from 
vmcoreinfo
  and as a safeguard it uses the old way of deriving VA_BITS only if reading 
from vmcoreinfo doesn't work.

  From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later 
use later kernel so not
  great regression potentional and if any it would only affect arm64.

  Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  arm64 only
  Linux 5.4 and later kernels for arm64 changed the kernel VA space
  arrangement and introduced 52-bit kernel VAs by merging branch
  commit b333b0ba2346.  Support 5.9+ kernels with vmcoreinfo entries
  and 5.4+ kernels with best guessing.

  This patch makes adjustemnt to properly calculate vabits_actual, 
max_physmem_bits, page_offset
  Any regression potential would affect only arm64 and the calculation of the 
above variables.

  [Other]

  For H only the 3 commits are needed and they cherry-pick.

  For G and F the 3rd commit does not apply and 

[Kernel-packages] [Bug 1923888] Re: Apply Patch to 4.15 kernels which will resolve a netvsc bug

[Tim Gardner]

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

** This bug has been marked a duplicate of bug 1924314
   netvsc may cause CPU lockup

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

Title:
  Apply Patch to 4.15 kernels which will resolve a netvsc bug

Status in linux-azure package in Ubuntu:
  New

Bug description:
  A soft lockup is happening to Customers due to a bug in netvsc_poll.

  Ubuntu 4.15.0-1103 has CONFIG_NET_POLL_CONTROLLER=y in kernel config
  file, there is a bug in netvsc that may cause CPU lockup with
  POLL_CONTROLLER. This bug  has been fixed by the following patch:

  
  commit 2a7f8c3b1d3feedee3aa319ac220cbde3725b5d5
  Author: Stephen Hemminger 
  Date:   Sat Sep 29 14:52:56 2018 +0200

  hv_netvsc: remove ndo_poll_controller

  
  This commit is in mainline as of 4.20-rc1.

  Microsoft would like to request this patch in 4.15 based Azure
  kernels.

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

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

[Kernel-packages] [Bug 1923737] Re: TLP aggressively suspends active USB audio devices when on AC

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-mate-settings - 21.04.8

---
ubuntu-mate-settings (21.04.8) hirsute; urgency=medium

  * Disable TLP USB autosuspend. (LP: #1923737)

 -- Martin Wimpress   Wed, 14 Apr 2021 10:17:41 +0100

** Changed in: ubuntu-mate-settings (Ubuntu)
   Status: Fix Committed => 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/1923737

Title:
  TLP aggressively suspends active USB audio devices when on AC

Status in linux package in Ubuntu:
  Confirmed
Status in tlp package in Ubuntu:
  New
Status in ubuntu-mate-settings package in Ubuntu:
  Fix Released

Bug description:
  Expected behaviour:

  When running Ubuntu 21.04 on desktop hardware any active USB audio
  devices should not be suspended while playing/recording audio.

  Actual behaviour:

  When running Ubuntu 21.04 on desktop hardware active USB audio devices
  that are playing/recording audio are suspended after a few seconds.

  This upstream bug appears relevant and seems to lay the blame
  elsewhere, perhaps the kernel.

* https://github.com/linrunner/TLP/issues/545
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  martin52211 F pulseaudio
   /dev/snd/controlC4:  martin52211 F pulseaudio
   /dev/snd/controlC1:  martin52211 F pulseaudio
   /dev/snd/controlC0:  martin52211 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-19 (176 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201019)
  MachineType: Gigabyte Technology Co., Ltd. TRX40 DESIGNARE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: ubuntu-mate-settings
  PackageArchitecture: all
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=e1cb7300-2f01-4638-9e29-764441684c38 ro quiet splash noibrs noibpb 
nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable 
no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-13-generic N/A
   linux-backports-modules-5.11.0-13-generic  N/A
   linux-firmware 1.197
  Tags:  hirsute apport-hook-error
  Uname: Linux 5.11.0-13-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-04-09 (4 days ago)
  UserGroups: adm audio cdrom dip input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2020
  dmi.bios.release: 5.15
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FBd
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 DESIGNARE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFBd:bd09/25/2020:br5.15:svnGigabyteTechnologyCo.,Ltd.:pnTRX40DESIGNARE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40DESIGNARE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 DESIGNARE
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1917433] Re: riscv: revert SiFive Unleashed CPUFreq

[Launchpad Bug Tracker]

This bug was fixed in the package linux-riscv - 5.8.0-22.24

---
linux-riscv (5.8.0-22.24) groovy; urgency=medium

  [ Ubuntu: 5.8.0-50.56 ]

  * overlayfs calls vfs_setxattr without cap_convert_nscap
- vfs: move cap_convert_nscap() call into vfs_setxattr()
  * CVE-2021-3492
- SAUCE: shiftfs: free allocated memory in shiftfs_btrfs_ioctl_fd_replace()
  error paths
- SAUCE: shiftfs: handle copy_to_user() return values correctly
  * CVE-2021-29154
- SAUCE: bpf, x86: Validate computation of branch displacements for x86-64
- SAUCE: bpf, x86: Validate computation of branch displacements for x86-32

 -- Kelsey Skunberg   Mon, 12 Apr 2021
15:36:17 -0600

** Changed in: linux-riscv (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29154

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3492

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

Title:
   riscv: revert SiFive Unleashed CPUFreq

Status in linux-riscv package in Ubuntu:
  Fix Released
Status in linux-riscv source package in Groovy:
  Fix Released

Bug description:
  == SRU Justifcation Groovy/RISCV ==

  The SiFive Unleashed board with the current Ubuntu cpufreq default
  config can hang on boot with CPU freq enabled with the latest device
  tree settings.  It is known that the cpufreq can be problematic so the
  recommended way forward is to currently revert the cpufreq enablement
  commit

  commit 3949df6ecdca04339bc8a3925c2ba7f881cf82b1
  Author: David Abdurachmanov 
  Date:   Tue Jan 28 02:55:56 2020 -0800

  SiFive Unleashed CPUFreq

  
  == The fix(es) ==

  Revert commit "SiFive Unleashed CPUFreq"

  == Test Case ==

  Boot with the latest DT. It should now boot. Boot without the latest
  DT, it should also boot.

  == Where problems could occur ==

  1. Users expecting CPU freq scaling now don't have this working
  option. This is deemed to be acceptable as without the fix their
  systems are likely to be unbootable with the updated DT.

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

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

[Kernel-packages] [Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

[Wes Newell]

Kernel 5.4.0-71 has finally fixed the problem. Having just installed it,
I have not run extensive test on it, but it appears to be stable.

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

Title:
  Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run mythtv on Ubuntu 20.04 and I used a custom remote control keymap
  in /etc/rc_keymaps to correctly map buttons on my IR remote.  The
  above kernel seems to break custom keymap loading for my remote
  (certain buttons no longer work in mythtv).  Reverting to kernel
  5.4.0-48 corrects the problem.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  linux-image-5.4.0-52-generic:
Installed: 5.4.0-52.57
Candidate: 5.4.0-52.57
Version table:
   *** 5.4.0-52.57 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  belongs to the linux source package

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pdaniel1552 F pulseaudio
   /dev/snd/controlC0:  pdaniel1552 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Oct 22 16:16:58 2020
  InstallationDate: Installed on 2017-04-17 (1284 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7792
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=38b7dfb0-9848-4919-890b-fdc027e936f1 ro radeon.dpm=0 quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-11 (164 days ago)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FM2-A75IA-E53 (MS-7792)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd02/12/2015:svnMSI:pnMS-7792:pvr1.0:rvnMSI:rnFM2-A75IA-E53(MS-7792):rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7792
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

[RBX2]

The problem I reported here was NOT fixed by the latest kernel update
(5.4.0-71).

To clarify what I observe on my AMD-based desktop:
The suspend/hibernation/resume problem seems to be strictly related to the 
amdgpu kernel module and possibly also amdgpu Xorg driver. I have tested the 
following scenarios.

1) kernel 5.4.0-71 with ACP enabled:
 - Xorg vesa driver loaded & no acceleration
 - suspend seems ok but fails on resume
 - hibernation/resume ok

2) kernel 5.4.0-71 with ACP disabled:
 - Xorg amdgpu driver loaded & acceleration working
 - suspend/resume ok
 - hibernation fails

3) kernel 5.8.0-49 with ACP disabled:
 - Xorg amdgpu driver loaded & acceleration working
 - suspend/resume ok
 - hibernation fails

4) kernel 5.8.0-49 with ACP enabled:
 - I only get black screen - Xorg fails to start?
 - suspend/hibernation not tested

I have no problems with hibernation/suspend/resume on any of my Intel-
based laptops. I also have no problem on most of my older AMD-based
desktops.

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

Title:
  AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear developers, please let me thank you for all your hard work first
  of all, I'm a big fan of yours!

  On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which
  seem to be connected to the amdgpu kernel module:

  1. Amdgpu kernel module loads correctly during boot, but VESA Xorg
  module is loaded instead of AMDGPU Xorg module during X startup. This
  results in non-accelerated X and high CPU load.

  - This situation is always reproducible.

  - I'm experiencing it with all kernel versions in between
  5.4.0-47-generic and 5.4.0-67-generic inclusive.

  - The situation escalates more with newer kernel version. For
  5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and
  I just get black screen.

  - I have found a workaround after many days of googling and testing. AMDGPU 
Xorg module is loaded correctly if and only if I disable AMD ACP by means of 
the following kernel boot parameter:
  amdgpu.ip_block_mask=0xfdff

  - Acceleration is ok with kernels where AMD ACP is disabled by default
  (linux-image-linuxlite-5.6.0 for example)

  
  2. The 2nd problem I'm facing is with non functioning hibernation after I 
"fixed" the X acceleration. Hibernation image does not seem to get created, 
screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module 
is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by 
means of "nomodeset" and go just with VESA module.

  - always reproducible but tested only with 5.4.0-67-generic

  
  Thank you and best regards,
  Radek

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-67-generic 5.4.0-67.75
  ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
  Uname: Linux 5.4.0-67-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  radek  1513 F pulseaudio
   /dev/snd/controlC0:  radek  1513 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Mar 21 15:22:29 2021
  HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic 
root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 
nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff 
no_console_suspend
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-67-generic N/A
   linux-backports-modules-5.4.0-67-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.20
  dmi.board.name: FM2A68M-HD+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

-- 

[Kernel-packages] [Bug 1896598] Re: Enable LTR for endpoints behind VMD

[Anthony Wong]

** Changed in: linux-oem-5.6 (Ubuntu)
   Status: New => Invalid

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Enable LTR for endpoints behind VMD

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact] 
  PCIe links behind VMD may not be able to reach ASPM L1.2, because PCIe
  Link Tolenrence Reporting doesn't get programmed with a sensible value.

  [Fix]
  Temporarily hardcode LTR value, which is used by Windows, for NVMe 
  devices behind VMD.

  [Test]
  With the patch applied, PCIe links can reach ASPM L1.2, hence the entire
  Intel SoC can reach deeper power saving state.

  [Regression Potential]
  This patch targets specifically Intel Tigerlake VMD bridges, so there
  won't be any regression since they are not on the market yet.

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

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

[Kernel-packages] [Bug 1923638] Re: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11

[Iain Lane]

Would have preferred this to come much earlier, but sounds like
something we need to do ...

Please make sure to keep an eye out for bugs.

I'll accept, thanks.

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

Title:
  [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11

Status in evdi package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  evdi-dkms in hirsute cannot be used with the 5.11 kernel in hirsute as
  it will fail to build. Upstream updates for 5.11 proved problematic,
  and a working set of updates became available in the upstream project
  only recently. Unfortunately these updates are difficult to backport
  due to upstream changes, and if they are backported the kernel team
  has no access to hardware to confirm that the backports function as
  intended. Therefore the safest course of action seems to be to move
  forward to the latest upstream evdi release plus they fixes for 5.11
  from git, which has been tested by a number of evdi users already.

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

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

[Kernel-packages] [Bug 1924588] Re: P2P mode doesn't work in qla2xxx

[Launchpad Bug Tracker]

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

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

Title:
  P2P mode doesn't work in  qla2xxx

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  QLogic FC adapters don't work in direct mode on focal (at least
  QLE2692, and QLE2694, QLE2742 are affected):

  [  266.821659] qla2xxx [:05:00.0]-3874:3: ELS_DCMD PLOGI sent, hdl=1a, 
loopid=0, to port_id 02 from port_id 01
  [  266.822926] qla2xxx [:05:00.0]-583f:3: ELS IOCB Done -Driver ELS logo 
error hdl=1a comp_status=0x0 error subcode 1=0x0 error subcode 2=0x0 
total_byte=0x74
  [  266.822933] qla2xxx [:05:00.0]-3872:3: ELS_DCMD ELS done rc 0 hdl=1a, 
portid=02 21:00:34:80:0d:74:14:d2
  [  266.822937] qla2xxx [:05:00.0]-2918:3: qla_handle_els_plogi_done 1764 
21:00:34:80:0d:74:14:d2 post PRLI
  [  266.822965] qla2xxx [:05:00.0]-291b:3: Async-prli - 
21:00:34:80:0d:74:14:d2 hdl=0, loopid=0 portid=02 retries=29 nvme.
  [  266.823008] qla2xxx [:05:00.0]-5837:3: Async-prli failed - 
21:00:34:80:0d:74:14:d2 hdl=1b portid=02 comp=31 iop0=18 iop1=b.
  [  266.823011] qla2xxx [:05:00.0]-2929:3: qla2x00_async_prli_sp_done 
21:00:34:80:0d:74:14:d2 res 0
  [  266.823014] qla2xxx [:05:00.0]-2918:3: qla24xx_handle_prli_done_event 
1934 21:00:34:80:0d:74:14:d2 post NVMe prli
  [  266.823019] qla2xxx [:05:00.0]-e801:3: Scheduling sess 
a438982b for deletion 21:00:34:80:0d:74:14:d2
  [  266.823031] qla2xxx [:05:00.0]-290a:3: qlt_unreg_sess sess 
a438982b for deletion 21:00:34:80:0d:74:14:d2
  [  266.823039] qla2xxx [:05:00.0]-f884:3: qlt_free_session_done: se_sess 
 / sess a438982b from port 21:00:34:80:0d:74:14:d2 
loop_id 0x00 s_id 00:00:02 logout 1 keep 0 els_logo 0
  [  266.823043] qla2xxx [:05:00.0]-f886:3: qlt_free_session_done: waiting 
for sess a438982b logout
  [  266.823066] qla2xxx [:05:00.0]-2870:3: Async-logout - hdl=0 loop-id=0 
portid=02 21:00:34:80:0d:74:14:d2.
  [  266.823087] qla2xxx [:05:00.0]-5836:3: Async-logout complete - 
21:00:34:80:0d:74:14:d2 hdl=1c portid=02 iop0=0.
  [  266.823093] qla2xxx [:05:00.0]-f893:3: qlt_logo_completion_handler: 
se_sess  / sess a438982b from port 
21:00:34:80:0d:74:14:d2 loop_id 0x00 s_id 00:00:02 LOGO failed: 0x0
  [  266.928413] qla2xxx [:05:00.0]-f887:3: qlt_free_session_done: sess 
a438982b logout completed
  [  266.931754] qla2xxx [:05:00.0]-f89a:3: se_sess  / sess 
a438982b port 21:00:34:80:0d:74:14:d2 is gone, no own PLOGI pending 
(ref=-1)

  The snippet above shows that qla2xxx is trying to send NVMe PRLI
  instead of FCP PRLI to FCP target and link connection doesn't succeed.

  The same bug exists in linux-stable since 5.4.69. P2P worked until
  5.4.69 but issue_lip was broken and link was not recovered after
  issue_lip.

  We have triaged the issue and found a way to fix it by backporting and
  properly merging upstream patches and will send a series to linux-
  stable shortly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-71-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  Date: Thu Apr 15 15:43:55 2021
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M

[Kernel-packages] [Bug 1924588] [NEW] P2P mode doesn't work in qla2xxx

[Anastasia Kovaleva]

Public bug reported:

QLogic FC adapters don't work in direct mode on focal (at least QLE2692,
and QLE2694, QLE2742 are affected):

[  266.821659] qla2xxx [:05:00.0]-3874:3: ELS_DCMD PLOGI sent, hdl=1a, 
loopid=0, to port_id 02 from port_id 01
[  266.822926] qla2xxx [:05:00.0]-583f:3: ELS IOCB Done -Driver ELS logo 
error hdl=1a comp_status=0x0 error subcode 1=0x0 error subcode 2=0x0 
total_byte=0x74
[  266.822933] qla2xxx [:05:00.0]-3872:3: ELS_DCMD ELS done rc 0 hdl=1a, 
portid=02 21:00:34:80:0d:74:14:d2
[  266.822937] qla2xxx [:05:00.0]-2918:3: qla_handle_els_plogi_done 1764 
21:00:34:80:0d:74:14:d2 post PRLI
[  266.822965] qla2xxx [:05:00.0]-291b:3: Async-prli - 
21:00:34:80:0d:74:14:d2 hdl=0, loopid=0 portid=02 retries=29 nvme.
[  266.823008] qla2xxx [:05:00.0]-5837:3: Async-prli failed - 
21:00:34:80:0d:74:14:d2 hdl=1b portid=02 comp=31 iop0=18 iop1=b.
[  266.823011] qla2xxx [:05:00.0]-2929:3: qla2x00_async_prli_sp_done 
21:00:34:80:0d:74:14:d2 res 0
[  266.823014] qla2xxx [:05:00.0]-2918:3: qla24xx_handle_prli_done_event 
1934 21:00:34:80:0d:74:14:d2 post NVMe prli
[  266.823019] qla2xxx [:05:00.0]-e801:3: Scheduling sess a438982b 
for deletion 21:00:34:80:0d:74:14:d2
[  266.823031] qla2xxx [:05:00.0]-290a:3: qlt_unreg_sess sess 
a438982b for deletion 21:00:34:80:0d:74:14:d2
[  266.823039] qla2xxx [:05:00.0]-f884:3: qlt_free_session_done: se_sess 
 / sess a438982b from port 21:00:34:80:0d:74:14:d2 
loop_id 0x00 s_id 00:00:02 logout 1 keep 0 els_logo 0
[  266.823043] qla2xxx [:05:00.0]-f886:3: qlt_free_session_done: waiting 
for sess a438982b logout
[  266.823066] qla2xxx [:05:00.0]-2870:3: Async-logout - hdl=0 loop-id=0 
portid=02 21:00:34:80:0d:74:14:d2.
[  266.823087] qla2xxx [:05:00.0]-5836:3: Async-logout complete - 
21:00:34:80:0d:74:14:d2 hdl=1c portid=02 iop0=0.
[  266.823093] qla2xxx [:05:00.0]-f893:3: qlt_logo_completion_handler: 
se_sess  / sess a438982b from port 
21:00:34:80:0d:74:14:d2 loop_id 0x00 s_id 00:00:02 LOGO failed: 0x0
[  266.928413] qla2xxx [:05:00.0]-f887:3: qlt_free_session_done: sess 
a438982b logout completed
[  266.931754] qla2xxx [:05:00.0]-f89a:3: se_sess  / sess 
a438982b port 21:00:34:80:0d:74:14:d2 is gone, no own PLOGI pending 
(ref=-1)

The snippet above shows that qla2xxx is trying to send NVMe PRLI instead
of FCP PRLI to FCP target and link connection doesn't succeed.

The same bug exists in linux-stable since 5.4.69. P2P worked until
5.4.69 but issue_lip was broken and link was not recovered after
issue_lip.

We have triaged the issue and found a way to fix it by backporting and
properly merging upstream patches and will send a series to linux-stable
shortly.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-71-generic 5.4.0-71.79
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-71-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: skip
Date: Thu Apr 15 15:43:55 2021
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-71-generic 
root=UUID=fed00282-cd6d-405e-ba8d-3f1d5cd7bcff ro net.ifnames=0 biosdevname=0 
quiet console=ttyS0 console=tty1
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-71-generic N/A
 linux-backports-modules-5.4.0-71-generic  N/A
 linux-firmware1.187.10
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux

[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[Lux Libertas]

Installed it from here.. 
https://github.com/mohamed-badaoui/ux433-touchpad-numpad

Works perfectly well on UX425EA!

Thanks!!!

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

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

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute

[Paride Legovini]

Hi Guilherme,

Answering your question in comment #6:

> Why one method executes from DataSourceAzure.py
> whereas the other from azure.py?

The reason is not that interesting and won't really help here. Some log
messages generated in DataSourceAzure.py are logged using a helper
function defined in azure.py, while some others are logged directly from
DataSourceAzure.py. Honestly I'm not completely sure on why we have this
difference, it could be in part a legacy thing. In any case the
interesting logic is all in DataSourceAzure.py.

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

Title:
  Azure: issues with accelerated networking on Hirsute

Status in cloud-init:
  Incomplete
Status in cloud-init package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New

Bug description:
  [General]

  On Azure, when provisioning a Hirsute VM with Accelerated Networking
  enabled, sometimes the SSH key is not setup properly and the user
  cannot log into the VM.

  [how to reproduce]

  Start a VM with AN enabled:

  ```
  az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South" 
 --image 
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size 
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" 
--accelerated-networking
  ```

  After a moment, try to SSH: if you succeed, delete and recreate a new
  VM.

  [troubleshooting]

  To be able to connect into the VM to debug, run:

  ```
  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id 
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
  ```

  In "/run/cloud-init/instance-data.json", I can see:
  ```
   "publicKeys": [
{
 "keyData": "",
 "path": "/home/ubuntu/.ssh/authorized_keys"
}
   ],
  ```

  as expected.

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

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

[Kernel-packages] [Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Merge proposal linked:
   
https://code.launchpad.net/~joalif/ubuntu/+source/crash/+git/crash/+merge/401229

** Merge proposal linked:
   
https://code.launchpad.net/~joalif/ubuntu/+source/crash/+git/crash/+merge/401230

** Merge proposal linked:
   
https://code.launchpad.net/~joalif/ubuntu/+source/crash/+git/crash/+merge/401231

** Merge proposal linked:
   
https://code.launchpad.net/~joalif/ubuntu/+source/crash/+git/crash/+merge/401232

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in crash source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in crash source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in crash source package in Groovy:
  Confirmed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug has been addressed upstream and needed patches both in crash
  and kernel.

  Kernel patch :

  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

  Crash patch :

  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530

  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ

  
  Series affected :

  Kenrel : 
  This affects Focal (5.4 kernel)  and Groovy (5.8 kernel).
  Hirsute already contains the commit and kernels prior to 5.3 are not affected.

  Crash :
  The commit is already in Hirsute.
  Groovy, Focal and Bionic are affected.
  In case of Bionic the bug appears only if 5.4 hwe kernel is used.

  [Test Case]

  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL

  [Where problems could occur]

  Kernel patch :

  The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
  and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
  Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.

  Crash patch :

  This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
  The regression potential is small and any problem would regard reading this 
variable.

  [Other]

  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.

  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

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

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

[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container

[Younes Manton]

In the same boat as buck2202 and nfliu; we're doing some work in IBM
that uses Docker+criu so we're very interested in a fix for current LTS
releases as well.

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

Title:
  linux-image-5.0.0-35-generic breaks checkpointing of container

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Confirmed

Bug description:
  Trying to checkpoint a container (docker/podman) on 18.04 fails
  starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see
  this in Travis starting a few weeks ago. Manually testing it locally
  shows that linux-image-5.0.0-32-generic still works and linux-
  image-5.0.0-35-generic does not longer work. It seems to be overlayfs
  related, at least that is what we believe. The CRIU error message we
  see is:

  (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 
path=/bin/busybox
  (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed 
with -1

  
  We have not seen this only in Travis, but also multiple CRIU users reported 
that bug already. Currently we have to tell them to downgrade the kernel.

  I also able to reproduce it with linux-image-5.3.0-24-generic. Staying
  on the 4.18.0 kernel series does not show this error.
  4.18.0-25-generic works without problems.

  See also https://github.com/checkpoint-restore/criu/issues/860

  One of the possible explanations from our side include:

  "Looks like we have the same as for st_dev now with mnt_id, that is
  bad, because we can't find on which mount to open the file if kernel
  hides these information from us."

  Running on the upstream 5.5.0-rc1 kernel does not show this error.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 18:52 seq
   crw-rw 1 root audio 116, 33 Jan  7 18:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.11-0ubuntu8.2
  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:
  CRDA: N/A
  DistroRelease: Ubuntu 19.10
  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: DigitalOcean Droplet
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20171212
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
  dmi.product.family: DigitalOcean_Droplet
  dmi.product.name: Droplet
  dmi.product.version: 20171212
  dmi.sys.vendor: DigitalOcean

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

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

[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

[Brian Murray]

** Tags removed: rls-hh-incoming
** Tags added: rls-ff-incoming

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

Title:
  unexpected error pop-up after 'apt install nvidia-driver-455'

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu info:

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52)
  Release 20.04

  Full reproduce step

  1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first 
place, without all i386 pkg installed.
  2. run update-manager to do upgrade.
  3. it will show error after download deb and didn't upgrade anything.

  Per test with the command to do the upgrade, it will have an extra
  error message, but it will just upgrade and install recommended i386
  debs.

  The error msgs are:

  E: Could not configure 'libc6:i386'.
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  Short way to get the error:
  # apt-get install libgcc-s1:i386 --dry-run
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 
gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16
libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 
libunistring2:i386
  Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
  The following NEW packages will be installed:
gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 
libunistring2:i386
  The following packages will be upgraded:
libc6
  1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded.
  Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates 
[amd64])
  Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) []
  Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) []
  Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386])
  Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386])
  Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  E: Could not configure 'libc6:i386'. 
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  For now, we think the above Error is the root cause of update-manager
  failure.

  ---

  This happens as upgrade package nvidia-driver-455 from
  455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1.

  for more detail, please check the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions

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

[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

[Dimitri John Ledkov]

20.04.1 is obsolete point release. Can you please try with 20.04.2?

** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
   Status: New => Incomplete

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

Title:
  unexpected error pop-up after 'apt install nvidia-driver-455'

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu info:

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52)
  Release 20.04

  Full reproduce step

  1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first 
place, without all i386 pkg installed.
  2. run update-manager to do upgrade.
  3. it will show error after download deb and didn't upgrade anything.

  Per test with the command to do the upgrade, it will have an extra
  error message, but it will just upgrade and install recommended i386
  debs.

  The error msgs are:

  E: Could not configure 'libc6:i386'.
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  Short way to get the error:
  # apt-get install libgcc-s1:i386 --dry-run
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 
gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16
libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 
libunistring2:i386
  Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
  The following NEW packages will be installed:
gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 
libunistring2:i386
  The following packages will be upgraded:
libc6
  1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded.
  Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates 
[amd64])
  Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) []
  Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) []
  Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386])
  Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386])
  Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  E: Could not configure 'libc6:i386'. 
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  For now, we think the above Error is the root cause of update-manager
  failure.

  ---

  This happens as upgrade package nvidia-driver-455 from
  455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1.

  for more detail, please check the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions

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

[Kernel-packages] [Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Changed in: crash (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in crash source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in crash source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in crash source package in Groovy:
  Confirmed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug has been addressed upstream and needed patches both in crash
  and kernel.

  Kernel patch :

  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

  Crash patch :

  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530

  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ

  
  Series affected :

  Kenrel : 
  This affects Focal (5.4 kernel)  and Groovy (5.8 kernel).
  Hirsute already contains the commit and kernels prior to 5.3 are not affected.

  Crash :
  The commit is already in Hirsute.
  Groovy, Focal and Bionic are affected.
  In case of Bionic the bug appears only if 5.4 hwe kernel is used.

  [Test Case]

  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL

  [Where problems could occur]

  Kernel patch :

  The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
  and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
  Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.

  Crash patch :

  This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
  The regression potential is small and any problem would regard reading this 
variable.

  [Other]

  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.

  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

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

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

[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

[Julian Andres Klode]

I mean 2.0.4, of course, which is included in the current LTS images
(20.04.2); your image is the previous version (20.04.1)

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

Title:
  unexpected error pop-up after 'apt install nvidia-driver-455'

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  New

Bug description:
  Ubuntu info:

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52)
  Release 20.04

  Full reproduce step

  1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first 
place, without all i386 pkg installed.
  2. run update-manager to do upgrade.
  3. it will show error after download deb and didn't upgrade anything.

  Per test with the command to do the upgrade, it will have an extra
  error message, but it will just upgrade and install recommended i386
  debs.

  The error msgs are:

  E: Could not configure 'libc6:i386'.
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  Short way to get the error:
  # apt-get install libgcc-s1:i386 --dry-run
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 
gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16
libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 
libunistring2:i386
  Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
  The following NEW packages will be installed:
gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 
libunistring2:i386
  The following packages will be upgraded:
libc6
  1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded.
  Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates 
[amd64])
  Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) []
  Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) []
  Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386])
  Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386])
  Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  E: Could not configure 'libc6:i386'. 
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  For now, we think the above Error is the root cause of update-manager
  failure.

  ---

  This happens as upgrade package nvidia-driver-455 from
  455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1.

  for more detail, please check the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions

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

[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

[Julian Andres Klode]

It seems you are not using libapt-pkg6.0 in version 2.1.10ubuntu0.2 or
later? This issue was fixed in that version.

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

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

Title:
  unexpected error pop-up after 'apt install nvidia-driver-455'

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  New

Bug description:
  Ubuntu info:

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52)
  Release 20.04

  Full reproduce step

  1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first 
place, without all i386 pkg installed.
  2. run update-manager to do upgrade.
  3. it will show error after download deb and didn't upgrade anything.

  Per test with the command to do the upgrade, it will have an extra
  error message, but it will just upgrade and install recommended i386
  debs.

  The error msgs are:

  E: Could not configure 'libc6:i386'.
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  Short way to get the error:
  # apt-get install libgcc-s1:i386 --dry-run
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 
gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16
libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 
libunistring2:i386
  Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
  The following NEW packages will be installed:
gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 
libunistring2:i386
  The following packages will be upgraded:
libc6
  1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded.
  Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates 
[amd64])
  Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) []
  Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) []
  Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386])
  Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386])
  Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  E: Could not configure 'libc6:i386'. 
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  For now, we think the above Error is the root cause of update-manager
  failure.

  ---

  This happens as upgrade package nvidia-driver-455 from
  455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1.

  for more detail, please check the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions

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

[Kernel-packages] [Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

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

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

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

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

** Description changed:

  [Impact]
  
  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:
  
  crash: cannot determine VA_BITS_ACTUAL
  
  This bug has been addressed upstream and needed patches both in crash
  and kernel.
  
  Kernel patch :
  
  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo
  
  Crash patch :
  
  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530
  
  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ
  
+ 
+ Series affected :
+ 
+ Kenrel : 
+ This affects Focal (5.4 kernel)  and Groovy (5.8 kernel).
+ Hirsute already contains the commit and kernels prior to 5.3 are not affected.
+ 
+ Crash :
+ The commit is already in Hirsute.
+ Groovy, Focal and Bionic are affected.
+ In case of Bionic the bug appears only if 5.4 hwe kernel is used.
+ 
  [Test Case]
  
  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL
  
  [Where problems could occur]
  
  Kernel patch :
  
  The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
  and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
  Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.
  
  Crash patch :
  
  This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
  The regression potential is small and any problem would regard reading this 
variable.
  
- 
  [Other]
  
  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.
  
  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in crash source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in crash source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in crash source package in Groovy:
  Confirmed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug has been addressed upstream and needed patches both in crash
  and kernel.

  Kernel patch :

  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

  Crash patch :

  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530

  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ

  
  Series affected :

  Kenrel : 
  This affects Focal (5.4 kernel)  and Groovy (5.8 kernel).
  Hirsute already contains the commit and kernels prior to 5.3 are not affected.

  Crash :
  The commit is already in Hirsute.
  Groovy, Focal and Bionic are affected.
  In case of Bionic the bug appears only if 5.4 hwe kernel is used.

  [Test Case]

  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL

  [Where problems could occur]

  Kernel patch :

  The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
  and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
  Any potential problem would occur in vmcoreinfo since this is where 

[Kernel-packages] [Bug 1923670] Re: CIFS DFS entries not accessible with 5.4.0-71.74-generic

[Tim Gardner]

That is my goal.

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

Title:
  CIFS DFS entries not accessible with 5.4.0-71.74-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  When booting 5.4.0-71-generic I can not access DFS entries anymore,
  with 5.4.0-70-generic this still works. Some details:

  fstab entry:

  //example.com/public /home/user/remotecifs
  
noauto,vers=default,noserverino,users,_netdev,user=remote_user,domain=example.com
  00

  shell session
  ~$ mount /home/user/remote
  Password for remote_user@//example.com/public:
  ~$ ls /home/user/remote/dfs-folder
  dfs-subfolder dfs-entry
  ~$ ls /home/user/remote/dfs-folder/dfs-entry
  ls: cannot access '/home/user/remote/dfs-folder/dfs-entry': No such file or 
directory

  dmesg excerpt
  [ 1219.568778] CIFS: Attempting to mount 
//DC01.example.com/Public/dfs-folder/dfs-entry
  [ 1219.584975] FS-Cache: Duplicate cookie detected
  [ 1219.584986] FS-Cache: O-cookie c=6e995395 [p=f4725c61 
fl=222 nc=0 na=1]
  [ 1219.584990] FS-Cache: O-cookie d=a11c1428 n=71ab21ba
  [ 1219.584993] FS-Cache: O-key=[6] '5075626c6963'
  [ 1219.585001] FS-Cache: N-cookie c=a0608786 [p=f4725c61 fl=2 
nc=0 na=1]
  [ 1219.585004] FS-Cache: N-cookie d=a11c1428 n=901f6a53
  [ 1219.585007] FS-Cache: N-key=[6] '5075626c6963'
  [ 1219.725834] FS-Cache: Duplicate cookie detected
  [ 1219.725847] FS-Cache: O-cookie c=6e995395 [p=f4725c61 
fl=222 nc=0 na=1]
  [ 1219.725851] FS-Cache: O-cookie d=a11c1428 n=71ab21ba
  [ 1219.725854] FS-Cache: O-key=[6] '5075626c6963'
  [ 1219.725864] FS-Cache: N-cookie c=0509709f [p=f4725c61 fl=2 
nc=0 na=1]
  [ 1219.725868] FS-Cache: N-cookie d=a11c1428 n=556f158b
  [ 1219.725870] FS-Cache: N-key=[6] '5075626c6963'
  [ 1220.216524] CIFS VFS: cifs_read_super: get root inode failed

  The dmesg from 5.4.0-70-generic does not have the line
  CIFS VFS: cifs_read_super: get root inode failed

  
  ~$ lsb_release -rd
  Description:KDE neon User Edition 5.21
  Release:   ~$ lsb_release -rd
  Description:KDE neon User Edition 5.21
  Release:20.04
   20.04
  ~$ apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 5.4.0.71.74
Candidate: 5.4.0.71.74
Version table:
   *** 5.4.0.71.74 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.4.0.26.32 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dirk   2946 F pulseaudio
   /dev/snd/controlC1:  dirk   2946 F pulseaudio
   /dev/snd/controlC0:  dirk   2946 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: KDE neon 20.04
  InstallationDate: Installed on 2017-07-27 (1356 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20170614-00:52
  MachineType: LENOVO 20HMS00T00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/vg00-lv_root ro intel_iommu=off
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-71-generic N/A
   linux-backports-modules-5.4.0-71-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.4.0-71-generic x86_64
  UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht 
installiert ist.
  UpgradeStatus: Upgraded to focal on 2020-11-22 (142 days ago)
  UserGroups: adm cdrom davfs2 dialout dip kvm libvirt lpadmin plugdev roccat 
sambashare scanner sudo vboxusers
  _MarkForUpload: False
  dmi.bios.date: 04/20/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET61W (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HMS00T00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET61W(1.39):bd04/20/2020:svnLENOVO:pn20HMS00T00:pvrThinkPadX270:rvnLENOVO:rn20HMS00T00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HMS00T00
  dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware

[Ian Mackinnon]

I have a Dell/Broadcom 413c:8143 device and the patchram is apparently
still not being applied for me in Ubuntu 20.04, kernel
`5.4.0-70-generic`.

I see that the following struct was added in early 2017:

/* Dell Computer - Broadcom based  */
{ USB_VENDOR_AND_INTERFACE_INFO(0x413c, 0xff, 0x01, 0x01),
  .driver_info = BTUSB_BCM_PATCHRAM },

Commit diffs:

https://github.com/torvalds/linux/commit/fdfddc601713d4ed564b0bd25b29415bd622020a

https://kernel.ubuntu.com/git/ubuntu/ubuntu-
zesty.git/diff/drivers/bluetooth/btusb.c?h=Ubuntu-4.10.0-14.16=9f8d1a6f221b33b294032c15e4739a8a9076aaec

However, an earlier struct some ten items above appears to be blocking
the addition from taking effect:

{ USB_DEVICE(0x413c, 0x8197) },

With the stock Ubuntu module HSP/HFP does not work for me, but if I
remove the `USB_DEVICE` item, leaving the
`USB_VENDOR_AND_INTERFACE_INFO` item, and recompile, the patchram is
applied and HSP/HFP works.

Might it be necessary to remove the previous `USB_DEVICE` item from the
module source?

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

Title:
  Support for loading Broadcom bluetooth firmware

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux source package in Saucy:
  Fix Released
Status in linux source package in Trusty:
  Confirmed

Bug description:
  Broadcom bluetooth chips require a tool called patchram uploader [1]
  to load firmware. This applies to at least BCM20702 and BCM43142.
  Although some of the devices have an OTPROM that contains required
  firmware, but it is found that these devices would not have HFP/HSP
  support unless a upgraded firmware is loaded via patchram uploader.

  This tool requires hci device to do the firmware loading, but this may
  cause some race condition between patchram tool and bluetoothd or
  something that also works on hci interface.

  Also it needs some hooks to make firmware loads after bootup, s3,  s4,
  rfkill, and device hotplug events. Implement this loader in kernel
  module would make things more easier.

  [1] http://marc.info/?l=linux-bluetooth=132039175324993=2

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

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

[Kernel-packages] [Bug 1924314] Re: netvsc may cause CPU lockup

[Tim Gardner]

Test kernels at https://launchpad.net/~timg-tpi/+archive/ubuntu/netvsc-
lp1924314:

sudo add-apt-repository ppa:timg-tpi/netvsc-lp1924314
sudo apt-get update

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

Title:
  netvsc may cause CPU lockup

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  A soft lockup is happening to Azure cloud customers due to a bug in 
netvsc_poll.

  Ubuntu 4.15.0-1103 has CONFIG_NET_POLL_CONTROLLER=y in kernel config
  file, there is a bug in netvsc that may cause CPU lockup with
  POLL_CONTROLLER. This bug has been fixed by the following patch:

  commit 2a7f8c3b1d3feedee3aa319ac220cbde3725b5d5 ("hv_netvsc: remove
  ndo_poll_controller")

  This commit is in mainline as of 4.20-rc1.

  Microsoft would like to request this patch in 4.15 based Azure
  kernels.

  [Test Plan]
  Run high stress network traffic on an Azure instance.

  [Where problems could occur]
  There could be a decrease in performance or dropped packets due to NAPI not 
being able to keep up.

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

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

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

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

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

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

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

** Tags added: focal

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in crash source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in crash source package in Groovy:
  Confirmed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug has been addressed upstream and needed patches both in crash
  and kernel.

  Kernel patch :

  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

  Crash patch :

  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530

  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ

  [Test Case]

  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL

  [Where problems could occur]

  Kernel patch :

  The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
  and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
  Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.

  Crash patch :

  This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
  The regression potential is small and any problem would regard reading this 
variable.

  
  [Other]

  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.

  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

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

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

[Kernel-packages] [Bug 1923667] Re: Desktop shifted 1 pixel to the right when using full kms driver (Raspberry Pi 4B).

[Juerg Haefliger]

I'm not able to reproduce this. Maybe related?
https://github.com/raspberrypi/linux/issues/3667

** Bug watch added: github.com/raspberrypi/linux/issues #3667
   https://github.com/raspberrypi/linux/issues/3667

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

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

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

Title:
  Desktop shifted 1 pixel to the right when using full kms driver
  (Raspberry Pi 4B).

Status in linux-raspi package in Ubuntu:
  Triaged
Status in linux-raspi source package in Hirsute:
  Triaged

Bug description:
  - System: Raspberry Pi 4 Model B Rev 1.4
  - O.S. Ubuntu 21.04 Desktop Beta arm64 
  - Kernel: Linux fpgrpi 5.11.0-1005-raspi #5-Ubuntu SMP PREEMPT Fri Apr 9 
13:10:37 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
  - Package version: linux-raspi 5.11.0.1005.3
  - Desktop: GNOME 3.38.4 tk: GTK 3.24.25 wm: gnome-shell dm: GDM3 3.38.2.1 
Distro: Ubuntu 21.04 (Hirsute Hippo)
  - Display: server: X.Org 1.20.10 compositor: gnome-shell driver: loaded: 
modesetting unloaded: fbdev display ID: :1 
  - OpenGL: renderer: V3D 4.2 v: 2.1 Mesa 21.0.1 direct render: Yes 

  Problem summary:
  
  Most of times, after boot, the desktop is shifted 1 pixel to the right when 
attached to an HDMI monitor. It means that the most right vertical line is 
shown at the left of the screen.

  It only happens using the full kms drivers vc4-kms-v3d and vc4-kms-
  v3d-pi4, and not always but most of times. It doesn't happen using the
  fake kms driver vc4-fkms-v3d.

  I'm using X.Org, not Wayland. I've checked dmesg and journalctl
  messages and didn't found any related error. I also tried a fresh
  install of Ubuntu 21.04 Beta and got the same problem.

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

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

[Kernel-packages] [Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

Focal kernel :
Patch submitted 
https://lists.ubuntu.com/archives/kernel-team/2021-April/119287.html

Groovy kernel : 
Patch submitted 
https://lists.ubuntu.com/archives/kernel-team/2021-April/119288.html

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

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

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

** Also affects: crash (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Changed in: linux (Ubuntu Groovy)
   Importance: Undecided => Medium

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

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

** Changed in: crash (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: crash (Ubuntu Focal)
   Importance: Undecided => Medium

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in crash source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in crash source package in Groovy:
  Confirmed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug has been addressed upstream and needed patches both in crash
  and kernel.

  Kernel patch :

  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

  Crash patch :

  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530

  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ

  [Test Case]

  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL

  [Where problems could occur]

  Kernel patch :

  The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
  and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
  Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.

  Crash patch :

  This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
  The regression potential is small and any problem would regard reading this 
variable.

  
  [Other]

  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.

  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

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

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

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

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

Title:
  netvsc may cause CPU lockup

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  A soft lockup is happening to Azure cloud customers due to a bug in 
netvsc_poll.

  Ubuntu 4.15.0-1103 has CONFIG_NET_POLL_CONTROLLER=y in kernel config
  file, there is a bug in netvsc that may cause CPU lockup with
  POLL_CONTROLLER. This bug has been fixed by the following patch:

  commit 2a7f8c3b1d3feedee3aa319ac220cbde3725b5d5 ("hv_netvsc: remove
  ndo_poll_controller")

  This commit is in mainline as of 4.20-rc1.

  Microsoft would like to request this patch in 4.15 based Azure
  kernels.

  [Test Plan]
  Run high stress network traffic on an Azure instance.

  [Where problems could occur]
  There could be a decrease in performance or dropped packets due to NAPI not 
being able to keep up.

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

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

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

Title:
  accept returns duplicate endpoints under load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
  accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient 
= 232

  This indicates that the sockets with file descriptors 233 and 232 are
  duplicates.

  The issue has been reproduced on fully patched versions of Ubuntu
  20.04 and 18.04. Other versions have not been tested.

  This issue was originally observed in Java and was reported against the 
Spring Framework:
  https://github.com/spring-projects/spring-framework/issues/26434

  Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
  https://bugs.openjdk.java.net/browse/JDK-8263243

  Further research from the JDK team determined that the issue was at
  the OS level. Hence this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 12:52:53 2021
  HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
  InstallationDate: Installed on 2017-02-02 (1532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-71-generic N/A
   linux-backports-modules-5.4.0-71-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Also affects: crash-installer
   Importance: Undecided
   Status: New

** No longer affects: crash-installer

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New

Bug description:
  [Impact]

  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug has been addressed upstream and needed patches both in crash
  and kernel.

  Kernel patch :

  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

  Crash patch :

  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530

  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ

  [Test Case]

  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL

  [Where problems could occur]

  Kernel patch :

  The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
  and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
  Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.

  Crash patch :

  This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
  The regression potential is small and any problem would regard reading this 
variable.

  
  [Other]

  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.

  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

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

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

[Kernel-packages] [Bug 1924314] [NEW] netvsc may cause CPU lockup

[Tim Gardner]

Public bug reported:

[SRU Justification]

[Impact]
A soft lockup is happening to Azure cloud customers due to a bug in netvsc_poll.

Ubuntu 4.15.0-1103 has CONFIG_NET_POLL_CONTROLLER=y in kernel config
file, there is a bug in netvsc that may cause CPU lockup with
POLL_CONTROLLER. This bug has been fixed by the following patch:

commit 2a7f8c3b1d3feedee3aa319ac220cbde3725b5d5 ("hv_netvsc: remove
ndo_poll_controller")

This commit is in mainline as of 4.20-rc1.

Microsoft would like to request this patch in 4.15 based Azure kernels.

[Test Plan]
Run high stress network traffic on an Azure instance.

[Where problems could occur]
There could be a decrease in performance or dropped packets due to NAPI not 
being able to keep up.

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress


** Tags: bot-stop-nagging

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Tags added: bot-stop-nagging

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

Title:
  netvsc may cause CPU lockup

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  A soft lockup is happening to Azure cloud customers due to a bug in 
netvsc_poll.

  Ubuntu 4.15.0-1103 has CONFIG_NET_POLL_CONTROLLER=y in kernel config
  file, there is a bug in netvsc that may cause CPU lockup with
  POLL_CONTROLLER. This bug has been fixed by the following patch:

  commit 2a7f8c3b1d3feedee3aa319ac220cbde3725b5d5 ("hv_netvsc: remove
  ndo_poll_controller")

  This commit is in mainline as of 4.20-rc1.

  Microsoft would like to request this patch in 4.15 based Azure
  kernels.

  [Test Plan]
  Run high stress network traffic on an Azure instance.

  [Where problems could occur]
  There could be a decrease in performance or dropped packets due to NAPI not 
being able to keep up.

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

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

[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

[Dimitri John Ledkov]

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

** Tags added: rls-hh-incoming

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

Title:
  unexpected error pop-up after 'apt install nvidia-driver-455'

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  New

Bug description:
  Ubuntu info:

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52)
  Release 20.04

  Full reproduce step

  1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first 
place, without all i386 pkg installed.
  2. run update-manager to do upgrade.
  3. it will show error after download deb and didn't upgrade anything.

  Per test with the command to do the upgrade, it will have an extra
  error message, but it will just upgrade and install recommended i386
  debs.

  The error msgs are:

  E: Could not configure 'libc6:i386'.
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  Short way to get the error:
  # apt-get install libgcc-s1:i386 --dry-run
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 
gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16
libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 
libunistring2:i386
  Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
  The following NEW packages will be installed:
gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 
libunistring2:i386
  The following packages will be upgraded:
libc6
  1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded.
  Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates 
[amd64])
  Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) []
  Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) []
  Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386])
  Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386])
  Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  E: Could not configure 'libc6:i386'. 
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  For now, we think the above Error is the root cause of update-manager
  failure.

  ---

  This happens as upgrade package nvidia-driver-455 from
  455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1.

  for more detail, please check the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions

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

[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  unexpected error pop-up after 'apt install nvidia-driver-455'

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  New

Bug description:
  Ubuntu info:

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52)
  Release 20.04

  Full reproduce step

  1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first 
place, without all i386 pkg installed.
  2. run update-manager to do upgrade.
  3. it will show error after download deb and didn't upgrade anything.

  Per test with the command to do the upgrade, it will have an extra
  error message, but it will just upgrade and install recommended i386
  debs.

  The error msgs are:

  E: Could not configure 'libc6:i386'.
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  Short way to get the error:
  # apt-get install libgcc-s1:i386 --dry-run
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 
gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16
libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 
libunistring2:i386
  Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
  The following NEW packages will be installed:
gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 
libunistring2:i386
  The following packages will be upgraded:
libc6
  1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded.
  Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates 
[amd64])
  Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) []
  Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) []
  Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386])
  Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386])
  Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  E: Could not configure 'libc6:i386'. 
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  For now, we think the above Error is the root cause of update-manager
  failure.

  ---

  This happens as upgrade package nvidia-driver-455 from
  455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1.

  for more detail, please check the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions

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

[Kernel-packages] [Bug 1923846] Re: Kernel panic

[Seth Forshee]

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

** This bug has been marked a duplicate of bug 1922403
   hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI

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

Title:
  Kernel panic

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I use Hyper-V and created VM with "Generation 2", I cannot boot Ubuntu
  Hirsute Hippo Live CD, it gives me kernel panic, I tried it when there
  were included 5.11.0-13 and 5.11.0-14 kernels - same result, when
  there was 5.11.0-11 and older it was fine.

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

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

[Kernel-packages] [Bug 1924298] [NEW] accept returns duplicate endpoints under load

[Mark Thomas]

Public bug reported:

When accepting client connections under load, duplicate endpoints may be
returned. These endpoints will have different (usually sequential) file
descriptors but will refer to the same connection (same server IP, same
server port, same client IP, same client port). Both copies of the
endpoint appear to be functional.

Reproduction requires:
- compilation of the attached server.c program
- wrk (https://github.com/wg/wrk) to generate load

The steps to reproduce are:
- run 'server' application in one console window
- run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency --timeout 
1s http://localhost:/post; done' in a second console window
- run the same command in a third window to generate concurrent load

You may need to run additional instance of the wrk command in multiple
windows to trigger the issue.

When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient = 
232

This indicates that the sockets with file descriptors 233 and 232 are
duplicates.

The issue has been reproduced on fully patched versions of Ubuntu 20.04
and 18.04. Other versions have not been tested.

This issue was originally observed in Java and was reported against the Spring 
Framework:
https://github.com/spring-projects/spring-framework/issues/26434

Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
https://bugs.openjdk.java.net/browse/JDK-8263243

Further research from the JDK team determined that the issue was at the
OS level. Hence this report.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-71-generic 5.4.0-71.79
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 12:52:53 2021
HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
InstallationDate: Installed on 2017-02-02 (1532 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
 lono wireless extensions.
 
 docker0   no wireless extensions.
 
 eno1  no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. Default string
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/ubuntu--vg-root ro text
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-71-generic N/A
 linux-backports-modules-5.4.0-71-generic  N/A
 linux-firmware1.187.10
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
dmi.bios.date: 06/13/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F22
dmi.board.asset.tag: Default string
dmi.board.name: X99-SLI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug focal

** Attachment added: "Simple listening server to demonstrate issue"
   https://bugs.launchpad.net/bugs/1924298/+attachment/5488298/+files/server.c

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

Title:
  accept returns duplicate endpoints under load

Status in linux package in Ubuntu:
  New

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server 

[Kernel-packages] [Bug 1909814] Re: Keyboard not working

[Rubén Ruiz]

Same problem, Medion S15449 keyboard not works in Ubuntu 20.10 or Debian
last distro.

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

Title:
  Keyboard not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  Brand new laptop (Medion), keyboard is only working with the grub menu.
  Mouse is now working since 20.10 have been installed.
  Only the luminosity key are working on the keyboard.
  External usb keyboard works fine.
  I tried to install with usb keyboard disconnected but doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  did4364 F pulseaudio
   /dev/snd/pcmC0D0p:   did4364 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  1 16:24:12 2021
  InstallationDate: Installed on 2021-01-01 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: MEDION S15450
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2020
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 209
  dmi.board.asset.tag: Default string
  dmi.board.name: M15T
  dmi.board.vendor: MEDION
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring:
  dmi.product.family: Akoya
  dmi.product.name: S15450
  dmi.product.sku: ML-230008 30030452
  dmi.product.version: Default string
  dmi.sys.vendor: MEDION

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

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

[Kernel-packages] [Bug 1922293] Re: Snaps appear broken on 21.04 Beta with ZFS

[Paweł Stołowski]

@Luna what was the fix, can you link to the respective change? I'm still
seeing the problem with up-to-date 21.04 (and there were no updates
reported for zfs-linux; was it actually released)?

The tentative fix for snapd hasn't been commited yet in snapd; if the
problem was fixed elsewhere then we won't need snapd fix; therefore I'm
marking this back to "in progress" in snapd and it should be set
"invalid" if not needed in snapd.

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

Title:
  Snaps appear broken on 21.04 Beta with ZFS

Status in snapd package in Ubuntu:
  In Progress
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  I've attempted to use two different userland snaps (qownnotes and
  keepassxc) neither function. When attempting to launch I get the
  following error:

  ```
  chalbersma@abdos:~$ qownnotes
  cannot perform operation: mount --rbind /dev /tmp/snap.rootfs_t3kehe//dev: No 
such file or directory
  ```

  Additionally the snaps installed "by default" have a note of "broken"
  next to them :

  ```
  chalbersma@abdos:~$ sudo snap list
  Name   Version  RevTracking Publisher   Notes
  core18  1997   latest/stablecanonical✓  broken
  gnome-3-34-1804 66 latest/stable/…  canonical✓  broken
  gtk-common-themes   1514   latest/stable/…  canonical✓  broken
  qownnotes  21.3.9   8183   latest/stablepbek-
  snap-store  518latest/stable/…  canonical✓  broken
  snapd   11402  latest/stablecanonical✓  broken
  ```

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

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

[Kernel-packages] [Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Description changed:

  [Impact]
  
  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:
  
  crash: cannot determine VA_BITS_ACTUAL
  
  This bug has been addressed upstream and needed patches both in crash
  and kernel.
  
  Kernel patch :
  
  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
- arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo
- 
+ arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo
  
  Crash patch :
  
  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530
  
- arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ
- 
+ arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ
  
  [Test Case]
  
  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL
  
+ [Where problems could occur]
  
- [Where problems could occur]
+ Kernel patch :
+ 
+ The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
+ and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
+ Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.
+ 
+ Crash patch :
+ 
+ This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
+ The regression potential is small and any problem would regard reading this 
variable.
+ 
  
  [Other]
  
  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.
  
  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New

Bug description:
  [Impact]

  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug has been addressed upstream and needed patches both in crash
  and kernel.

  Kernel patch :

  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

  Crash patch :

  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530

  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ

  [Test Case]

  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL

  [Where problems could occur]

  Kernel patch :

  The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
  and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
  Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.

  Crash patch :

  This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
  The regression potential is small and any problem would regard reading this 
variable.

  
  [Other]

  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.

  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

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

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

[Kernel-packages] [Bug 1922293] Re: Snaps appear broken on 21.04 Beta with ZFS

[Paweł Stołowski]

** Changed in: snapd (Ubuntu)
   Status: Fix Released => In Progress

** Changed in: snapd (Ubuntu)
 Assignee: (unassigned) => Paweł Stołowski (stolowski)

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

Title:
  Snaps appear broken on 21.04 Beta with ZFS

Status in snapd package in Ubuntu:
  In Progress
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  I've attempted to use two different userland snaps (qownnotes and
  keepassxc) neither function. When attempting to launch I get the
  following error:

  ```
  chalbersma@abdos:~$ qownnotes
  cannot perform operation: mount --rbind /dev /tmp/snap.rootfs_t3kehe//dev: No 
such file or directory
  ```

  Additionally the snaps installed "by default" have a note of "broken"
  next to them :

  ```
  chalbersma@abdos:~$ sudo snap list
  Name   Version  RevTracking Publisher   Notes
  core18  1997   latest/stablecanonical✓  broken
  gnome-3-34-1804 66 latest/stable/…  canonical✓  broken
  gtk-common-themes   1514   latest/stable/…  canonical✓  broken
  qownnotes  21.3.9   8183   latest/stablepbek-
  snap-store  518latest/stable/…  canonical✓  broken
  snapd   11402  latest/stablecanonical✓  broken
  ```

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

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

[Kernel-packages] [Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Description changed:

+ [Impact]
+ 
  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:
  
  crash: cannot determine VA_BITS_ACTUAL
  
- This bug/change in crash provides a workaround for 5.4+
- https://github.com/crash-utility/crash/issues/52 kernels.
+ This bug has been addressed upstream and needed patches both in crash
+ and kernel.
+ 
+ Kernel patch :
+ 
+ commit bbdbc11804ff0b4130e7550113b452e96a74d16e
+ Author: Bhupesh Sharma 
+ Date:   Thu May 14 00:22:37 2020 +0530
+ arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo
+ 
+ 
+ Crash patch :
+ 
+ commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
+ Author: Bhupesh Sharma 
+ Date:   Tue Jul 14 01:14:49 2020 +0530
+ 
+ arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ
+ 
+ 
+ [Test Case]
+ 
+ On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
+ It will fail with :
+ crash: cannot determine VA_BITS_ACTUAL
+ 
+ 
+ [Where problems could occur]
+ 
+ [Other]
+ 
+ Workaround :
+ This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.
  
  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New

Bug description:
  [Impact]

  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug has been addressed upstream and needed patches both in crash
  and kernel.

  Kernel patch :

  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

  
  Crash patch :

  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530

  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ

  
  [Test Case]

  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL

  
  [Where problems could occur]

  [Other]

  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.

  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

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

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

[Kernel-packages] [Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Changed in: crash (Ubuntu)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: crash (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New

Bug description:
  [Impact]

  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug has been addressed upstream and needed patches both in crash
  and kernel.

  Kernel patch :

  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

  
  Crash patch :

  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530

  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ

  
  [Test Case]

  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL

  
  [Where problems could occur]

  [Other]

  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.

  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

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

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

[Kernel-packages] [Bug 1856010] Re: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite

[Po-Hsu Lin]

On KVM node zeppo, these tests will take:

xfrm_policy.sh - 2m15s
pmtu.sh - 2m36s
udpgso_bench.sh - 58s

The reason why it will fail when running the whole suite is that, the
default timeout in kselftest framework for each tests is 45 seconds, so
they're terminated by the default timeout.

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

Title:
  xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in
  ubuntu_kernel_selftests will fail if running the whole suite

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-aws package in Ubuntu:
  New

Bug description:
  These 3 tests will fail with timeout when running the whole "net" test in 
ubuntu_kernel_selftests:
* not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT
* not ok 16 selftests: net: pmtu.sh # TIMEOUT
* not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT

  However they will pass if you run them manually:

  
  So there must be some test in net that will cause this.

  From the test result it looks like the test was executed in the following 
sequence:
   ok 1 selftests: net: reuseport_bpf
   ok 2 selftests: net: reuseport_bpf_cpu
   ok 3 selftests: net: reuseport_bpf_numa
   ok 4 selftests: net: reuseport_dualstack
   # Successok 5 selftests: net: reuseaddr_conflict
   ok 6 selftests: net: tls
   ok 7 selftests: net: run_netsocktests
   ok 8 selftests: net: run_afpackettests
   ok 9 selftests: net: test_bpf.sh
   ok 10 selftests: net: netdevice.sh
   ok 11 selftests: net: rtnetlink.sh
   not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT
   not ok 13 selftests: net: test_blackhole_dev.sh # exit=1 
   ok 14 selftests: net: fib_tests.sh
   ok 15 selftests: net: fib-onlink-tests.sh
   not ok 16 selftests: net: pmtu.sh # TIMEOUT
   ok 17 selftests: net: udpgso.sh
   not ok 18 selftests: net: ip_defrag.sh # exit=255 
   not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT
   ok 20 selftests: net: fib_rule_tests.sh
   not ok 21 selftests: net: msg_zerocopy.sh # exit=1
   ok 22 selftests: net: psock_snd.sh
   ok 23 selftests: net: udpgro_bench.sh
   ok 24 selftests: net: udpgro.sh
   ok 25 selftests: net: test_vxlan_under_vrf.sh
   ok 26 selftests: net: reuseport_addr_any.sh
   ok 27 selftests: net: test_vxlan_fdb_changelink.sh
   ok 28 selftests: net: so_txtime.sh
   ok 29 selftests: net: ipv6_flowlabel.sh
   ok 30 selftests: net: tcp_fastopen_backup_key.sh

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-1009-aws 5.3.0-1009.10
  ProcVersionSignature: User Name 5.3.0-1009.10-aws 5.3.13
  Uname: Linux 5.3.0-1009-aws aarch64
  ApportVersion: 2.20.11-0ubuntu8.3
  Architecture: arm64
  Date: Wed Dec 11 06:42:39 2019
  Ec2AMI: ami-047cec24582f6ae0d
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2c
  Ec2InstanceType: a1.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1922242] Re: openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

[Launchpad Bug Tracker]

This bug was fixed in the package openafs - 1.6.15-1ubuntu1.1

---
openafs (1.6.15-1ubuntu1.1) xenial; urgency=medium

  * debian/patches/1002-Linux-4.9-inode_change_ok-becomes-setattr_prepare.patch
   - Linux 4.9: inode_change_ok() becomes setattr_prepare()
 (LP: #1922242)

 -- Kleber Sacilotto de Souza   Thu, 01 Apr
2021 18:20:36 +0200

** Changed in: openafs (Ubuntu Xenial)
   Status: Fix Committed => 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/1922242

Title:
  openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in openafs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in openafs source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  autopkgtest caught a build failure with openafs-modules-dkms with the 
xenial/linux kernel currently in -proposed (4.4.0-207.239).

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz

  Build error:

    CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
   code = inode_change_ok(inode, );
  ^
  cc1: some warnings being treated as errors

  This was caused by commit "fs: Give dentry to inode_change_ok()
  instead of inode" applied to xenial/linux as part of the fixes for
  CVE-2015-1350, which renamed inode_change_ok() to setattr_prepare().

  [Fix]
  The proposed fix is to cherry-pick commit 
8aeb711eeaa5ddac5a74c354091e2d4f7ac0cd63 "Linux 4.9: inode_change_ok() becomes 
setattr_prepare()" from openafs repository (git://git.openafs.org/openafs.git).

  [Test]
  Install openafs-modules-dkms on a xenial system running an older kernel 
without the interface change (<4.4.0-207) and with a newer kernel with the 
interface change (>=4.4.0-207). The openafs module should be built and loaded 
with all kernels.

  [Where problems could occur]
  The fix is based on the detection made during build time of the function 
available on the kernel headers. If the detection doesn't work correctly the 
build would fail.

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

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

[Kernel-packages] [Bug 1922242] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for openafs has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in openafs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in openafs source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  autopkgtest caught a build failure with openafs-modules-dkms with the 
xenial/linux kernel currently in -proposed (4.4.0-207.239).

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz

  Build error:

    CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
   code = inode_change_ok(inode, );
  ^
  cc1: some warnings being treated as errors

  This was caused by commit "fs: Give dentry to inode_change_ok()
  instead of inode" applied to xenial/linux as part of the fixes for
  CVE-2015-1350, which renamed inode_change_ok() to setattr_prepare().

  [Fix]
  The proposed fix is to cherry-pick commit 
8aeb711eeaa5ddac5a74c354091e2d4f7ac0cd63 "Linux 4.9: inode_change_ok() becomes 
setattr_prepare()" from openafs repository (git://git.openafs.org/openafs.git).

  [Test]
  Install openafs-modules-dkms on a xenial system running an older kernel 
without the interface change (<4.4.0-207) and with a newer kernel with the 
interface change (>=4.4.0-207). The openafs module should be built and loaded 
with all kernels.

  [Where problems could occur]
  The fix is based on the detection made during build time of the function 
available on the kernel headers. If the detection doesn't work correctly the 
build would fail.

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

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

[Kernel-packages] [Bug 1924207] Re: [SRU][F:OEM-5.10/G/H] add realtek 8852 bluetooth support

[AaronMa]

** Summary changed:

- [SRU][F/G/H] add realtek 8852 bluetooth support
+ [SRU][F:OEM-5.10/G/H] add realtek 8852 bluetooth support

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

Title:
  [SRU][F:OEM-5.10/G/H] add realtek 8852 bluetooth support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux-oem-5.10 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:
  SRU justification:

  [Impact]
  Realtek 8852A bluetooth can not work because of no support in 5.10- kernel.

  [Fix]
  Add realtek 8852 bluetooth ID in driver.
  Chip firmware is in another SRU.

  [Test]
  Verified on hardware with bluetooth headset and file transfer, all good.

  [Where problems could occur]
  The bluetooth chip 8852A may fail to work.
  It should be low risk for adding ID for specfic hardware chip.
  Unstable kernel already got it, only for F/G/H.

  Backport for commit 0d484db60f ("Bluetooth: btusb: btrtl: Add support for 
RTL8852A")
  Because commit 6f9ff24645f ("Bluetooth: btrtl: Refine the ic_id_table for 
clearer and more regular") changes the macro of IC_INFO, use the old way to add 
the IDs for 8852A, no function changes.

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

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

[Kernel-packages] [Bug 1917203] Re: [PATCH 2/2] iommu/amd: Remove performance counter pre-initialization test

[Suravee Suthikulpanit]

David,

On 4/14/2021 10:33 PM, David Coe wrote:
> Hi Suravee!
> 
> I've re-run your revert+update patch on Ubuntu's latest kernel 5.11.0-14 
> partly to check my mailer's 'mangling' hadn't also reached the code!
> 
> There are 3 sets of results in the attachment, all for the Ryzen 2400G. The 
> as-distributed kernel already incorporates your IOMMU RFCv3 patch.
> 
> A. As-distributed kernel (cold boot)
>     >5 retries, so no IOMMU read/write capability, no amd_iommu events.
> 
> B. As-distributed kernel (warm boot)
>     <5 retries, amd_iommu running stats show large numbers as before.
> 
> C. Revert+Update kernel
>     amd_iommu events listed and also show large hit/miss numbers.
> 
> In due course, I'll load the new (revert+update) kernel on the 4700G but 
> won't overload your mail-box unless something unusual turns up.
> 
> Best regards,
> 

For the Ryzen 2400G, could you please try with:
- 1 event at a time
- Not more than 8 events (On your system, it has 2 banks x 4 counters/bank.
I am trying to see if this issue might be related to the counters multiplexing).

Thanks,
Suravee

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

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

Status in linux package in Ubuntu:
  In Progress

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

  The problem is currently under discussion at kernel level
  .

  One solution proposed by Suravee Suthikulpanit

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

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

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

  Best regards and all respect!

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

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

[Kernel-packages] [Bug 1919252] Re: zfs-dkms on Focal still allows building on Linux kernel version 5.10+

[Colin Ian King]

Thanks for testing.

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

Title:
  zfs-dkms on Focal still allows building on Linux kernel version 5.10+

Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Focal:
  Fix Committed

Bug description:
  == SRU update, zfs-dkms, Focal ==

  [Impact]

  Due to a mistake in the BUILD_EXCLUSIVE_KERNEL regex in dkms.conf,
  dkms will still consider zfs-dkms to be buildable on kernel version
  5.10+. This can happen if one installs a mainline kernel from the
  mainline PPA for one reason or another.

  Fixing this will stop users from installing incompatible newer
  versions of the kernel and hence stop dkms build failures on known
  incompatible kernel versions.  The fix is also trivial.

  [The Fix]

  Correctly escape . in regex so that the final sed'd string gets
  modified to produce the correct regex pattern, as follows:

  sed -ie '/^PACKAGE_VERSION/a 
BUILD_EXCLUSIVE_KERNEL="^(4\\.[0-9]+|5\\.[01234])\\."' \
  '$(CURDIR)/scripts/zfs-dkms.dkms'

  
  [Test Plan]

  Without the fix, install kernels > than versions 5.4. ZFS dkms will
  attempt to be built against these and fail with broken builds.
  Installing earlier kernels such as 4.20, 5.0, 5.4 should succeed.

  With the fix, installing kernels > 5.4 will skip the ZFS dkms build
  phase and report a meaningful error:

  Error!  The /var/lib/dkms/zfs/0.8.3/5.5.19-050519-generic/x86_64/dkms.conf 
for module zfs includes a BUILD_EXCLUSIVE directive which
  does not match this kernel/arch.  This indicates that it should not be built

  Test kernels for the test from https://kernel.ubuntu.com/~kernel-
  ppa/mainline/?C=N;O=D can be used to test this out.

  [Where problems could occur]

  The change is to a regex pattern match. If this is incorrect then
  kernels such a 5.4 will not be allowed to build the dkms zfs driver.
  This will clearly show up as a ZFS dkms build denied failure with an
  error such as:

  Error!  The /var/lib/dkms/zfs/0.8.3/5.5.19-050519-generic/x86_64/dkms.conf 
for module zfs includes a BUILD_EXCLUSIVE directive which
  does not match this kernel/arch.  This indicates that it should not be built

  This fix is relatively low-risk, it fixes am issue with an earlier fix
  to the regex which wasn't quite working for kernels > 5.4 and yet
  didn't cause any major issues blocking legitimate users from using
  known working 5.4 kernels with zfs dkms.

  ---

  Due to a mistake in the BUILD_EXCLUSIVE_KERNEL regex in dkms.conf,
  dkms will still consider zfs-dkms to be buildable on kernel version
  5.10+. This can happen if one installs a mainline kernel from the
  mainline PPA for one reason or another [1].

  The following patch to dkms.conf should fix the issue:

  --- ./dkms.conf.orig  2021-03-16 04:15:55.077568974 +0700
  +++ /usr/src/zfs-0.8.3/dkms.conf  2021-03-16 04:17:16.598219797 +0700
  @@ -1,6 +1,6 @@
   PACKAGE_NAME="zfs"
   PACKAGE_VERSION="0.8.3"
  -BUILD_EXCLUSIVE_KERNEL="^(4.[0-9]+|5.[01234])."
  +BUILD_EXCLUSIVE_KERNEL='^(4.[0-9]+|5.[01234])\.'
   PACKAGE_CONFIG="/etc/sysconfig/zfs"
   PRE_BUILD="configure
     --prefix=/usr

  Although it's not convenient for me at the moment to create a debdiff.

  Related: LP: #1902701

  [1] For me it's to get a complete fix for LP: #1887190, as Focal's HWE
  kernel doesn't seem to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: zfs-dkms 0.8.3-1ubuntu12.6
  Uname: Linux 5.11.6-051106-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Mar 16 04:26:08 2021
  InstallationDate: Installed on 2021-03-15 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=th_TH.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1924238] Re: Fix no picture from HDMI when it's plugged after boot

[Kai-Heng Feng]

** Tags added: oem-priority originate-from-1908030 stella

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

Title:
  Fix no picture from HDMI when it's plugged after boot

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

Bug description:
  [Impact]
  On Intel CML desktop, there's no HDMI output when the cable is not
  connected pre-boot.

  [Fix]
  Properly handle lane polarity so the driver can write different values
  to the register to enable the port.

  [Test]
  1. Boot with DP display.
  2. Connect HDMI under GNOME desktop.
  3. No picture on HDMI monitor.
  With the fix applied, the issue is resolved.

  [Where problems could occur]
  If the BIOS VBT table is not correct, which did happen in the pase, this
  fix may break those ports.

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

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

[Kernel-packages] [Bug 1924238] [NEW] Fix no picture from HDMI when it's plugged after boot

[Kai-Heng Feng]

Public bug reported:

[Impact]
On Intel CML desktop, there's no HDMI output when the cable is not
connected pre-boot.

[Fix]
Properly handle lane polarity so the driver can write different values
to the register to enable the port.

[Test]
1. Boot with DP display.
2. Connect HDMI under GNOME desktop.
3. No picture on HDMI monitor.
With the fix applied, the issue is resolved.

[Where problems could occur]
If the BIOS VBT table is not correct, which did happen in the pase, this
fix may break those ports.

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

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

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

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: Won't Fix

** Affects: linux-oem-5.10 (Ubuntu Focal)
 Importance: Medium
 Status: Confirmed

** Affects: linux (Ubuntu Hirsute)
 Importance: Medium
 Status: Confirmed

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


** Tags: oem-priority originate-from-1908030 stella

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux-oem-5.10 (Ubuntu Hirsute)
   Status: New => Invalid

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

Title:
  Fix no picture from HDMI when it's plugged after boot

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

Bug description:
  [Impact]
  On Intel CML desktop, there's no HDMI output when the cable is not
  connected pre-boot.

  [Fix]
  Properly handle lane polarity so the driver can write different values
  to the register to enable the port.

  [Test]
  1. Boot with DP display.
  2. Connect HDMI under GNOME desktop.
  3. No picture on HDMI monitor.
  With the fix applied, the issue is resolved.

  [Where problems could occur]
  If the BIOS VBT table is not correct, which did happen in the pase, this
  fix may break those ports.

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

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

[Kernel-packages] [Bug 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]

[T]

Hi,

i also have the X1 and i had the same problem today.

When my X1 didnt have an external monitor attached, everything was fine.
When an external monitor in, everything went black (but mouse cursor
visible). I had PhpStorm open.. so i closed it and tried again and it
worked. Afterwards i could open PhpStorm again and everything was good.

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

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

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 

[Kernel-packages] [Bug 1921355] Re: cgroups related kernel panics

[Juerg Haefliger]

Can you collect and upload logs per the previous comment? I've googled
around some but nothing jumped out. This will be difficult without a
reproducer.

Have you tried the latest HWE kernel 5.4.0-71.79~18.04.1?

Is there any chance you can enable kdump?

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

Title:
  cgroups related kernel panics

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

Bug description:
  Hi!

  Recently (throughout the last 6 months) we've upgraded our hypervisor
  compute hosts from ubuntu bionic kernel 4.15.* to ubuntu bionic hwe
  kernel 5.4.

  This month we noticed that several nodes failed due to bugs in cgroups.
  Trace was different almost every time, but it all revolves around cgroups - 
either null pointer failures, or panic caught by BUG_ON() macro. Looked like 
some cgroup didn't exist anymore but somebody tried to access it, thus causing 
kernel panic.
  Please find the logs attached.

  3 of 4 cases happened after a VM shutdown. We tried to spawn lots of VMs, 
load them, shut them down, but didn't manage to reproduce the behavior.
  Actually, every case is sort of different - patch kernel versions (5.4.0-42 
to 5.4.0-66), uptime vary (from 1 day to ~half a year). There are also lots of 
hosts with several months of uptime, no issue with them. Also, on 4.15 we've 
never seen this behavior, at all.
  That's quite disturbing, as I don't want dozens of VMs crash (due to host 
outage) at random times for some vague reason...
  I didn't manage to find any related bugs on the bug tracker, thus creating 
this one.

  I wonder if anybody in the community came across something like that.
  Could somebody give an advice how to debug further, or where else to report / 
look for a similar the case?

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

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

[Kernel-packages] [Bug 1919093] Re: [ThinkPad P1 Gen 3 w/ Intel + Nvidia Quadro T2000] Desktop does not load after login - purple screen with mouse

[Daniel van Vugt]

I've seen a couple of people report issues with manual NVIDIA driver
installations recently but so long as you installed the NVIDIA driver
through the 'Additional Drivers' app then it is expected to work.

I think I ran out of ideas for this bug a month ago but it does seem to
be assigned to the wrong project so I shall change that.

** Package changed: xorg-server (Ubuntu) => nvidia-graphics-drivers-460
(Ubuntu)

** Also affects: linux-hwe-5.8 (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/1919093

Title:
  [ThinkPad P1 Gen 3 w/ Intel + Nvidia Quadro T2000] Desktop does not
  load after login - purple screen with mouse

Status in linux-hwe-5.8 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New

Bug description:
  When logging in, the screen goes purple and blank, but I can still
  move the mouse. Keyboard shortcuts such as Alt+F2 or Ctrl+Alt+T have
  no effect. I can use Ctrl+Alt+F[1345...] to switch to a shell or go
  back to the login screen, but Ctrl+Alt+F2 puts me back in the blank
  state. When turning off the computer from the login screen, I get a
  warning that my user is logged in.

  The most similar previous bug report I've been able to find is
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137. However,
  my problem occurs regardless of whether I fail the first login attempt
  or not, or whether I enter my password or scan my fingerprint.

  I have replicated the problem booting with two kernel versions: Linux
  5.8.0-44 and Linux 5.8.0-43

  I have been using the computer since November 2020, and this problem
  occurred for the first time when I rebooted it this weekend (Sat
  2021-03-13). I have previously had trouble getting getting external
  monitors to work, but even that has worked fine for the past few
  months.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Mar 14 21:19:17 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo Device [17aa:22c0]
   NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev 
a1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo TU117GLM [Quadro T2000 Mobile / Max-Q] [17aa:22c0]
  MachineType: LENOVO 20TH000VMX
  ProcEnviron:
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   TERM=linux
   PATH=(custom, no user)
   LANG=nb_NO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=9da324cb-cdc4-42f8-abdd-b764e455a1f7 ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2020
  dmi.bios.release: 1.12
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2VET27W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TH000VMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET27W(1.12):bd12/21/2020:br1.12:efr1.7:svnLENOVO:pn20TH000VMX:pvrThinkPadP1Gen3:rvnLENOVO:rn20TH000VMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 3
  dmi.product.name: 20TH000VMX
  dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3
  dmi.product.version: ThinkPad P1 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1924217] Re: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()]

[Daniel van Vugt]

Prepared a fix for future update 5.56-0ubuntu5 (approximately)

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

Title:
  bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in
  get_report_cb() from notify_handler() from notify_handler() from
  queue_foreach() from queue_foreach()]

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8

  ---

  bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this 
in dmesg:
  [   58.257605] input: TrackPoint Keyboard II Keyboard as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26
  [   58.258542] input: TrackPoint Keyboard II Mouse as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27
  [   58.259561] input: TrackPoint Keyboard II Consumer Control as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input
  /input28
  [   58.259661] input: TrackPoint Keyboard II System Control as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i
  nput29
  [   58.260151] input: TrackPoint Keyboard II as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31
  [   58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID 
v0.47 Keyboard [TrackPoint Keyboard II]
  on 10:4a:7d:01:8d:7f
  [   58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 
7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000]
  [   58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 
11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 
24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07

  This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of 
today). It did not happen in 20.10.
  When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluez 5.56-0ubuntu3
  Uname: Linux 5.11.0-051100-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Apr 14 21:03:29 2021
  InstallationDate: Installed on 2021-02-26 (47 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20AW0006US
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic 
root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago)
  dmi.bios.date: 01/27/2015
  dmi.bios.release: 2.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET77WW (2.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AW0006US
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AW0006US
  dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 10:4A:7D:01:8D:7F  ACL MTU: 1021:5  SCO MTU: 96:5
    UP RUNNING
    RX bytes:267050 acl:16636 sco:0 events:966 errors:0
    TX bytes:28087 acl:371 sco:0 commands:388 errors:0

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

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

[Kernel-packages] [Bug 1919093] [NEW] [ThinkPad P1 Gen 3 w/ Intel + Nvidia Quadro T2000] Desktop does not load after login - purple screen with mouse

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When logging in, the screen goes purple and blank, but I can still move
the mouse. Keyboard shortcuts such as Alt+F2 or Ctrl+Alt+T have no
effect. I can use Ctrl+Alt+F[1345...] to switch to a shell or go back to
the login screen, but Ctrl+Alt+F2 puts me back in the blank state. When
turning off the computer from the login screen, I get a warning that my
user is logged in.

The most similar previous bug report I've been able to find is
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137. However, my
problem occurs regardless of whether I fail the first login attempt or
not, or whether I enter my password or scan my fingerprint.

I have replicated the problem booting with two kernel versions: Linux
5.8.0-44 and Linux 5.8.0-43

I have been using the computer since November 2020, and this problem
occurred for the first time when I rebooted it this weekend (Sat
2021-03-13). I have previously had trouble getting getting external
monitors to work, but even that has worked fine for the past few months.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Mar 14 21:19:17 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo Device [17aa:22c0]
 NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T2000 Mobile / Max-Q] [17aa:22c0]
MachineType: LENOVO 20TH000VMX
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 TERM=linux
 PATH=(custom, no user)
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=9da324cb-cdc4-42f8-abdd-b764e455a1f7 ro recovery nomodeset 
dis_ucode_ldr
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2020
dmi.bios.release: 1.12
dmi.bios.vendor: LENOVO
dmi.bios.version: N2VET27W (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TH000VMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.7
dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET27W(1.12):bd12/21/2020:br1.12:efr1.7:svnLENOVO:pn20TH000VMX:pvrThinkPadP1Gen3:rvnLENOVO:rn20TH000VMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P1 Gen 3
dmi.product.name: 20TH000VMX
dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3
dmi.product.version: ThinkPad P1 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug false-gpu-hang focal freeze regression-update ubuntu
-- 
[ThinkPad P1 Gen 3 w/ Intel + Nvidia Quadro T2000] Desktop does not load after 
login - purple screen with mouse
https://bugs.launchpad.net/bugs/1919093
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-460 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 1916468] Re: powerpc/eeh-basic.sh in kselftest make P8 node stopped working

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
   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/1916468

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

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

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 1924217] Re: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()]

[Daniel van Vugt]

Private is the default state for crashes because those bugs could
potentially contain personal information in crash data.

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

Title:
  bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in
  get_report_cb() from notify_handler() from notify_handler() from
  queue_foreach() from queue_foreach()]

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8

  ---

  bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this 
in dmesg:
  [   58.257605] input: TrackPoint Keyboard II Keyboard as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26
  [   58.258542] input: TrackPoint Keyboard II Mouse as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27
  [   58.259561] input: TrackPoint Keyboard II Consumer Control as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input
  /input28
  [   58.259661] input: TrackPoint Keyboard II System Control as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i
  nput29
  [   58.260151] input: TrackPoint Keyboard II as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31
  [   58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID 
v0.47 Keyboard [TrackPoint Keyboard II]
  on 10:4a:7d:01:8d:7f
  [   58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 
7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000]
  [   58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 
11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 
24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07

  This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of 
today). It did not happen in 20.10.
  When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluez 5.56-0ubuntu3
  Uname: Linux 5.11.0-051100-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Apr 14 21:03:29 2021
  InstallationDate: Installed on 2021-02-26 (47 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20AW0006US
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic 
root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago)
  dmi.bios.date: 01/27/2015
  dmi.bios.release: 2.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET77WW (2.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AW0006US
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AW0006US
  dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 10:4A:7D:01:8D:7F  ACL MTU: 1021:5  SCO MTU: 96:5
    UP RUNNING
    RX bytes:267050 acl:16636 sco:0 events:966 errors:0
    TX bytes:28087 acl:371 sco:0 commands:388 errors:0

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

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

[Kernel-packages] [Bug 1924217] Re: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()]

[John Bloom]

That's the only crash I'm experiencing. I didn't intend to set the other
bug as private, so I'm not sure what's up there.

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

Title:
  bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in
  get_report_cb() from notify_handler() from notify_handler() from
  queue_foreach() from queue_foreach()]

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8

  ---

  bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this 
in dmesg:
  [   58.257605] input: TrackPoint Keyboard II Keyboard as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26
  [   58.258542] input: TrackPoint Keyboard II Mouse as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27
  [   58.259561] input: TrackPoint Keyboard II Consumer Control as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input
  /input28
  [   58.259661] input: TrackPoint Keyboard II System Control as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i
  nput29
  [   58.260151] input: TrackPoint Keyboard II as 
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31
  [   58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID 
v0.47 Keyboard [TrackPoint Keyboard II]
  on 10:4a:7d:01:8d:7f
  [   58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 
7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000]
  [   58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 
11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 
24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07

  This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of 
today). It did not happen in 20.10.
  When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluez 5.56-0ubuntu3
  Uname: Linux 5.11.0-051100-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Apr 14 21:03:29 2021
  InstallationDate: Installed on 2021-02-26 (47 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20AW0006US
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic 
root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago)
  dmi.bios.date: 01/27/2015
  dmi.bios.release: 2.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET77WW (2.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AW0006US
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AW0006US
  dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 10:4A:7D:01:8D:7F  ACL MTU: 1021:5  SCO MTU: 96:5
    UP RUNNING
    RX bytes:267050 acl:16636 sco:0 events:966 errors:0
    TX bytes:28087 acl:371 sco:0 commands:388 errors:0

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

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