[Kernel-packages] [Bug 1920030] Re: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops

[jeremyszu]

** Changed in: oem-priority
   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/1920030

Title:
  Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Fix Released
Status in linux-oem-5.10 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  The Mute/Mic-mute LEDs are not work when muting audio-output/microphone on HP 
850/840/440 G8 laptops.

  [Fix]
  Add three realtek quirks for them.

  [Test]
  After applying the quirks, the LEDs are functioned on HP 850/840/440 G8 
laptops.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem IDs of 
audio codec which are using different GPIO pins (different layout), then the 
quirks will not work (LEDs will not function when muting audio-output or 
microphone.

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

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

[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

[Kai-Heng Feng]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After boot the idle power consumption is around 2.3 W but after suspend it is 
4.7 W.
  The measurement is 5-10 min after boot/resume - looking at "top" to see 
system was idle.
  This is consistent - I have tried more that 10 times. 
  BIOS is updated to latest version.
  I have checked power consumption with external meter - and confirmed that it 
is higher.

  I have attached output of:
  sudo powertop -t 60 -r --html=before.html  (and after)

  I have noticed that Package C-state 6 is reached before suspend but
  not after.

  I expect that idle power consumption after suspend should be the same
  as before.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-38-generic 5.8.0-38.43
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hjh1448 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 15:49:32 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-01-03 (13 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-38-generic N/A
   linux-backports-modules-5.8.0-38-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425JA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425JA
  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.4
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425JA_UX425JA
  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/1912057/+subscriptions

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

[Kernel-packages] [Bug 1905020] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2021-04-14 02:14 EDT---
IBM Bugzilla status->closed, Fix Released with hirsuite

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

Title:
  [21.04 FEAT] Add kernel debug infos for decompressor stage to kernel-
  debug package

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  In order to be able to debug kernel crashes during the early decompressing 
phase, it would be useful to add the vmlinux file from the decompressor stage 
to the kernel-debug deb package.
  The file is located in arch/s390/boot/compressed/vmlinux.
  There are plans to make the kernel relocatable and move more things to the 
decompressor stage, which would be easier to debug in case of a problem if we 
have this file in the debug info package.

  Business Case:
  Increase problem determination / serviceability.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1905020/+subscriptions

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

[Kernel-packages] [Bug 1905591] Re: no brightness control in {455, 460} after update from 450

[JAVIER COBOS MESA]

Same problem on Legion 5 AMD® Ryzen 7 4800h with radeon graphics × 16 RTX 2060
Solution in comment 11 didn't work for me
Also tried some grub commands that did not work.

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

Title:
  no brightness control in {455,460} after update from 450

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

Bug description:
  On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce
  GTX 1050 Ti Mobile]:

  WORKS FINE:
  nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1

  NO BRIGHTNESS CONTROL:
  nvidia-driver-455: 455.38-0ubuntu0.18.04.1
  nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
  nvidia-driver-460: 460.39-0ubuntu0.18.04.1

  *WORKAROUND: See comment #11 (add nvidia drivers to initramfs).

  *Note that 460 fixes it for a 20.04 ThinkPad P73 per comment #6, but
  not for my 18.04.5 Lenovo ThinkPad X1 per comment #5.

  Updating to nvidia-driver-455 (or -460) results in loss of brightness
  control.  On boot, the laptop display brightness is somewhat less than
  fully bright and cannot be changed.   The brightness up/down keys do
  pop up the gnome gui brightness widget, and
  /sys/class/backlight/nvidia_0/* values do change, but the actual
  display's brightness does not.

  Problem occurs with either version of nvidia-driver-455 (the archive
  or the ~graphics-drivers/PPA) or any version of -460.

  Normal functionality returns if I downgrade to any version of nvidia-
  driver-450.

  Also observed: 455 and 460 temporarily display some pixel garbage
  while mode-switching during the graphic login sequence.  Only a minor
  glitch, but note that 450 does not exhibit that issue either.

  Note also that manually applying this to 
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
  
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04
  Codename: bionic

  kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
  2020 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1917609] Re: [Regression] ubuntu_bpf failed to build on Groovy

[Po-Hsu Lin]

https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=a2bc8326c70f673744173df772c8026cbb4f10dd

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Ian (ian-may)

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

Title:
  [Regression] ubuntu_bpf failed to build on Groovy

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

Bug description:
  [Impact]
  Upstream commit d3bec0138bfbe58606fc1d6f57a4cdc1a20218db (bpf: Zero-fill 
re-used per-cpu map element) was applied to Groovy as part of an upstream 
stable update. This patch fixes a bpf issue and at the same time adds new 
selftests to verify these changes. However, the selftests can't be compiled on 
5.8 due to missing helper functions that were added only later. The bpf 
selftest build fails with errors such as:

  /usr/bin/ld: 
/tmp/autopkgtest.IzBxE1/build.8NX/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/map_init.test.o:
 in function `prog_run_insert_elem':

/tmp/autopkgtest.IzBxE1/build.8NX/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/prog_tests/map_init.c:89:
 undefined reference to `ASSERT_OK'

  [Fix]
  The proposed fix it to partially revert this commit by removing the selftests 
parts.

  [Testcase]
  On a groovy/linux repo:

  $ make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS=

  [Where problems could occur]
  By removing the selftests we could be introducing a regression with the bpf 
code change which would be likely unoticed during the tests.

  
   Original Description 

  Issue found on 5.8.0-1024.26-azure / 5.8.0-1022.23-oracle

  Test failed to build, I didn't see any meaningful error message, this
  might need to be double checked.

  HDRINST usr/include/asm/fcntl.h
  HDRINST usr/include/asm/termbits.h
  HDRINST usr/include/asm/errno.h
  INSTALL ./usr/include
    make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux'
    make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
    stderr:
    make: *** [Makefile:159: all] Error 1

  Please find attachment for the complete test log.

  == Process to reproduce this ==
  1. git clone 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/groovy
  2. cd groovy/tools/testing/selftests
  3. make TARGETS=bpf
  You will see the build failed if it's affected by this.

  I think this is affecting the ubuntu_kernel_selftests as well, as the
  net test would require the bpf test to be built first.

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

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

[Kernel-packages] [Bug 1862588] Re: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels

[Po-Hsu Lin]

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

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

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

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

** Changed in: linux-signed-oracle-5.0 (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: linux-signed-oracle-5.0 (Ubuntu)
   Status: New => Invalid

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

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

Title:
  user_notification_basic in seccomp of ubuntu_kernel_selftest failed on
  Bionic-5.0 Kernels

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-signed-oracle-5.0 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-aws source package in Bionic:
  Invalid
Status in linux-gcp source package in Bionic:
  Invalid
Status in linux-signed-oracle-5.0 source package in Bionic:
  Invalid
Status in linux source package in Disco:
  Won't Fix
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-gcp source package in Disco:
  Won't Fix
Status in linux-signed-oracle-5.0 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Released
Status in linux-aws source package in Eoan:
  Fix Released
Status in linux-gcp source package in Eoan:
  Fix Released
Status in linux-signed-oracle-5.0 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  Running seccomp kernel selftests will fail.

  [Test case]
  Run linux/tools/testing/selftests/seccomp/seccomp_bpf.

  On failure:

  seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
  seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == 
errno (0)
  global.user_notification_basic: Test failed at step #3
  [ FAIL ] global.user_notification_basic

  On success:

  [ RUN  ] global.user_notification_basic
  [   OK ] global.user_notification_basic

  
  [Regression potential]
  The test is checking that the given structure which the kernel will write to 
is all zeroes. It's doing it because it wants userspace to have the possibility 
in the future to give data there indicating support for an extension that might 
be developed in the future. As the test is there right now, not applying the 
breaking uABI fix might cause us to miss applications that would break in 
future kernels. As the backport for that is prone for more regression 
potential, we are deciding to revert the new test.

  ==

  Issue found on Oracle Bionic 5.0 (oracle : 5.0.0-1011.16 : amd64)

  [ RUN  ] global.user_notification_basic
  seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
  seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == 
errno (0)
  global.user_notification_basic: Test failed at step #3
  [ FAIL ] global.user_notification_basic

  This cannot be reproduced with the kselftest in older kernel, probably
  a test case issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1011-oracle 5.0.0-1011.16
  ProcVersionSignature: User Name 5.0.0-1011.16-oracle 5.0.21
  Uname: Linux 5.0.0-1011-oracle x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  Date: Mon Feb 10 05:17:54 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oracle-5.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Kernel-packages] [Bug 1923390] Re: NVidia driver 460 doesn't work after updating to proposed kernel 5.11.0-14.15-generic

[Chris Hermansen]

Not at present.  The problem went away immediately after running the apt
purge and then rebooting, and has not reoccurred since.  So I'm not
suffering at all at this point.  I reported it in case my situation
provided useful information for others.

On Tue, Apr 13, 2021 at 7:15 PM Daniel van Vugt <1923...@bugs.launchpad.net>
wrote:

> OK, thanks. Does that mean the problem is still active even with
> Ubuntu's official Nvidia driver?
>
> ** Changed in: linux (Ubuntu)
>Status: Invalid => Incomplete
>
> ** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
>Status: Invalid => Incomplete
>
> ** Tags removed: regression-proposed
> ** Tags added: regression-release
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1923390
>
> Title:
>   NVidia driver 460 doesn't work after updating to proposed kernel
>   5.11.0-14.15-generic
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923390/+subscriptions
>


-- 
Chris Hermansen · clhermansen "at" gmail "dot" com

C'est ma façon de parler.

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

Title:
  NVidia driver 460 doesn't work after updating to proposed kernel
  5.11.0-14.15-generic

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Incomplete

Bug description:
  Saturday night at about 03:00 UTC I noticed that an update to my
  system (Hirsute / 21.04) would no longer properly work with my NVidia
  RTX 3060; I was left in very low resolution mode.  When I ran
  Additional Drivers, the screen indicated that I had manually installed
  graphics drivers and I could not select the official and tested NVidia
  drivers.  I am assuming these "manually" installed drivers were a part
  of a system update as I did nothing to install any drivers on my own.

  I found a suggestion to run "apt purge nvdia-\*", which I did.  When I
  rebooted, I was able to select the "Using NVIDIA driver metapackage
  from nvidia-driver-460 (proprietary,tested), and my screen resolution
  and general behaviour seemed fine from that point on.

  In case it doesn't come through in the uploaded files, here are the
  lines from /var/log/dpkg.log relating to my purge:

  2021-04-10 20:28:09 startup packages purge
  2021-04-10 20:28:09 purge nvidia-compute-utils-460:amd64 460.67-0ubuntu1 

  2021-04-10 20:28:09 status config-files nvidia-compute-utils-460:amd64 
460.67-0ubuntu1
  2021-04-10 20:28:09 status not-installed nvidia-compute-utils-460:amd64 
  2021-04-10 20:28:09 purge nvidia-prime:all 0.8.16.1 
  2021-04-10 20:28:09 status config-files nvidia-prime:all 0.8.16.1
  2021-04-10 20:28:09 status not-installed nvidia-prime:all 
  2021-04-10 20:28:09 purge nvidia-kernel-common-460:amd64 460.67-0ubuntu1 

  2021-04-10 20:28:09 status config-files nvidia-kernel-common-460:amd64 
460.67-0ubuntu1
  2021-04-10 20:28:09 status triggers-pending initramfs-tools:all 0.139ubuntu3
  2021-04-10 20:28:09 status not-installed nvidia-kernel-common-460:amd64 
  2021-04-10 20:28:09 purge linux-modules-nvidia-460-5.11.0-13-generic:amd64 
5.11.0-13.14+2 
  2021-04-10 20:28:09 status config-files 
linux-modules-nvidia-460-5.11.0-13-generic:amd64 5.11.0-13.14+2
  2021-04-10 20:28:10 status not-installed 
linux-modules-nvidia-460-5.11.0-13-generic:amd64 
  2021-04-10 20:28:10 purge nvidia-settings:amd64 460.56-0ubuntu2 
  2021-04-10 20:28:10 status config-files nvidia-settings:amd64 460.56-0ubuntu2
  2021-04-10 20:28:10 status not-installed nvidia-settings:amd64 

  Note the time shown is Vancouver/Canada Pacific Daylight.

  It may be worth mentioning that nouveau doesn't recognize the RTX 3060
  (I understand that this is a very recently released video card).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:  gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5Ch

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

[Kai-Heng Feng]

Then please test latest mainline kernel and attach dmesg:
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/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 1919252] Re: zfs-dkms on Focal still allows building on Linux kernel version 5.10+

[Chris Halse Rogers]

Hello Ratchanan, or anyone else affected,

Accepted zfs-linux into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.3-1ubuntu12.8 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: zfs-linux (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
  touchpad don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i am using vi command to open .txt file, and then i can not use my touchpad. 
It's seems response nothing.
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-70-generic 5.4.0-70.78
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  f4 1565 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 10:40:10 2021
  InstallationDate: Installed on 2020-11-29 (136 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06cb:00da Synaptics, Inc. 
   Bus 001 Device 002: ID 04f2:b6d9 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20RA004QVN
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic 
root=UUID=a9548559-590d-41f6-a6cd-81e1a3461eaa ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-70-generic N/A
   linux-backports-modules-5.4.0-70-generic  N/A
   linux-firmware1.187.10
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2021-03-04 (40 days ago)
  dmi.bios.date: 01/07/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R16ET23W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20RA004QVN
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55756 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR16ET23W(1.09):bd01/07/2020:svnLENOVO:pn20RA004QVN:pvrThinkPadE14:rvnLENOVO:rn20RA004QVN:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14
  dmi.product.name: 20RA004QVN
  dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14
  dmi.product.version: ThinkPad E14
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1923697] [NEW] touchpad don't work

[phoung vo duc]

Public bug reported:

i am using vi command to open .txt file, and then i can not use my touchpad. 
It's seems response nothing.
Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-70-generic 5.4.0-70.78
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  f4 1565 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 14 10:40:10 2021
InstallationDate: Installed on 2020-11-29 (136 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 06cb:00da Synaptics, Inc. 
 Bus 001 Device 002: ID 04f2:b6d9 Chicony Electronics Co., Ltd Integrated Camera
 Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20RA004QVN
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic 
root=UUID=a9548559-590d-41f6-a6cd-81e1a3461eaa ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-70-generic N/A
 linux-backports-modules-5.4.0-70-generic  N/A
 linux-firmware1.187.10
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2021-03-04 (40 days ago)
dmi.bios.date: 01/07/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: R16ET23W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20RA004QVN
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55756 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR16ET23W(1.09):bd01/07/2020:svnLENOVO:pn20RA004QVN:pvrThinkPadE14:rvnLENOVO:rn20RA004QVN:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14
dmi.product.name: 20RA004QVN
dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14
dmi.product.version: ThinkPad E14
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  touchpad don't work

Status in linux package in Ubuntu:
  New

Bug description:
  i am using vi command to open .txt file, and then i can not use my touchpad. 
It's seems response nothing.
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-70-generic 5.4.0-70.78
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  f4 1565 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 10:40:10 2021
  InstallationDate: Installed on 2020-11-29 (136 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06cb:00da Synaptics, Inc. 
   Bus 001 Device 002: ID 04f2:b6d9 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20RA004QVN
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic 
root=UUID=a9548559-590d-41f6-a6cd-81e1a3461eaa ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-70-generic N/A
   linux-backports-modules-5.4.0-70-generic  N/A
   linux-firmware1.187.10
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2021-03-04 (40 days ago)
  dmi.bios.date: 01/07/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R16ET23W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20RA004QVN
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55756 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR16ET23W(1.09):bd01/07/2020:svnLENOVO:pn20RA004QVN:pvrThinkPadE14:rvnLENOVO:rn20RA004QVN:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14
  dmi.product.name: 20RA004QVN
  dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14
  dmi.product.version: ThinkPad E14
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1920632] Re: use of Wacom stylus causes immediate system hang with kernel 5.8.0-45, but 5.8.0-44 works

[Daniel van Vugt]

** Changed in: linux-hwe-5.8 (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  use of Wacom stylus causes immediate system hang with kernel 5.8.0-45,
  but 5.8.0-44 works

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.8 package in Ubuntu:
  Fix Released
Status in linux-signed-hwe-5.8 package in Ubuntu:
  Fix Released

Bug description:
  Once updated kernel from 5.8.0-44 to 5.8.0.45, any use of Wacom stylus causes 
immediate system hang, frozen both GUI and OS. Removing the Wacom kernel module 
solves the problem (no more hangs, but the stylus is unusable then).
  Rolling back to kernel 5.8.0-44 or any earlier solves the problem.

  The OS is:  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 20 18:53:56 2021
  InstallationDate: Installed on 2020-04-24 (329 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1922536] Re: Intel Killer Wi-Fi 6 AX1650i [8086:34f0] Subsystem [8086:0074]: Bluetooth (ideapad_bluetooth) not working in gnome settings after reboot and requires systemctl rest

[Daniel van Vugt]

** Tags added: regression-release

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

Title:
  Intel Killer Wi-Fi 6 AX1650i [8086:34f0] Subsystem [8086:0074]:
  Bluetooth (ideapad_bluetooth) not working in gnome settings after
  reboot and requires systemctl restart bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Selected logs:
  https://paste.ubuntu.com/p/gMbk2ntQyz/
  https://paste.ubuntu.com/p/F8n72kCbJJ/
  lshw:
  https://paste.ubuntu.com/p/3Z9jwBdyVt/

  If I try and use the bluetooth toggle in gnome settings upon boot it
  won't do anything. If I have the bluetooth settings window open in
  gnome settings and manually restart the bluetooth service with: "sudo
  systemctl restart bluetooth" then it starts searching for devices and
  I was able to pair Samsung Galaxy Earbuds after multiple service
  restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluez 5.56-0ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  5 00:35:34 2021
  InstallationDate: Installed on 2021-04-05 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 81Q9
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=dd9e8fc7-3c6a-462d-8cea-b37801ba586d ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.release: 1.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:br1.54:efr1.43:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D8:3B:BF:4D:22:D0  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:302871 acl:36 sco:0 events:10305 errors:0
TX bytes:822111 acl:36 sco:0 commands:5384 errors:0

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

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

[Kernel-packages] [Bug 1923390] Re: NVidia driver 460 doesn't work after updating to proposed kernel 5.11.0-14.15-generic

[Daniel van Vugt]

OK, thanks. Does that mean the problem is still active even with
Ubuntu's official Nvidia driver?

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

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Status: Invalid => Incomplete

** Tags removed: regression-proposed
** Tags added: regression-release

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

Title:
  NVidia driver 460 doesn't work after updating to proposed kernel
  5.11.0-14.15-generic

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Incomplete

Bug description:
  Saturday night at about 03:00 UTC I noticed that an update to my
  system (Hirsute / 21.04) would no longer properly work with my NVidia
  RTX 3060; I was left in very low resolution mode.  When I ran
  Additional Drivers, the screen indicated that I had manually installed
  graphics drivers and I could not select the official and tested NVidia
  drivers.  I am assuming these "manually" installed drivers were a part
  of a system update as I did nothing to install any drivers on my own.

  I found a suggestion to run "apt purge nvdia-\*", which I did.  When I
  rebooted, I was able to select the "Using NVIDIA driver metapackage
  from nvidia-driver-460 (proprietary,tested), and my screen resolution
  and general behaviour seemed fine from that point on.

  In case it doesn't come through in the uploaded files, here are the
  lines from /var/log/dpkg.log relating to my purge:

  2021-04-10 20:28:09 startup packages purge
  2021-04-10 20:28:09 purge nvidia-compute-utils-460:amd64 460.67-0ubuntu1 

  2021-04-10 20:28:09 status config-files nvidia-compute-utils-460:amd64 
460.67-0ubuntu1
  2021-04-10 20:28:09 status not-installed nvidia-compute-utils-460:amd64 
  2021-04-10 20:28:09 purge nvidia-prime:all 0.8.16.1 
  2021-04-10 20:28:09 status config-files nvidia-prime:all 0.8.16.1
  2021-04-10 20:28:09 status not-installed nvidia-prime:all 
  2021-04-10 20:28:09 purge nvidia-kernel-common-460:amd64 460.67-0ubuntu1 

  2021-04-10 20:28:09 status config-files nvidia-kernel-common-460:amd64 
460.67-0ubuntu1
  2021-04-10 20:28:09 status triggers-pending initramfs-tools:all 0.139ubuntu3
  2021-04-10 20:28:09 status not-installed nvidia-kernel-common-460:amd64 
  2021-04-10 20:28:09 purge linux-modules-nvidia-460-5.11.0-13-generic:amd64 
5.11.0-13.14+2 
  2021-04-10 20:28:09 status config-files 
linux-modules-nvidia-460-5.11.0-13-generic:amd64 5.11.0-13.14+2
  2021-04-10 20:28:10 status not-installed 
linux-modules-nvidia-460-5.11.0-13-generic:amd64 
  2021-04-10 20:28:10 purge nvidia-settings:amd64 460.56-0ubuntu2 
  2021-04-10 20:28:10 status config-files nvidia-settings:amd64 460.56-0ubuntu2
  2021-04-10 20:28:10 status not-installed nvidia-settings:amd64 

  Note the time shown is Vancouver/Canada Pacific Daylight.

  It may be worth mentioning that nouveau doesn't recognize the RTX 3060
  (I understand that this is a very recently released video card).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:  gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 11 19:53:17 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.67, 5.11.0-13-generic, x86_64: installed
   nvidia, 460.67, 5.11.0-14-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GA106 [GeForce RTX 3060] [10de:2503] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:3657]
  InstallationDate: Installed on 2021-04-10 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210408)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-gener

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

[Matthew Ruffell]

Hi @Hmpf,

Thanks for filing a bug report.

I had a look at the changes between 5.4.0-70-generic and
5.4.0-71-generic, and I found three patches for CIFS:

$ git log --grep "cifs" Ubuntu-5.4.0-70.78..Ubuntu-5.4.0-71.79
https://paste.ubuntu.com/p/YgrZcN8B6j/

I had a read of the patches, and I think that this one is causing
problems for you.

commit 21b200d091826a83aafc95d847139b2b0582f6d1
Author: Aurelien Aptel 
Date:   Fri Feb 5 15:42:48 2021 +0100
Subject: cifs: report error instead of invalid when revalidating a dentry fails
Link: 
https://github.com/torvalds/linux/commit/21b200d091826a83aafc95d847139b2b0582f6d1

This was backported to 5.4.0-71-generic through upstream stable in the
below patch:

https://paste.ubuntu.com/p/8FWhRNr8KW/

Now, I think it is that commit due to the error message you are seeing:

CIFS VFS: cifs_read_super: get root inode failed

The commit changes how errors are passed back to the VFS. What it did
before was just return 0 (invalid) on any error at all, when
cifs_revalidate_dentry() failed.

What it does now is send 0 on ENOENT and ESTALE, and the actual error
number on any other error. I think you are getting an "other" error, and
cifs isn't sure what to do with it.

Now, looking at cifs_read_super(), where the error message came from:

 150 static int
 151 cifs_read_super(struct super_block *sb)
 152 {
 ...
 205 rc = super_setup_bdi(sb);
 206 if (rc)
 207 goto out_no_root;
 ...
 213 inode = cifs_root_iget(sb);
 214 
 215 if (IS_ERR(inode)) {
 216 rc = PTR_ERR(inode);
 217 goto out_no_root;
 218 }
 ...
 225 sb->s_root = d_make_root(inode);
 226 if (!sb->s_root) {
 227 rc = -ENOMEM;
 228 goto out_no_root;
 229 }
 ...
 240 out_no_root:
 241 cifs_dbg(VFS, "%s: get root inode failed\n", __func__);
 242 return rc;
 243 }
 
We see the out_no_root label is really just a catch-all error handler, and 
doesn't really tell us what happened, or try to handle the error.

Looking at the code added by the commit, it added a new debug string:

737 static int
738 cifs_d_revalidate(struct dentry *direntry, unsigned int flags)
739 {
...
751 rc = cifs_revalidate_dentry(direntry);
752 if (rc) {
753 cifs_dbg(FYI, "cifs_revalidate_dentry failed with rc=%d", rc);

We can use this string to see what the actual error is, but it is turned
off by default, which is why it doesn't appear in dmesg.

Would you be able to turn on this extra error message so we can keep
helping you to figure out what is happening?

You can turn on extra debugging with instruction from:
https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting

1) sudo -s
2) echo 'module cifs +p' > /sys/kernel/debug/dynamic_debug/control
3) echo 'file fs/cifs/* +p' > /sys/kernel/debug/dynamic_debug/control
4) echo 7 > /proc/fs/cifs/cifsFYI
5) exit

Then, try your mount command and then try ls on that dentry file.

If you check dmesg, you will get much more logging. What we are
interested in will be a line with "cifs_revalidate_dentry failed with
rc" and then an error number.

We can then look up what the number is, and try go from there.

The easiest way to turn off the extra debug logging is to reboot your
system. Or you can run:

1) sudo -s
2) echo 0 > /proc/fs/cifs/cifsFYI
3) exit

But rebooting is probably easier for you.

Attach your new dmesg to the launchpad bug, and I will have a look. You
might want to remove the URL of your company cifs share and any
usernames before you upload.

Let me know if you have any questions.

Thanks,
Matthew

** Tags added: seg

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

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=a1

[Kernel-packages] [Bug 1883493] Re: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!

[fabtagon]

Update: issue seems to have reappeared even with
5.12.0-051200rc6drmtip20210410-generic, unfortunately. I got a white
blank screen while using LibreOffice and Firefox. System was no longer
reachable via network and nothing got written to syslog, so probably the
kernel has died hard.

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

Title:
  amdgpu hangs from time to time with *ERROR* Waiting for fences timed
  out!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  un 15 08:30:42 alhazen kernel: [ 1566.155810] 
[drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences 
timed out!
  Jun 15 08:30:47 alhazen kernel: [ 1566.159792] 
[drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences 
timed out!
  Jun 15 08:30:47 alhazen kernel: [ 1571.020144] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=535493, emitted 
seq=535495
  Jun 15 08:30:47 alhazen kernel: [ 1571.020216] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 3664 thread Xorg:cs0 
pid 3694
  Jun 15 08:30:47 alhazen kernel: [ 1571.020218] [drm] GPU recovery disabled.

  Mouse pointer still moves, but apart from that the display is frozen.
  Music keeps playing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 09:09:56 2020
  InstallationDate: Installed on 2020-05-28 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi-enforce-resources=lax 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0604
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/02/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1909422] Re: ubuntu_ftrace_smoke_test timeout on G-riscv

[Kelsey Skunberg]

There still seems to be a timeout occurring on G/riscv and F/riscv-5.8,
though the results cut off:

04/13 22:39:04 DEBUG| utils:0116| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_ftrace_smoke_test/ubuntu_ftrace_smoke_test.sh'
04/13 22:39:04 DEBUG| utils:0153| [stdout] PASSED (CONFIG_FUNCTION_TRACER=y 
in /boot/config-5.8.0-21-generic)
04/13 22:39:04 DEBUG| utils:0153| [stdout] PASSED 
(CONFIG_FUNCTION_GRAPH_TRACER=y in /boot/config-5.8.0-21-generic)
04/13 22:39:04 DEBUG| utils:0153| [stdout] PASSED (CONFIG_STACK_TRACER=y in 
/boot/config-5.8.0-21-generic)
04/13 22:39:05 DEBUG| utils:0153| [stdout] PASSED (CONFIG_DYNAMIC_FTRACE=y 
in /boot/config-5.8.0-21-generic)
04/13 22:39:07 DEBUG| utils:0153| [stdout] PASSED all expected 
/sys/kernel/debug/tracing files exist
04/13 22:39:07 DEBUG| utils:0153| [stdout] PASSED (function_graph in 
/sys/kernel/debug/tracing/available_tracers)
04/13 22:39:07 DEBUG| utils:0153| [stdout] PASSED (function in 
/sys/kernel/debug/tracing/available_tracers)
04/13 22:39:07 DEBUG| utils:0153| [stdout] PASSED (nop in 
/sys/kernel/debug/tracing/available_tracers)
04/13 22:39:13 DEBUG| utils:0153| [stdout] PASSED (tracer function can be 
enabled)
04/13 22:39:22 DEBUG| utils:0153| [stdout] PASSED (tracer function_graph 
can be enabled)

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

Title:
  ubuntu_ftrace_smoke_test timeout on G-riscv

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

Bug description:
  Issue found on 5.8.0-13.15 RISCV with a KVM instance.

  Test failed with "Timer expired (1350 sec.), nuking pid 520", test log:
  $ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_ftrace_smoke_test/control 
  03:46:12 INFO | Writing results to 
/home/ubuntu/autotest/client/results/default
  03:46:12 DEBUG| Initializing the state engine
  03:46:12 DEBUG| Persistent state client.steps now set to []
  03:46:13 DEBUG| Persistent option harness now set to None
  03:46:13 DEBUG| Persistent option harness_args now set to None
  03:46:13 DEBUG| Selected harness: standalone
  03:46:15 INFO | START timestamp=1609127175localtime=Dec 
28 03:46:15   
  03:46:16 DEBUG| Persistent state client._record_indent now set to 1
  03:46:16 DEBUG| Test has timeout: 1350 sec.
  03:46:16 INFO |   START   ubuntu_ftrace_smoke_test.ftrace-smoke-test  
ubuntu_ftrace_smoke_test.ftrace-smoke-test  timestamp=1609127176
timeout=1350localtime=Dec 28 03:46:16   
  03:46:16 DEBUG| Persistent state client._record_indent now set to 2
  03:46:16 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_ftrace_smoke_test.ftrace-smoke-test', 
'ubuntu_ftrace_smoke_test.ftrace-smoke-test')
  03:46:16 DEBUG| Waiting for pid 520 for 1350 seconds
  03:46:16 WARNI| System python is too old, crash handling disabled
  03:46:16 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_ftrace_smoke_test/ubuntu_ftrace_smoke_test.sh'
  03:46:16 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_TRACER=y in 
/boot/config-5.8.0-13-generic)
  03:46:17 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in 
/boot/config-5.8.0-13-generic)
  03:46:17 DEBUG| [stdout] PASSED (CONFIG_STACK_TRACER=y in 
/boot/config-5.8.0-13-generic)
  03:46:17 DEBUG| [stdout] PASSED (CONFIG_DYNAMIC_FTRACE=y in 
/boot/config-5.8.0-13-generic)
  03:46:19 DEBUG| [stdout] PASSED all expected /sys/kernel/debug/tracing files 
exist
  03:46:19 DEBUG| [stdout] PASSED (function_graph in 
/sys/kernel/debug/tracing/available_tracers)
  03:46:19 DEBUG| [stdout] PASSED (function in 
/sys/kernel/debug/tracing/available_tracers)
  03:46:20 DEBUG| [stdout] PASSED (nop in 
/sys/kernel/debug/tracing/available_tracers)
  03:46:26 DEBUG| [stdout] PASSED (tracer function can be enabled)
  03:46:35 DEBUG| [stdout] PASSED (tracer function_graph can be enabled)
  03:46:35 DEBUG| [stdout]  - tracer function_graph got enough data
  03:46:35 DEBUG| [stdout]  - tracer function_graph completed
  03:46:36 DEBUG| [stdout]  - tracer function_graph being turned off
  03:46:36 DEBUG| [stdout]  - tracer got 532 irq events
  03:46:43 DEBUG| [stdout]  - tracer hwlat got enough data
  03:46:43 DEBUG| [stdout]  - tracer hwlat completed
  03:46:43 DEBUG| [stdout]  - tracer hwlat being turned off
  03:46:44 DEBUG| [stdout]  - tracer nop being set as current tracer
  03:46:46 DEBUG| [stdout] PASSED (tracer hwlat can be enabled (got 12 lines of 
tracing output))
  03:46:48 DEBUG| [stdout]  - tracer blk got enough data
  03:46:48 DEBUG| [stdout]  - tracer blk completed
  03:46:48 DEBUG| [stdout]  - tracer blk being turned off
  03:46:48 DEBUG| [stdout]  - tracer nop being set as current tracer
  03:46:50 DEBUG| [stdout] PASSED (tracer blk can be enabled (got 2 lines of 
tracing outpu

[Kernel-packages] [Bug 1909422] Re: ubuntu_ftrace_smoke_test timeout on G-riscv

[Kelsey Skunberg]

** Tags added: riscv riscv64 sru-20210315

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

Title:
  ubuntu_ftrace_smoke_test timeout on G-riscv

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

Bug description:
  Issue found on 5.8.0-13.15 RISCV with a KVM instance.

  Test failed with "Timer expired (1350 sec.), nuking pid 520", test log:
  $ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_ftrace_smoke_test/control 
  03:46:12 INFO | Writing results to 
/home/ubuntu/autotest/client/results/default
  03:46:12 DEBUG| Initializing the state engine
  03:46:12 DEBUG| Persistent state client.steps now set to []
  03:46:13 DEBUG| Persistent option harness now set to None
  03:46:13 DEBUG| Persistent option harness_args now set to None
  03:46:13 DEBUG| Selected harness: standalone
  03:46:15 INFO | START timestamp=1609127175localtime=Dec 
28 03:46:15   
  03:46:16 DEBUG| Persistent state client._record_indent now set to 1
  03:46:16 DEBUG| Test has timeout: 1350 sec.
  03:46:16 INFO |   START   ubuntu_ftrace_smoke_test.ftrace-smoke-test  
ubuntu_ftrace_smoke_test.ftrace-smoke-test  timestamp=1609127176
timeout=1350localtime=Dec 28 03:46:16   
  03:46:16 DEBUG| Persistent state client._record_indent now set to 2
  03:46:16 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_ftrace_smoke_test.ftrace-smoke-test', 
'ubuntu_ftrace_smoke_test.ftrace-smoke-test')
  03:46:16 DEBUG| Waiting for pid 520 for 1350 seconds
  03:46:16 WARNI| System python is too old, crash handling disabled
  03:46:16 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_ftrace_smoke_test/ubuntu_ftrace_smoke_test.sh'
  03:46:16 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_TRACER=y in 
/boot/config-5.8.0-13-generic)
  03:46:17 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in 
/boot/config-5.8.0-13-generic)
  03:46:17 DEBUG| [stdout] PASSED (CONFIG_STACK_TRACER=y in 
/boot/config-5.8.0-13-generic)
  03:46:17 DEBUG| [stdout] PASSED (CONFIG_DYNAMIC_FTRACE=y in 
/boot/config-5.8.0-13-generic)
  03:46:19 DEBUG| [stdout] PASSED all expected /sys/kernel/debug/tracing files 
exist
  03:46:19 DEBUG| [stdout] PASSED (function_graph in 
/sys/kernel/debug/tracing/available_tracers)
  03:46:19 DEBUG| [stdout] PASSED (function in 
/sys/kernel/debug/tracing/available_tracers)
  03:46:20 DEBUG| [stdout] PASSED (nop in 
/sys/kernel/debug/tracing/available_tracers)
  03:46:26 DEBUG| [stdout] PASSED (tracer function can be enabled)
  03:46:35 DEBUG| [stdout] PASSED (tracer function_graph can be enabled)
  03:46:35 DEBUG| [stdout]  - tracer function_graph got enough data
  03:46:35 DEBUG| [stdout]  - tracer function_graph completed
  03:46:36 DEBUG| [stdout]  - tracer function_graph being turned off
  03:46:36 DEBUG| [stdout]  - tracer got 532 irq events
  03:46:43 DEBUG| [stdout]  - tracer hwlat got enough data
  03:46:43 DEBUG| [stdout]  - tracer hwlat completed
  03:46:43 DEBUG| [stdout]  - tracer hwlat being turned off
  03:46:44 DEBUG| [stdout]  - tracer nop being set as current tracer
  03:46:46 DEBUG| [stdout] PASSED (tracer hwlat can be enabled (got 12 lines of 
tracing output))
  03:46:48 DEBUG| [stdout]  - tracer blk got enough data
  03:46:48 DEBUG| [stdout]  - tracer blk completed
  03:46:48 DEBUG| [stdout]  - tracer blk being turned off
  03:46:48 DEBUG| [stdout]  - tracer nop being set as current tracer
  03:46:50 DEBUG| [stdout] PASSED (tracer blk can be enabled (got 2 lines of 
tracing output))
  03:46:56 INFO | Timer expired (1350 sec.), nuking pid 520
  03:46:57 INFO |   ERROR   
ubuntu_ftrace_smoke_test.ftrace-smoke-test  
ubuntu_ftrace_smoke_test.ftrace-smoke-test  timestamp=1609127216
localtime=Dec 28 03:46:56   Unhandled AutoservRunError: Could not kill 520
None
Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/job.py", line 510, in _runtest
parallel.fork_waitfor_timed(self.resultdir, pid, timeout)
  File "/home/ubuntu/autotest/client/parallel.py", line 112, in 
fork_waitfor_timed
utils.nuke_pid(pid)
  File "/home/ubuntu/autotest/client/shared/utils.py", line 1214, in 
nuke_pid
raise error.AutoservRunError('Could not kill %d' % pid, None)
AutoservRunError: Could not kill 520
None

  03:46:57 INFO |   END ERROR   
ubuntu_ftrace_smoke_test.ftrace-smoke-test  
ubuntu_ftrace_smoke_test.ftrace-smoke-test  timestamp=1609127217
localtime=Dec 28 03:46:57

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

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

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

[Hmpf]

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

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

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

Status in linux package in Ubuntu:
  Confirmed

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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923670/+subscriptions

[Kernel-packages] [Bug 1922540] Re: 99.98Hz display mode is sometimes missing on USB-C (DisplayPort) external monitor, which resets the display layout

[Freeman]

If I bring up the display switching menu and select external display
only it lets me switch the refresh rate after it bugging out and not
showing the refresh rate selector in gnome-settings.

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

Title:
  99.98Hz display mode is sometimes missing on USB-C (DisplayPort)
  external monitor, which resets the display layout

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When rebooting with USB-C external monitor (3440x1440) attached,
  display orientation in "gnome-control-center display" resets requiring
  one to reposition the windows on boot. Very annoying.

  In addition, refresh rate drop down for external display sometimes
  goes missing when setting refresh rate to 100hz instead of default
  60?Hz. Refresh rate listing and dropdown box disappears until setting
  monitor resolution to different resolution and back or reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-control-center 1:3.38.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  5 01:09:38 2021
  InstallationDate: Installed on 2021-04-05 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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:
http

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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 1923670] UdevDb.txt

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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:
https://b

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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:
https://b

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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:
ht

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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 1923670] ProcInterrupts.txt

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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 1923670] Lsusb-v.txt

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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:
https:

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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 

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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:
https:

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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:
https://bug

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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:
http

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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:
https://bug

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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:
http

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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 

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

[Hmpf]

apport information

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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:
https://bugs.

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

[Hmpf]

apport information

** Tags added: apport-collected

** Description changed:

  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

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

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

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

Status in linux package in Ubuntu:
  Incomplet

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

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

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

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

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

** Tags added: focal

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

[Kernel-packages] [Bug 1922536] Re: Intel Killer Wi-Fi 6 AX1650i [8086:34f0] Subsystem [8086:0074]: Bluetooth (ideapad_bluetooth) not working in gnome settings after reboot and requires systemctl rest

[Freeman]

Correct. Bluetooth works on 20.04 desktop.

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

Title:
  Intel Killer Wi-Fi 6 AX1650i [8086:34f0] Subsystem [8086:0074]:
  Bluetooth (ideapad_bluetooth) not working in gnome settings after
  reboot and requires systemctl restart bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Selected logs:
  https://paste.ubuntu.com/p/gMbk2ntQyz/
  https://paste.ubuntu.com/p/F8n72kCbJJ/
  lshw:
  https://paste.ubuntu.com/p/3Z9jwBdyVt/

  If I try and use the bluetooth toggle in gnome settings upon boot it
  won't do anything. If I have the bluetooth settings window open in
  gnome settings and manually restart the bluetooth service with: "sudo
  systemctl restart bluetooth" then it starts searching for devices and
  I was able to pair Samsung Galaxy Earbuds after multiple service
  restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluez 5.56-0ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  5 00:35:34 2021
  InstallationDate: Installed on 2021-04-05 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 81Q9
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=dd9e8fc7-3c6a-462d-8cea-b37801ba586d ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.release: 1.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:br1.54:efr1.43:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D8:3B:BF:4D:22:D0  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:302871 acl:36 sco:0 events:10305 errors:0
TX bytes:822111 acl:36 sco:0 commands:5384 errors:0

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

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

[Guilherme G. Piccoli]

(b) Regarding kernel, I found some oddities too [ output of dmesg | grep
-v "audit\|apparmor" ]:

GOOD: 

[ 1627.732924] hv_netvsc 00224840-7fbf-0022-4840-7fbf00224840 eth0: VF slot 1 
added
[ 1627.733637] hv_pci fb9ea909-d0dd-41b6-a1c2-98b1233e987d: PCI VMBus probing: 
Using version 0x10002
[ 1627.742469] hv_pci fb9ea909-d0dd-41b6-a1c2-98b1233e987d: PCI host bridge to 
bus d0dd:00
[ 1627.742472] pci_bus d0dd:00: root bus resource [mem 0xfe000-0xfe00f 
window]
[ 1627.743208] pci d0dd:00:02.0: [15b3:1016] type 00 class 0x02
[ 1627.747302] pci d0dd:00:02.0: reg 0x10: [mem 0xfe000-0xfe00f 64bit 
pref]
[ 1627.825728] pci d0dd:00:02.0: enabling Extended Tags
[ 1627.830106] pci d0dd:00:02.0: 0.000 Gb/s available PCIe bandwidth, limited 
by Unknown x0 link at d0dd:00:02.0 (capable of 63.008 Gb/s with 8.0 GT/s PCIe 
x8 link)
[ 1627.834774] pci d0dd:00:02.0: BAR 0: assigned [mem 0xfe000-0xfe00f 
64bit pref]
[ 1627.926227] mlx5_core d0dd:00:02.0: firmware version: 14.25.8362
[ 1627.936526] mlx5_core d0dd:00:02.0: handle_hca_cap:526:(pid 619): log_max_qp 
value in current profile is 18, changing it to HCA capability limit (12)
[ 1628.131452] mlx5_core d0dd:00:02.0: MLX5E: StrdRq(0) RqSz(1024) StrdSz(256) 
RxCqeCmprss(0)
[ 1628.256107] hv_netvsc 00224840-7fbf-0022-4840-7fbf00224840 eth0: VF 
registering: eth1
[ 1628.256147] mlx5_core d0dd:00:02.0 eth1: joined to eth0
[ 1628.257059] mlx5_core d0dd:00:02.0 eth1: Disabling LRO, not supported in 
legacy RQ
[ 1628.266117] mlx5_core d0dd:00:02.0 eth1: Disabling LRO, not supported in 
legacy RQ
[ 1628.266803] mlx5_core d0dd:00:02.0 enP53469s1np0: renamed from eth1
[ 1628.305588] mlx5_core d0dd:00:02.0 enP53469s1np0: Disabling LRO, not 
supported in legacy RQ
[ 1628.444056] mlx5_core d0dd:00:02.0 enP53469s1np0: Link up
[ 1628.445592] hv_netvsc 00224840-7fbf-0022-4840-7fbf00224840 eth0: Data path 
switched to VF: enP53469s1np0

BAD:
[5.211059] hv_netvsc 000d3ad6-1871-000d-3ad6-1871000d3ad6 eth0: VF slot 1 
added
[5.211618] hv_pci e94e34d7-6e53-4ab5-95d1-4328102a7c87: PCI VMBus probing: 
Using version 0x10002
[5.220736] hv_pci e94e34d7-6e53-4ab5-95d1-4328102a7c87: PCI host bridge to 
bus 6e53:00
[5.220739] pci_bus 6e53:00: root bus resource [mem 0xfe000-0xfe00f 
window]
[5.221465] pci 6e53:00:02.0: [15b3:1016] type 00 class 0x02
[5.239844] pci 6e53:00:02.0: reg 0x10: [mem 0xfe000-0xfe00f 64bit 
pref]
[5.317841] pci 6e53:00:02.0: enabling Extended Tags
[5.322168] pci 6e53:00:02.0: 0.000 Gb/s available PCIe bandwidth, limited 
by Unknown x0 link at 6e53:00:02.0 (capable of 63.008 Gb/s with 8.0 GT/s PCIe 
x8 link)
[5.325766] pci 6e53:00:02.0: BAR 0: assigned [mem 0xfe000-0xfe00f 
64bit pref]
[5.412415] mlx5_core 6e53:00:02.0: firmware version: 14.25.8102
[5.424153] mlx5_core 6e53:00:02.0: handle_hca_cap:526:(pid 7): log_max_qp 
value in current profile is 18, changing it to HCA capability limit (12)
[5.613614] mlx5_core 6e53:00:02.0: MLX5E: StrdRq(0) RqSz(1024) StrdSz(256) 
RxCqeCmprss(0)
[5.727686] hv_netvsc 000d3ad6-1871-000d-3ad6-1871000d3ad6 eth0: VF 
registering: eth1
[5.727714] mlx5_core 6e53:00:02.0 eth1: joined to eth0
[5.728473] mlx5_core 6e53:00:02.0 eth1: Disabling LRO, not supported in 
legacy RQ
[5.740989] mlx5_core 6e53:00:02.0 eth1: Disabling LRO, not supported in 
legacy RQ
[5.741670] mlx5_core 6e53:00:02.0 enP28243s1np0: renamed from eth1
[5.785980] mlx5_core 6e53:00:02.0 enP28243s1np0: Disabling LRO, not 
supported in legacy RQ
[8.790213] mlx5_core 6e53:00:02.0 enP28243s1np0: Link up
[8.791599] hv_netvsc 000d3ad6-1871-000d-3ad6-1871000d3ad6 eth0: Data path 
switched to VF: enP28243s1np0
[8.792382] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[9.759956] hv_netvsc 000d3ad6-1871-000d-3ad6-1871000d3ad6 eth0: Data path 
switched from VF: enP28243s1np0
[   10.388005] mlx5_core 6e53:00:02.0 enP28243s1np0: Link up
[   10.389894] hv_netvsc 000d3ad6-1871-000d-3ad6-1871000d3ad6 eth0: Data path 
switched to VF: enP28243s1np0
[...]
[79404.014695] hv_netvsc 000d3ad6-1871-000d-3ad6-1871000d3ad6 eth0: Data path 
switched from VF: enP28243s1np0
[79404.015275] hv_netvsc 000d3ad6-1871-000d-3ad6-1871000d3ad6 eth0: VF 
unregistering: enP28243s1np0
[79404.988951] hv_netvsc 000d3ad6-1871-000d-3ad6-1871000d3ad6 eth0: VF slot 1 
removed
[79536.467267] hv_netvsc 000d3ad6-1871-000d-3ad6-1871000d3ad6 eth0: VF slot 1 
added
[79536.467725] hv_pci e94e34d7-6e53-4ab5-95d1-4328102a7c87: PCI VMBus probing: 
Using version 0x10002
[79536.477073] hv_pci e94e34d7-6e53-4ab5-95d1-4328102a7c87: PCI host bridge to 
bus 6e53:00
[79536.477075] pci_bus 6e53:00: root bus resource [mem 0xfe000-0xfe00f 
window]
[79536.477816] pci 6e53:00:02.0: [15b3:1016] type 00 class 0x02
[79536.491917] pci 6e53:00:02.0: reg 0x10: [mem 0xfe000-0xfe00f 64bit 
pref]
[79536.883663] pci 6e53:00:02.0: enabling Extended Tags
[79536.889425] pci 6e53:00:02.0: 0

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

[Hmpf]

Public bug reported:

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

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

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/1923670/+attachment/5487455/+files/version.log

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

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

Status in linux package in Ubuntu:
  New

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:
I

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

[Guilherme G. Piccoli]

I'm also taking a look in this one, I couldn't reproduce it (tried 11 times, 
with the same az-cli command-line provided by gjolly.
Found 2 interesting things after Gauthier provide me access to one of his 
failing instances:

(a) Regarding cloud-init, I see the following in the logs (comparing a
GOOD and BAD instance):

GOOD:
2021-04-13 19:19:09,341 - DataSourceAzure.py[DEBUG]: Retrieving public SSH keys
2021-04-13 19:19:09,341 - azure.py[DEBUG]: Unable to get keys from IMDS, 
falling back to OVF
2021-04-13 19:19:09,341 - DataSourceAzure.py[DEBUG]: Retrieved keys from OVF
2021-04-13 19:19:09,342 - handlers.py[DEBUG]: finish: 
azure-ds/get_public_ssh_keys: SUCCESS: get_public_ssh_keys
2021-04-13 19:19:09,342 - util.py[DEBUG]: Changing the ownership of 
/home/ubuntu/.ssh to 1000:1000
2021-04-13 19:19:09,343 - util.py[DEBUG]: Reading from /etc/ssh/sshd_config 
(quiet=False)
2021-04-13 19:19:09,343 - util.py[DEBUG]: Read 3287 bytes from 
/etc/ssh/sshd_config
2021-04-13 19:19:09,343 - util.py[DEBUG]: Writing to 
/home/ubuntu/.ssh/authorized_keys - wb: [600] 381 bytes
2021-04-13 19:19:09,343 - util.py[DEBUG]: Changing the ownership of 
/home/ubuntu/.ssh/authorized_keys to 1000:1000
2021-04-13 19:19:09,344 - util.py[DEBUG]: Changing the ownership of /root/.ssh 
to 0:0
2021-04-13 19:19:09,344 - util.py[DEBUG]: Reading from /etc/ssh/sshd_config 
(quiet=False)
2021-04-13 19:19:09,344 - util.py[DEBUG]: Read 3287 bytes from 
/etc/ssh/sshd_config
2021-04-13 19:19:09,344 - util.py[DEBUG]: Writing to /root/.ssh/authorized_keys 
- wb: [600] 545 bytes


BAD:
2021-04-12 08:25:07,412 - DataSourceAzure.py[DEBUG]: Retrieving public SSH keys
2021-04-12 08:25:07,412 - azure.py[DEBUG]: Unable to get keys from IMDS, 
falling back to OVF
2021-04-12 08:25:07,412 - azure.py[DEBUG]: No keys available from OVF
2021-04-12 08:25:07,412 - handlers.py[DEBUG]: finish: 
azure-ds/get_public_ssh_keys: SUCCESS: get_public_ssh_keys
2021-04-12 08:25:07,413 - util.py[DEBUG]: Changing the ownership of 
/home/ubuntu/.ssh to 1000:1000
2021-04-12 08:25:07,413 - util.py[DEBUG]: Reading from /etc/ssh/sshd_config 
(quiet=False)
2021-04-12 08:25:07,413 - util.py[DEBUG]: Read 3287 bytes from 
/etc/ssh/sshd_config
2021-04-12 08:25:07,414 - util.py[DEBUG]: Writing to 
/home/ubuntu/.ssh/authorized_keys - wb: [600] 0 bytes
2021-04-12 08:25:07,414 - util.py[DEBUG]: Changing the ownership of 
/home/ubuntu/.ssh/authorized_keys to 1000:1000
2021-04-12 08:25:07,414 - util.py[DEBUG]: Changing the ownership of /root/.ssh 
to 0:0
2021-04-12 08:25:07,414 - util.py[DEBUG]: Reading from /etc/ssh/sshd_config 
(quiet=False)
2021-04-12 08:25:07,415 - util.py[DEBUG]: Read 3287 bytes from 
/etc/ssh/sshd_config
2021-04-12 08:25:07,415 - util.py[DEBUG]: Writing to /root/.ssh/authorized_keys 
- wb: [600] 0 bytes

So, the main difference here is:

2021-04-13 19:19:09,341 - DataSourceAzure.py[DEBUG]: Retrieved keys from OVF
vs
2021-04-12 08:25:07,412 - azure.py[DEBUG]: No keys available from OVF

Why one method executes from DataSourceAzure.py whereas the other from azure.py?
I'm far from expert in cloud-init, so I'll defer that questions to cloud-init 
folks.

Will continue in next comment.

-- 
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 1923667] [NEW] Desktop shifted 1 pixel to the right when using full kms driver (Raspberry Pi 4B).

[fprietog]

Public bug reported:

- 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.

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

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

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

Status in linux-raspi package in Ubuntu:
  New

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 1902156] Re: [ASUS VivoBook X541UJ] Keyboard and touchpad don't work on kernel 5.8.0.29, but 5.4 or 5.8.16 work

[Gunnar Snorri Ragnarsson]

I have the same issues with 5.8.0-49 but not 5.8.0.48

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

Title:
  [ASUS VivoBook X541UJ] Keyboard and touchpad don't work on kernel
  5.8.0.29, but 5.4 or 5.8.16 work

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  when I updated my system to ubuntu 20.10, the keyboard and mouse no longer 
worked after a little investigation, I found out the kernel causes this 
problem, downgrading to linux 5.4 or upgrading to linux kernel 5.8.11 solved 
this issue, I also found that this problem is present on other ASUS laptop 
models ( my laptop is ASUS) so you may want to investigate this issue to update 
your default 20.10 Linux kernel.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joseph 1979 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-06-03 (515 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: ASUSTeK COMPUTER INC. X541UJ
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic 
root=UUID=1298f5d0-e6c0-4aa3-9c5a-fbe0ebf0fc02 ro quiet splash pci=noaer 
mds=full,nosmt vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-26-generic N/A
   linux-backports-modules-5.8.0-26-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-26-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/18/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541UJ.310
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541UJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541UJ.310:bd04/18/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X541UJ
  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/1902156/+subscriptions

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

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

[Ed Holden]

Ah, I missed that "b"! Unfortunately the 5.10.0 kernel the linux-
oem-20.04b package installs also doesn't fix it (same detection, same
dmesg log lines).

-- 
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 1922754] Re: Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output

[Alex Hung]

@matombo,

You will want to take a look at
https://wiki.ubuntu.com/KernelTeam/KernelUpdates for how to send SRUs to
Ubuntu kernel.

An example will be LP:1923000 (you can add SRU template to this bug),
cover page: https://lists.ubuntu.com/archives/kernel-
team/2021-April/119154.html & patch: https://lists.ubuntu.com/archives
/kernel-team/2021-April/119155.html

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

Title:
  Make AMD gpus choose YCbCr420 encoding automatically when required for
  4k 60Hz output

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On some setups, while the monitor and the gpu support display modes with
  pixel clocks of up to 600MHz, the link encoder might not. This prevents
  YCbCr444 and RGB encoding for 4k60Hz, but YCbCr420 encoding might still be
  possible. However, which color mode is used is decided before the link
  encoder capabilities are checked. This patch fixes the problem by retrying
  to find a display mode with YCbCr420 enforced and using it, if it is
  valid.

  Patch already got accepted upstream for linux-next:
  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=14e4a095b29fd290a9b80f6e553adcfcf01672d1 and
  applies without modifications to ubuntu-focal/hwe-5.8

  Commit-hash: 14e4a095b29fd290a9b80f6e553adcfcf01672d1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  test   2903 F pulseaudio
   /dev/snd/controlC0:  test   2903 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 20.04
  MachineType: TUXEDO TUXEDO Aura 15 Gen1
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=59a028a1-0764-418a-951d-515f1839bd7f ro ignore_loglevel quiet splash 
i8042.reset i8042.nomux i8042.nopnp i8042.noloop xhci_hcd.quirks=1073741824 
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.9
  Tags:  focal
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: AURA1501
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR2:bd11/13/2020:br7.3:svnTUXEDO:pnTUXEDOAura15Gen1:pvrNotApplicable:rvnTUXEDOComputers:rnAURA1501:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO Aura 15 Gen1
  dmi.product.sku: AURA1501
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

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

[Kernel-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi

[Sebastien Bacher]

Thanks!

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

Title:
  Bluez should notify users when they need to reboot to apply changes on
  Raspberry Pi

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  In the case of upgrading or installing bluez for the first time on
  certain raspberry pi devices, a reboot may be required to apply the
  changes. We should add a check for this scenario in the postinst
  script.

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

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

[Kernel-packages] [Bug 1905020] Re: [21.04 FEAT] Add kernel debug infos for decompressor stage to kernel-debug package

[Frank Heimes]

** Changed in: ubuntu-z-systems
   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/1905020

Title:
  [21.04 FEAT] Add kernel debug infos for decompressor stage to kernel-
  debug package

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  In order to be able to debug kernel crashes during the early decompressing 
phase, it would be useful to add the vmlinux file from the decompressor stage 
to the kernel-debug deb package.
  The file is located in arch/s390/boot/compressed/vmlinux.
  There are plans to make the kernel relocatable and move more things to the 
decompressor stage, which would be easier to debug in case of a problem if we 
have this file in the debug info package.

  Business Case:
  Increase problem determination / serviceability.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1905020/+subscriptions

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

[Kernel-packages] [Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration

[Frank Heimes]

** Changed in: ubuntu-power-systems
   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/1920784

Title:
  qemu-system-ppc64le fails with kvm acceleration

Status in The Ubuntu-power-systems project:
  Fix Released
Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Invalid
Status in glibc source package in Hirsute:
  Invalid
Status in linux source package in Hirsute:
  Fix Released
Status in qemu source package in Hirsute:
  Invalid

Bug description:
  (Suspected glibc issue!)

  qemu-system-ppc64(le) fails when invoked with kvm acceleration with
  error "illegal instruction"

  > qemu-system-ppc64(le) -M pseries,accel=kvm

  Illegal instruction (core dumped)

  In dmesg:

  Facility 'SCV' unavailable (12), exception at 0x7624f8134c0c,
  MSR=9280f033

  
  Version-Release number of selected component (if applicable):
  qemu 5.2.0 
  Linux kernel 5.11
  glibc 2.33
  all latest updates as of submitting the bug report

  How reproducible:
  Always

  Steps to Reproduce:
  1. Run qemu with kvm acceleration

  Actual results:
  Illegal instruction

  Expected results:
  Normal VM execution

  Additional info:
  The machine is a Raptor Talos II Lite with a Sforza V1 8-core, but was also 
observed on a Raptor Blackbird with the same processor.

  This was also observed on Fedora 34 beta, which uses glibc 2.33
  Also tested on ArchPOWER (unofficial port of Arch Linux for ppc64le) with 
glibc 2.33
  Fedora 33 and Ubuntu 20.10, both using glibc 2.32 do not have this issue, and 
downgrading the Linux kernel from 5.11 to 5.4 LTS on ArchPOWER solved the 
problem. Kernel 5.9 and 5.10 have the same issue when combined with glibc2.33

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: qemu-system 1:5.2+dfsg-6ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic ppc64le
  .sys.firmware.opal.msglog: Error: [Errno 13] Permission denied: 
'/sys/firmware/opal/msglog'
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: ppc64el
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Mar 22 14:48:39 2021
  InstallationDate: Installed on 2021-03-22 (0 days ago)
  InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Alpha ppc64el 
(20210321)
  KvmCmdLine: COMMAND STAT  EUID  RUID PIDPPID %CPU COMMAND
  ProcKernelCmdLine: root=UUID=f3d03315-0944-4a02-9c87-09c00eba9fa1 ro
  ProcLoadAvg: 1.20 0.73 0.46 1/1054 6071
  ProcSwaps:
   Filename TypeSizeUsed
Priority
   /swap.img   file 8388544 0   
-2
  ProcVersion: Linux version 5.11.0-11-generic (buildd@bos02-ppc64el-002) (gcc 
(Ubuntu 10.2.1-20ubuntu1) 10.2.1 20210220, GNU ld (GNU Binutils for Ubuntu) 
2.36.1) #12-Ubuntu SMP Mon Mar 1 19:26:20 UTC 2021
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  acpidump:
   
  cpu_cores: Number of cores present = 8
  cpu_coreson: Number of cores online = 8
  cpu_smt: SMT=4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1920784/+subscriptions

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

[Kernel-packages] [Bug 1920632] Re: use of Wacom stylus causes immediate system hang with kernel 5.8.0-45, but 5.8.0-44 works

[Jesko]

Today I updated the released to 5.8.0-49. I works perfectly now.

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

Title:
  use of Wacom stylus causes immediate system hang with kernel 5.8.0-45,
  but 5.8.0-44 works

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-5.8 package in Ubuntu:
  Fix Committed
Status in linux-signed-hwe-5.8 package in Ubuntu:
  Fix Committed

Bug description:
  Once updated kernel from 5.8.0-44 to 5.8.0.45, any use of Wacom stylus causes 
immediate system hang, frozen both GUI and OS. Removing the Wacom kernel module 
solves the problem (no more hangs, but the stylus is unusable then).
  Rolling back to kernel 5.8.0-44 or any earlier solves the problem.

  The OS is:  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 20 18:53:56 2021
  InstallationDate: Installed on 2020-04-24 (329 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1900438] Re: Bcache bypasse writeback on caching device with fragmentation

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1905020] Re: [21.04 FEAT] Add kernel debug infos for decompressor stage to kernel-debug package

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1915717] Re: [FEATURE] Hirsute: support TLS device offload for Bond

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1919930] Re: power off stress test will hang on the TGL machines

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1920030] Re: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1920874] Re: [Regression] Partition not removed after removing the memory cards from card reader since kernel 5.9.0-rc3+

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1921140] Re: Tegra "mmc0: Timeout waiting for hardware interrupt"

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1921710] Re: Hirsute update: v5.11.8 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1921712] Re: Hirsute update: v5.11.9 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1921757] Re: Fix mic on P620 after S3 resume

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1922033] Re: Enable ath11k debugfs/tracing

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1922171] Re: Handle Intel Wifi firmware disconnection

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1922207] Re: Microphone and Mute/Mic-mute LEDs are not work on HP 640 G8 Laptop

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1922372] Re: i915 doesn't support some high pixel clock 4k * 60Hz monitors

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1922600] Re: Hirsute update: v5.11.10 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1922601] Re: Hirsute update: v5.11.11 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1922768] Re: Update - Fix no screen show on display after S3 on CML-R

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1923069] Re: Hirsute update: v5.11.12 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1923104] Re: Include Infiniband Peer Memory interface

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.11.0-14.15

---
linux (5.11.0-14.15) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface

  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: usb-audio: Apply sample rate quirk to Logitech Connect
- ALSA: hda: Re-add dropped snd_poewr_change_state() calls
- ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks
- ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook
- xtensa: fix uaccess-related livelock in do_page_fault
- xtensa: move coprocessor_flush to 

[Kernel-packages] [Bug 1922403] Re: hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI

[Kai-Heng Feng]

https://lkml.org/lkml/2021/4/13/987

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

Title:
  hirsute beta desktop AMD64 ISO kernel panic on boot when booting using
  UEFI

Status in linux package in Ubuntu:
  In Progress

Bug description:
  I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64;
  http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso)
  inside a Hyper-V Gen 2 Virtual Machine with UEFI enabled.

  The GRUB boot menu loads, and I continue with the default option. I
  immediately get a kernel panic (screenshot attached).

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

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

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

[Kai-Heng Feng]

Should be "linux-oem-20.04b" instead of "linux-oem-20.04".

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1923638] [NEW] evdi/1.7.0+dfsg-1ubuntu2 ADT test failure with linux/5.11.0-14.15

[Seth Forshee]

Public bug reported:

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

Testing failed on:

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

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  evdi/1.7.0+dfsg-1ubuntu2 ADT test failure with linux/5.11.0-14.15

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

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

  Testing failed on:

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 1920916] Re: cold boot panics on unmatched board, soft reboot is fine

[Launchpad Bug Tracker]

This bug was fixed in the package linux-riscv - 5.11.0-1005.5

---
linux-riscv (5.11.0-1005.5) hirsute; urgency=medium

  * hirsute/linux-riscv: 5.11.0-1005.5 -proposed tracker (LP: #1923102)

  * Enable ath11k debugfs/tracing (LP: #1922033)
- [Config] enable ath11k debugfs/tracing

  * Miscellaneous Ubuntu changes
- [Packaging]: linux-image should suggest linux-modules-extra
- [Packaging]: linux-modules should depend on linux-image

  [ Ubuntu: 5.11.0-14.15 ]

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface
  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: u

[Kernel-packages] [Bug 1923564] Re: BlueZ 5.58 release

[Hans Joachim Desserud]

** Tags added: upgrade-software-version

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

Title:
  BlueZ 5.58 release

Status in bluez package in Ubuntu:
  New

Bug description:
  BlueZ 5.58 has been released. We should look at it for the 21.10
  cycle...

  http://www.bluez.org/release-of-bluez-5-58-and-5-57/
  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

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

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

[Tim Gardner]

gjolly - can you attach the whole /var/log/syslog soon after boot ? I
see the same pattern of link UP/DOWN/UP on a non-accelerated Hirsute
instance, but systemd correctly waits for networking to be configured in
this case.

-- 
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 1922582] Re: linux-azure: Enable CONFIG_FPGA_MGR_XILINX_SPI for Azure cloud kernel

[Tim Gardner]

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

** Changed in: linux-azure (Ubuntu Bionic)
   Status: In Progress => Invalid

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

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

Title:
  linux-azure: Enable CONFIG_FPGA_MGR_XILINX_SPI for Azure cloud kernel

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-4.15 package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  Fix Committed
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-azure-4.15 source package in Focal:
  Invalid
Status in linux-azure source package in Groovy:
  Fix Committed
Status in linux-azure-4.15 source package in Groovy:
  Invalid
Status in linux-azure source package in Hirsute:
  Fix Released
Status in linux-azure-4.15 source package in Hirsute:
  Invalid

Bug description:
  [SRU Justification]

  Microsoft Azure clouds support the use of a Xilinx FPGA to accelerate
  machine learning and other high performance tasks. The master kernels
  have had this option since the beginning. The lack of this option for
  Azure appears to have been an oversight.

  [Fix]
  Enable CONFIG_FPGA=m and CONFIG_FPGA_MGR_XILINX_SPI=m. Add these modules to 
the inclusion list.

  [Test Plan]
  modprobe xilinx-spi

  [Where problems could occur]
  The chances for regression are minimal as all additions are modules.

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

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

[Kernel-packages] [Bug 1863385] Re: System is generally unstable with amdgpu errors in syslog

[Lin Manfu]

I also have a 3400G with a freezing bug. Two questions to help establish
whether it's the same bug:

> The system has been crashing (no response to mouse/keyboard, but the
screen seems to still be updating).

When you say the screen is updating, what exactly do you mean, please?
My bug means the screen blanks to black, then returns to where it was
(or an earlier frame), and the mouse cursor moves. But actually, it's a
graphics crash: Clicking on buttons etc. has no effect and if I use the
keyboard to open a Terminal (Ctrl+Alt+T) and reboot, I get a response
about half the time. This is consistent with what I see in the SysLog,
which reports a series of amdgpu crashes and failed resets.

> I see a lot of junk in dmesg about amdgpu.

Are you seeing messages like these or something different, please?:

[drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences 
timed out!
Apr  5 01:12:11 paul kernel: [  285.638026] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* ring gfx timeout, signaled seq=92956, emitted seq=92958
Apr  5 01:12:11 paul kernel: [  285.638075] [drm:amdgpu_job_timedout [amdgpu]] 
*ERROR* Process information: process RLTM3.exe pid 3670 thread RLTM3.exe:cs0 
pid 3700
Apr  5 01:12:11 paul kernel: [  285.638078] amdgpu :27:00.0: amdgpu: GPU 
reset begin!

It might help you to know that many people with amdgpu bugs in Ryzen
report that setting the kernel parameter iommu=pt fixes them, though
this does not help me.

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

Title:
  System is generally unstable with amdgpu errors in syslog

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just set up a new computer to back up some files to a ZFS mirror on
  external USB3 drives.

  I'm booting off of NVMe, with four older sata hard drives installed
  internally (each with a single NTFS partition), and 3 external USB3
  drives (each set as part of a 3 way mirror in ZFS)

  Motherboard:AsRock X570 PRO4 AM4
  Processor: AMD Ryzen 5 3400G

  The system has been crashing (no response to mouse/keyboard, but the
  screen seems to still be updating).

  I see a lot of junk in dmesg about amdgpu.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cwal  17230 F pulseaudio
   /dev/snd/controlC0:  cwal  17230 F pulseaudio
  CurrentDesktop: LXQt
  Date: Fri Feb 14 17:10:33 2020
  InstallationDate: Installed on 2020-02-14 (0 days ago)
  InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono 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.3.0-18-generic 
root=UUID=8a1e698e-a3ba-4ae4-8bf8-811803447743 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: X570 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd09/10/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Pro4: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/1863385/+subscriptions

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

[Dimitri John Ledkov]

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

** Changed in: linux-azure (Ubuntu)
Milestone: None => ubuntu-21.04

-- 
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 1922582] Re: linux-azure: Enable CONFIG_FPGA_MGR_XILINX_SPI for Azure cloud kernel

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.11.0-1003.3

---
linux-azure (5.11.0-1003.3) hirsute; urgency=medium

  * hirsute/linux-azure: 5.11.0-1003.3 -proposed tracker (LP: #1923096)

  * linux-azure: Enable CONFIG_FPGA_MGR_XILINX_SPI for Azure cloud kernel
(LP: #1922582)
- [Config] azure: CONFIG_FPGA_MGR_XILINX_SPI=m

  * Miscellaneous Ubuntu changes
- [Config] annotations: updateconfigs following Ubuntu-5.11.0-14.15 rebase

  [ Ubuntu: 5.11.0-14.15 ]

  * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Include Infiniband Peer Memory interface (LP: #1923104)
- SAUCE: RDMA/core: Introduce peer memory interface
  * Hirsute update: v5.11.12 upstream stable release (LP: #1923069)
- arm64: mm: correct the inside linear map range during hotplug check
- virtiofs: Fail dax mount if device does not support it
- ext4: shrink race window in ext4_should_retry_alloc()
- ext4: fix bh ref count on error paths
- fs: nfsd: fix kconfig dependency warning for NFSD_V4
- rpc: fix NULL dereference on kmalloc failure
- iomap: Fix negative assignment to unsigned sis->pages in
  iomap_swapfile_activate
- ASoC: rt1015: fix i2c communication error
- ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
- ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on 
probe
- ASoC: es8316: Simplify adc_pga_gain_tlv table
- ASoC: soc-core: Prevent warning if no DMI table is present
- ASoC: cs42l42: Fix Bitclock polarity inversion
- ASoC: cs42l42: Fix channel width support
- ASoC: cs42l42: Fix mixer volume control
- ASoC: cs42l42: Always wait at least 3ms after reset
- NFSD: fix error handling in NFSv4.0 callbacks
- ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge
- kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing
- vhost: Fix vhost_vq_reset()
- io_uring: fix ->flags races by linked timeouts
- io_uring: halt SQO submission on ctx exit
- scsi: st: Fix a use after free in st_open()
- scsi: qla2xxx: Fix broken #endif placement
- staging: comedi: cb_pcidas: fix request_irq() warn
- staging: comedi: cb_pcidas64: fix request_irq() warn
- ASoC: rt5659: Update MCLK rate in set_sysclk()
- ASoC: rt711: add snd_soc_component remove callback
- thermal/core: Add NULL pointer check before using cooling device stats
- locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
- locking/ww_mutex: Fix acquire/release imbalance in
  ww_acquire_init()/ww_acquire_fini()
- nvmet-tcp: fix kmap leak when data digest in use
- io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls
- Revert "PM: ACPI: reboot: Use S5 for reboot"
- nouveau: Skip unvailable ttm page entries
- static_call: Align static_call_is_init() patching condition
- ext4: do not iput inode under running transaction in ext4_rename()
- io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with
  MSG_WAITALL
- net: mvpp2: fix interrupt mask/unmask skip condition
- mptcp: deliver ssk errors to msk
- mptcp: fix poll after shutdown
- mptcp: init mptcp request socket earlier
- mptcp: add a missing retransmission timer scheduling
- flow_dissector: fix TTL and TOS dissection on IPv4 fragments
- mptcp: fix DATA_FIN processing for orphaned sockets
- mptcp: provide subflow aware release function
- can: dev: move driver related infrastructure into separate subdir
- net: introduce CAN specific pointer in the struct net_device
- mptcp: fix race in release_cb
- net: bonding: fix error return code of bond_neigh_init()
- mptcp: fix bit MPTCP_PUSH_PENDING tests
- can: tcan4x5x: fix max register value
- brcmfmac: clear EAP/association status bits on linkdown events
- ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL
  pointer
- netdevsim: dev: Initialize FIB module after debugfs
- iwlwifi: pcie: don't disable interrupts for reg_lock
- ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()
- net: ethernet: aquantia: Handle error cleanup of start on open
- appletalk: Fix skb allocation size in loopback case
- net: ipa: remove two unused register definitions
- net: ipa: use a separate pointer for adjusted GSI memory
- net: ipa: fix register write command validation
- net: wan/lmc: unregister device when no matching device is found
- net: 9p: advance iov on empty read
- bpf: Remove MTU check in __bpf_skb_max_len
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
- ACPI: scan: Fix _STA getting called on devices with unmet dependencies
- ALSA: 

[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu

[Brian Murray]

** Changed in: u-boot (Ubuntu)
   Status: Confirmed => In Progress

** Also affects: u-boot (Ubuntu Hirsute)
   Importance: Critical
   Status: In Progress

** Also affects: u-boot-menu (Ubuntu Hirsute)
   Importance: Critical
   Status: Fix Released

** Also affects: linux-riscv (Ubuntu Hirsute)
   Importance: Undecided
   Status: Invalid

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

Title:
  riscv64 images fail to boot in qemu

Status in linux-riscv package in Ubuntu:
  Invalid
Status in u-boot package in Ubuntu:
  In Progress
Status in u-boot-menu package in Ubuntu:
  Fix Released
Status in linux-riscv source package in Hirsute:
  Invalid
Status in u-boot source package in Hirsute:
  In Progress
Status in u-boot-menu source package in Hirsute:
  Fix Released

Bug description:
  When booting v5.11 based riscv unmatched image in qemu with uboot, it
  fails to boot.

  When booting v5.11 based riscv unmatched kernel+initrd directly, it
  boots fine.

  Somehow, it seems that u-boot fails to correctly load & start v5.11
  kernel.

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

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

[Kernel-packages] [Bug 1919308] Re: sometimes unable to play media like music or youtube etc.

[Dennis Eyke]

** Summary changed:

- sometimes unable to play media like youtube
+ sometimes unable to play media like music or youtube etc.

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

Title:
  sometimes unable to play media like music or youtube etc.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  after my updated linux kernel 5.4.0-67 If I open Youtube and want to play a 
video, the video stops over and over again. Furthermore it plays with very 
often stops in between.
  The audio is flickering too.
  I tried Firefox, Brave and Celludoid. It need to be a kernel issue, because 
of the last update I did.
  Old kernel I used: 5.4.0-60 : there works everything fine!

  Problem filmed:
  
https://drive.google.com/drive/folders/1qU1MUJvGro-StN3mnt4cJvP-H2A2Uo2O?usp=sharing

  
  System:
Kernel: 5.4.0-67-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 
Distro: Linux Mint 20.1 Ulyssa 
  Machine:
Type: Desktop System: Gigabyte product: X570 AORUS ULTRA v: -CF 
serial:  
Mobo: Gigabyte model: X570 AORUS ULTRA v: x.x serial:  
UEFI: American Megatrends v: F30a date: 08/28/2020 
  CPU:
Topology: 16-Core (2-Die) model: AMD Ryzen 9 3950X bits: 64 
type: MT MCP MCM L2 cache: 8192 KiB 
Speed: 2777 MHz min/max: 2200/3500 MHz Core speeds (MHz): 1: 2195 2: 2192 
3: 2793 4: 2794 5: 2195 6: 2192 7: 2196 8: 2196 9: 2193 10: 2195 11: 2192 
12: 2193 13: 2196 14: 2196 15: 2193 16: 2196 17: 2191 18: 1863 19: 1859 
20: 2789 21: 2792 22: 2196 23: 2193 24: 2195 25: 2196 26: 2194 27: 2193 
28: 2195 29: 2196 30: 2191 31: 1862 32: 1859 
  Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2060] driver: nvidia v: 460.39 
Display: x11 server: X.Org 1.20.9 driver: nvidia 
unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz 
OpenGL: renderer: GeForce RTX 2060/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39 
  Audio:
Device-1: NVIDIA TU104 HD Audio driver: snd_hda_intel 
Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel 
Sound Server: ALSA v: k5.4.0-67-generic 
  Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi 
IF: wlp4s0 state: up mac:  
Device-2: Intel I211 Gigabit Network driver: igb 
IF: enp5s0 state: down mac:  
  Drives:
Local Storage: total: 1.36 TiB used: 890.85 GiB (63.8%) 
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB 
size: 465.76 GiB 
ID-2: /dev/sda vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB 
  Partition:
ID-1: / size: 456.96 GiB used: 208.47 GiB (45.6%) fs: ext4 
dev: /dev/nvme0n1p2 
  Sensors:
System Temperatures: cpu: 43.0 C mobo: N/A gpu: nvidia temp: 27 C 
Fan Speeds (RPM): N/A gpu: nvidia fan: 38% 
  Info:
Processes: 524 Uptime: 9m Memory: 62.82 GiB used: 2.34 GiB (3.7%) 
Shell: bash inxi: 3.0.38 

  Kind regards
  Dennis
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1721 F pulseaudio
   /dev/snd/controlC1:  dennis 1721 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic 
root=UUID=3d4d7c9d-8bb8-4200-997d-98d01519bf85 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
  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
  Tags:  ulyssa
  Uname: Linux 5.4.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/28/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F30a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  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.:bvrF30a:bd08/28/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis

[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu

[Dimitri John Ledkov]

So the issue around providing fdtdir was that qemu did not know what fdt
file to attempt loading, and hence was failing to boot.

Now that we dropped fdtdir in extlinux.conf, all riscv64 boards need to
use preboot to pick up fdt from the .itb. This was already the case on
unleashed and smode, but not on unmatched.

Add USE_PREBOOT config option to unmatched too, thus bringing it inline
with unleashed & qemu.

** Changed in: u-boot (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: u-boot (Ubuntu)
   Importance: Low => Critical

** Changed in: u-boot (Ubuntu)
Milestone: None => ubuntu-21.04

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

Title:
  riscv64 images fail to boot in qemu

Status in linux-riscv package in Ubuntu:
  Invalid
Status in u-boot package in Ubuntu:
  Confirmed
Status in u-boot-menu package in Ubuntu:
  Fix Released

Bug description:
  When booting v5.11 based riscv unmatched image in qemu with uboot, it
  fails to boot.

  When booting v5.11 based riscv unmatched kernel+initrd directly, it
  boots fine.

  Somehow, it seems that u-boot fails to correctly load & start v5.11
  kernel.

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

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

[Kernel-packages] [Bug 1922582] Re: linux-azure: Enable CONFIG_FPGA_MGR_XILINX_SPI for Azure cloud kernel

[Tim Gardner]

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

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

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

** Changed in: linux-azure-4.15 (Ubuntu Bionic)
   Status: New => Fix Committed

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

** Changed in: linux-azure-4.15 (Ubuntu Groovy)
   Status: New => Invalid

** Changed in: linux-azure-4.15 (Ubuntu Hirsute)
   Status: New => Invalid

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

Title:
  linux-azure: Enable CONFIG_FPGA_MGR_XILINX_SPI for Azure cloud kernel

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure-4.15 package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  In Progress
Status in linux-azure-4.15 source package in Bionic:
  Fix Committed
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure-4.15 source package in Focal:
  Invalid
Status in linux-azure source package in Groovy:
  In Progress
Status in linux-azure-4.15 source package in Groovy:
  Invalid
Status in linux-azure source package in Hirsute:
  In Progress
Status in linux-azure-4.15 source package in Hirsute:
  Invalid

Bug description:
  [SRU Justification]

  Microsoft Azure clouds support the use of a Xilinx FPGA to accelerate
  machine learning and other high performance tasks. The master kernels
  have had this option since the beginning. The lack of this option for
  Azure appears to have been an oversight.

  [Fix]
  Enable CONFIG_FPGA=m and CONFIG_FPGA_MGR_XILINX_SPI=m. Add these modules to 
the inclusion list.

  [Test Plan]
  modprobe xilinx-spi

  [Where problems could occur]
  The chances for regression are minimal as all additions are modules.

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

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

Re: [Kernel-packages] [Bug 1923390] Re: NVidia driver 460 doesn't work after updating to proposed kernel 5.11.0-14.15-generic

[Chris Hermansen]

Sorry I forgot to mention that...

After the boot where the screen resolution was messed up, I tried:

1. The recovery boot (nothing improved)
2. Installing the NVidia driver manually (terminated with error, no
improvement)
3. Apt purge (resolution back to 1920 x 1080, seemingly ok)

 So just to be completely clear, the failed install of the NVidia driver
was an attempt to repair the problem that had already happened.

Again sorry for the confusion!

On Tue, Apr 13, 2021, 01:50 Daniel van Vugt <1923...@bugs.launchpad.net>
wrote:

> Chris,
>
> Please only install NVIDIA drivers from the 'Additional Drivers' app in
> future. If you install drivers from elsewhere then that's unsupported
> and can cause bugs which we can't fix.
>
> To recover in this case you will need to figure out how to fully
> *uninstall* the manually installed driver, and then reinstall using the
> 'Additional Drivers' app.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1923390
>
> Title:
>   NVidia driver 460 doesn't work after updating to proposed kernel
>   5.11.0-14.15-generic
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923390/+subscriptions
>

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

Title:
  NVidia driver 460 doesn't work after updating to proposed kernel
  5.11.0-14.15-generic

Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Invalid

Bug description:
  Saturday night at about 03:00 UTC I noticed that an update to my
  system (Hirsute / 21.04) would no longer properly work with my NVidia
  RTX 3060; I was left in very low resolution mode.  When I ran
  Additional Drivers, the screen indicated that I had manually installed
  graphics drivers and I could not select the official and tested NVidia
  drivers.  I am assuming these "manually" installed drivers were a part
  of a system update as I did nothing to install any drivers on my own.

  I found a suggestion to run "apt purge nvdia-\*", which I did.  When I
  rebooted, I was able to select the "Using NVIDIA driver metapackage
  from nvidia-driver-460 (proprietary,tested), and my screen resolution
  and general behaviour seemed fine from that point on.

  In case it doesn't come through in the uploaded files, here are the
  lines from /var/log/dpkg.log relating to my purge:

  2021-04-10 20:28:09 startup packages purge
  2021-04-10 20:28:09 purge nvidia-compute-utils-460:amd64 460.67-0ubuntu1 

  2021-04-10 20:28:09 status config-files nvidia-compute-utils-460:amd64 
460.67-0ubuntu1
  2021-04-10 20:28:09 status not-installed nvidia-compute-utils-460:amd64 
  2021-04-10 20:28:09 purge nvidia-prime:all 0.8.16.1 
  2021-04-10 20:28:09 status config-files nvidia-prime:all 0.8.16.1
  2021-04-10 20:28:09 status not-installed nvidia-prime:all 
  2021-04-10 20:28:09 purge nvidia-kernel-common-460:amd64 460.67-0ubuntu1 

  2021-04-10 20:28:09 status config-files nvidia-kernel-common-460:amd64 
460.67-0ubuntu1
  2021-04-10 20:28:09 status triggers-pending initramfs-tools:all 0.139ubuntu3
  2021-04-10 20:28:09 status not-installed nvidia-kernel-common-460:amd64 
  2021-04-10 20:28:09 purge linux-modules-nvidia-460-5.11.0-13-generic:amd64 
5.11.0-13.14+2 
  2021-04-10 20:28:09 status config-files 
linux-modules-nvidia-460-5.11.0-13-generic:amd64 5.11.0-13.14+2
  2021-04-10 20:28:10 status not-installed 
linux-modules-nvidia-460-5.11.0-13-generic:amd64 
  2021-04-10 20:28:10 purge nvidia-settings:amd64 460.56-0ubuntu2 
  2021-04-10 20:28:10 status config-files nvidia-settings:amd64 460.56-0ubuntu2
  2021-04-10 20:28:10 status not-installed nvidia-settings:amd64 

  Note the time shown is Vancouver/Canada Pacific Daylight.

  It may be worth mentioning that nouveau doesn't recognize the RTX 3060
  (I understand that this is a very recently released video card).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:  gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
  App

[Kernel-packages] [Bug 1917203] Re: [PATCH 2/2] iommu/amd: Remove performance counter pre-initialization test

[Suravee Suthikulpanit]

On 4/10/2021 5:03 PM, David Coe wrote:
> Results for AMD Ryzen 4700U running Ubuntu 21.04β kernel 5.11.0-13
> 
> $ sudo dmesg | grep IOMMU
> [    0.490352] pci :00:00.2: AMD-Vi: IOMMU performance counters supported
> [    0.491985] pci :00:00.2: AMD-Vi: Found IOMMU cap 0x40
> [    0.493732] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 
> counters/bank).
> [    0.793259] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel 
> 
> 
> 
> $ sudo perf stat -e 'amd_iommu_0/cmd_processed/, 
> amd_iommu_0/cmd_processed_inv/, amd_iommu_0/ign_rd_wr_mmio_1ff8h/, 
> amd_iommu_0/int_dte_hit/, amd_iommu_0/int_dte_mis/, amd_iommu_0/mem_dte_hit/, 
> amd_iommu_0/mem_dte_mis/, amd_iommu_0/mem_iommu_tlb_pde_hit/, 
> amd_iommu_0/mem_iommu_tlb_pde_mis/, amd_iommu_0/mem_iommu_tlb_pte_hit/, 
> amd_iommu_0/mem_iommu_tlb_pte_mis/, amd_iommu_0/mem_pass_excl/, 
> amd_iommu_0/mem_pass_pretrans/, amd_iommu_0/mem_pass_untrans/, 
> amd_iommu_0/mem_target_abort/, 
> amd_iommu_0/mem_trans_total/, amd_iommu_0/page_tbl_read_gst/, 
> amd_iommu_0/page_tbl_read_nst/, amd_iommu_0/page_tbl_read_tot/, 
> amd_iommu_0/smi_blk/, amd_iommu_0/smi_recv/, amd_iommu_0/tlb_inv/, 
> amd_iommu_0/vapic_int_guest/, amd_iommu_0/vapic_int_non_guest/' sleep 10
> 
> Performance counter stats for 'system wide':
> 
>     12  amd_iommu_0/cmd_processed/ (33.28%)
>      6   amd_iommu_0/cmd_processed_inv/    (33.32%)
>      0   amd_iommu_0/ign_rd_wr_mmio_1ff8h/ (33.36%)
>    290   amd_iommu_0/int_dte_hit/  (33.40%)
>     20   amd_iommu_0/int_dte_mis/  (33.46%)
>    391   amd_iommu_0/mem_dte_hit/  (33.49%)
>      3,720   amd_iommu_0/mem_dte_mis/  (33.49%)
>     44   amd_iommu_0/mem_iommu_tlb_pde_hit/    (33.46%)
>    810   amd_iommu_0/mem_iommu_tlb_pde_mis/    (33.45%)
>     35   amd_iommu_0/mem_iommu_tlb_pte_hit/    (33.41%)
>    746   amd_iommu_0/mem_iommu_tlb_pte_mis/    (33.37%)
>      0   amd_iommu_0/mem_pass_excl/    (33.32%)
>      0   amd_iommu_0/mem_pass_pretrans/    (33.28%)
>      0   amd_iommu_0/mem_pass_untrans/ (33.28%)
>      0   amd_iommu_0/mem_target_abort/ (33.27%)
>    715   amd_iommu_0/mem_trans_total/  (33.27%)
>      0   amd_iommu_0/page_tbl_read_gst/    (33.28%)
>     36   amd_iommu_0/page_tbl_read_nst/    (33.27%)
>     36   amd_iommu_0/page_tbl_read_tot/    (33.27%)
>      0   amd_iommu_0/smi_blk/  (33.28%)
>      0   amd_iommu_0/smi_recv/ (33.26%)
>      0   amd_iommu_0/tlb_inv/  (33.23%)
>      0   amd_iommu_0/vapic_int_guest/  (33.24%)
>    366   amd_iommu_0/vapic_int_non_guest/  (33.27%)
> 
> The immediately obvious difference is the with the enormous count seen on 
> mem_dte_mis on the older Ryzen 2400G. Will do some RTFM but anyone with 
> comments and insight?
> 
> 841,689,151,202,939   amd_iommu_0/mem_dte_mis/  (33.44%)
> 
> Otherwise, all seems to running smoothly (especially for a distribution still 
> in β). Bravo and many thanks all!
> 
That doesn't look correct. Lemme do some more investigation also.

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

[Kernel-packages] [Bug 1921769] Re: Backport mlx5e fix for tunnel offload

[Naadir Jeewa]

Follow up comments, albeit a bit late.

The test PPA kernel did resolve the issue for us, and can confirm that
our 18.04 images were using the 5.4 kernel.

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

Title:
  Backport mlx5e fix for tunnel offload

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-azure source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-azure source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in linux-azure source package in Groovy:
  Confirmed
Status in linux source package in Hirsute:
  Fix Released
Status in linux-azure source package in Hirsute:
  Confirmed

Bug description:
  [SRU Justification]

  We've discovered an issue on Ubuntu 20.04 when used with Kubernetes
  CNIs that perform offloading using Geneve that causes the kernel to
  panic on Azure instances with accelerated networking with the
  following errors:

  [ 307.561223] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x200, ci 
0x3d4, sqn 0x2c5, opcode 0xd, syndrome 0x2, vendor syndrome 0x68
  [ 307.573864] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2c5
  [ 307.764902] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x200, ci 
0x3d7, sqn 0x2c5, opcode 0xd, syndrome 0x2, vendor syndrome 0x68
  [ 307.777332] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2c5
  [ 322.814393] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x218, ci 
0x1a7, sqn 0x2bd, opcode 0xd, syndrome 0x2, vendor syndrome 0x68
  [ 322.826685] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2bd

  NVIDIA fixed this issue in
  
https://github.com/torvalds/linux/commit/5ccc0ecda9e8a67add654d93d7e0ac4346c0fa22
  , so we're looking to have this backported to at least the linux-azure
  package.

  [Test Plan]
  Spin up a Kubernetes CNI that uses Geneve offloading

  [Where problems could occur]
  Its possible some traffic won't get geneve acceleration. This patch has been 
backported to v5.10.y and v5.11.y

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

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

[Kernel-packages] [Bug 1921769] Re: Backport mlx5e fix for tunnel offload

[Tim Gardner]

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

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

Title:
  Backport mlx5e fix for tunnel offload

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-azure source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-azure source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in linux-azure source package in Groovy:
  Confirmed
Status in linux source package in Hirsute:
  Fix Released
Status in linux-azure source package in Hirsute:
  Confirmed

Bug description:
  [SRU Justification]

  We've discovered an issue on Ubuntu 20.04 when used with Kubernetes
  CNIs that perform offloading using Geneve that causes the kernel to
  panic on Azure instances with accelerated networking with the
  following errors:

  [ 307.561223] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x200, ci 
0x3d4, sqn 0x2c5, opcode 0xd, syndrome 0x2, vendor syndrome 0x68
  [ 307.573864] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2c5
  [ 307.764902] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x200, ci 
0x3d7, sqn 0x2c5, opcode 0xd, syndrome 0x2, vendor syndrome 0x68
  [ 307.777332] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2c5
  [ 322.814393] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x218, ci 
0x1a7, sqn 0x2bd, opcode 0xd, syndrome 0x2, vendor syndrome 0x68
  [ 322.826685] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2bd

  NVIDIA fixed this issue in
  
https://github.com/torvalds/linux/commit/5ccc0ecda9e8a67add654d93d7e0ac4346c0fa22
  , so we're looking to have this backported to at least the linux-azure
  package.

  [Test Plan]
  Spin up a Kubernetes CNI that uses Geneve offloading

  [Where problems could occur]
  Its possible some traffic won't get geneve acceleration. This patch has been 
backported to v5.10.y and v5.11.y

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

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

[Ioanna Alifieraki]

This bug also affects Bionic when 5.4 hwe kernel is used.

** Description changed:

  [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
  [PATCH] arm64: Add support for ARMv8.2-LPA (52-bit PA support)
+ 
+ This bug also affects Bionic when 5.4 hwe kernel is used.

-- 
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 i

[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.

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

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

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

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

[Kernel-packages] [Bug 1913633] Re: nvidia-graphics-drivers-460 causes vlc to crash when taking video snapshot

[Ciro Santilli 六四事件 法轮功]

I'm on Ubuntu 20.10, default desktop, nvidia-driver-460, Quadro M1200
GPU, and VLC also crashes for me whenever I try to take a snapshot.

However, I don't get the gl information logs mentioned by OP, is just
says "segmentation fault".

I tried reverting to 450, and it still segfaults.

The `--verbose 2` messages corresponding to me clicking the take
snapshot button in both cases are:

```
[7f23600013b0] main vout display debug: VoutDisplayEvent 'mouse button' 2 
t=6
[7f23600013b0] main vout display debug: VoutDisplayEvent 'mouse button' 2 
t=7
[7f23600013b0] main vout display debug: auto hiding mouse cursor
[55c87ad2f7e0] pulse audio output debug: suspended
[55c87ad2f7e0] pulse audio output debug: changing sink 0: 
alsa_output.pci-_00_1f.3.analog-stereo (Built-in Audio Analogue Stereo)
[7f23a40c2d80] main encoder debug: looking for encoder module matching 
"any": 21 candidates
[7f23a40c2d80] main encoder debug: using encoder module "png"
[7f23a4708060] main filter debug: looking for video converter module 
matching "any": 23 candidates
[7f23a4708060] swscale filter debug: 1280x720 (1280x736) chroma: I420 -> 
1280x720 (1280x720) chroma: RV24 with scaling using Bicubic (good quality)
[7f23a4708060] main filter debug: using video converter module "swscale"
Segmentation fault (core dumped)
```

Also like OP mentioned, PrtSc does not work on full screen. Outside of
full screen it works.

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

Title:
  nvidia-graphics-drivers-460 causes vlc to crash when taking video
  snapshot

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

Bug description:
  vlc 3.0.11.1-2 would happily take video snapshots with version 450
  (and earlier) of the drivers, but crashes instantly every time with
  460.

  me@mine ~$ vlc
  VLC media player 3.0.11.1 Vetinari (revision 3.0.11.1-0-g52483f3ca2)
  [55acea1745b0] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  [55acea213580] main playlist: playlist is empty
  (** attempt to take snapshot via GUI **)
  libEGL warning: DRI2: failed to authenticate
  [7f7f840045f0] gl gl: Initialized libplacebo v2.72.0 (API v72)
  [7f7f840045f0] glx gl error: cannot create GLX context
  libEGL warning: DRI2: failed to authenticate
  [7f7f840045f0] gles2 gl: Initialized libplacebo v2.72.0 (API v72)
  libEGL warning: DRI2: failed to authenticate
  [7f7f840045f0] gl gl: Initialized libplacebo v2.72.0 (API v72)
  Segmentation fault (core dumped)

  Using PrtSc to get a screenshot works, but doesn't capture the video
  shown in the vlc window.

  Ubuntu MATE 20.10, kernel 5.8.0-41-generic.
  nvidia-driver-460 460.32.03-0ubuntu0.20.10.1

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

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

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

[Ed Holden]

Thanks, Kai-Heng. I've installed linux-oem-20.04 and selected the new
kernel, 5.6.0-1052-oem, on boot. Unfortunately the behavior is
identical. The mouse still appears as "PS/2 Logitech Wheel Mouse" with
all the same information (e.g., event3 in xinput). I checked dmesg and
the four lines you identified are still there with the OEM kernel:

[0.846922] i2c_designware i2c_designware.1: i2c_dw_handle_tx_abort: lost 
arbitration
[0.846960] i2c_designware i2c_designware.1: i2c_dw_handle_tx_abort: lost 
arbitration
[0.846997] i2c_designware i2c_designware.1: i2c_dw_handle_tx_abort: lost 
arbitration
[0.847034] i2c_designware i2c_designware.1: i2c_dw_handle_tx_abort: lost 
arbitration

-- 
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 1923609] Re: Couldn't change to nvidia driver package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460 package post-installation scri

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

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

Bug description:
  Fresh install of Ubuntu 20.04 with a kernel upgrade to 5.12.x (for
  wifi driver). Nvidia card (3070) was not being detected by the system.
  Attempted to switch from the mesa driver to the Nvidia proprietary
  driver.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-460 460.39-0ubuntu0.20.04.1
  Uname: Linux 5.12.0-051200rc7-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 13 08:18:42 2021
  ErrorMessage: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2021-04-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: nvidia-graphics-drivers-460
  Title: package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1923609] [NEW] Couldn't change to nvidia driver package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460 package post-installation sc

[Ethan Plummer]

Public bug reported:

Fresh install of Ubuntu 20.04 with a kernel upgrade to 5.12.x (for wifi
driver). Nvidia card (3070) was not being detected by the system.
Attempted to switch from the mesa driver to the Nvidia proprietary
driver.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-460 460.39-0ubuntu0.20.04.1
Uname: Linux 5.12.0-051200rc7-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Apr 13 08:18:42 2021
ErrorMessage: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2021-04-13 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: nvidia-graphics-drivers-460
Title: package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

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

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

Bug description:
  Fresh install of Ubuntu 20.04 with a kernel upgrade to 5.12.x (for
  wifi driver). Nvidia card (3070) was not being detected by the system.
  Attempted to switch from the mesa driver to the Nvidia proprietary
  driver.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-460 460.39-0ubuntu0.20.04.1
  Uname: Linux 5.12.0-051200rc7-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 13 08:18:42 2021
  ErrorMessage: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2021-04-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: nvidia-graphics-drivers-460
  Title: package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1922350] Re: missing firmware reported when updating initramfs

[You-Sheng Yang]

bionic: https://lists.ubuntu.com/archives/kernel-
team/2021-April/119192.html

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

Title:
  missing firmware reported when updating initramfs

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-firmware source package in Groovy:
  In Progress
Status in linux-firmware source package in Hirsute:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Some kernel firmwares might be landed after linux-firmware forked for
  each series, or for LTS series, kernels of new versions may claim
  additional ones that were not previously available. This leaves devices
  fail to function correctly while they ought to.

  With a checking script that enumerates all the blobs available in
  upstream repo and in the Ubuntu fork of a given series, e.g. hirsute,
  iterate through all the installed kernel modules of a given version to
  check if claimed firmware blobs are available in Ubuntu's fork.
  Following kernel version/series have been checked:

* 5.11.0-14-generic/hirsute
* 5.8.0-48-generic/groovy
* 5.4.0-70-generic/focal
* 5.6.0-1052-oem/focal
* 5.8.0-48-generic/focal
* 5.10.0-1019-oem/focal
* 4.15.0-140-generic/bionic
* 4.18.0-25-generic/bionic
* 5.0.0-65-generic/bionic
* 5.4.0-70-generic/bionic

  And it gives following files were missing in at least one of above
  cases:

* amdgpu/arcturus_asd.bin
* amdgpu/arcturus_gpu_info.bin
* amdgpu/arcturus_mec.bin
* amdgpu/arcturus_mec2.bin
* amdgpu/arcturus_rlc.bin
* amdgpu/arcturus_sdma.bin
* amdgpu/arcturus_smc.bin
* amdgpu/arcturus_sos.bin
* amdgpu/arcturus_ta.bin
* amdgpu/arcturus_vcn.bin
* amdgpu/navi12_asd.bin
* amdgpu/navi12_ce.bin
* amdgpu/navi12_dmcu.bin
* amdgpu/navi12_gpu_info.bin
* amdgpu/navi12_me.bin
* amdgpu/navi12_mec.bin
* amdgpu/navi12_mec2.bin
* amdgpu/navi12_pfp.bin
* amdgpu/navi12_rlc.bin
* amdgpu/navi12_sdma.bin
* amdgpu/navi12_sdma1.bin
* amdgpu/navi12_smc.bin
* amdgpu/navi12_sos.bin
* amdgpu/navi12_ta.bin
* amdgpu/navi12_vcn.bin
* amdgpu/navy_flounder_ce.bin
* amdgpu/navy_flounder_dmcub.bin
* amdgpu/navy_flounder_me.bin
* amdgpu/navy_flounder_mec.bin
* amdgpu/navy_flounder_mec2.bin
* amdgpu/navy_flounder_pfp.bin
* amdgpu/navy_flounder_rlc.bin
* amdgpu/navy_flounder_sdma.bin
* amdgpu/navy_flounder_smc.bin
* amdgpu/navy_flounder_sos.bin
* amdgpu/navy_flounder_ta.bin
* amdgpu/navy_flounder_vcn.bin
* amdgpu/oland_uvd.bin
* amdgpu/pitcairn_uvd.bin
* amdgpu/renoir_asd.bin
* amdgpu/renoir_ce.bin
* amdgpu/renoir_gpu_info.bin
* amdgpu/renoir_me.bin
* amdgpu/renoir_mec.bin
* amdgpu/renoir_mec2.bin
* amdgpu/renoir_pfp.bin
* amdgpu/renoir_rlc.bin
* amdgpu/renoir_sdma.bin
* amdgpu/renoir_ta.bin
* amdgpu/renoir_vcn.bin
* amdgpu/sienna_cichlid_ce.bin
* amdgpu/sienna_cichlid_dmcub.bin
* amdgpu/sienna_cichlid_me.bin
* amdgpu/sienna_cichlid_mec.bin
* amdgpu/sienna_cichlid_mec2.bin
* amdgpu/sienna_cichlid_pfp.bin
* amdgpu/sienna_cichlid_rlc.bin
* amdgpu/sienna_cichlid_sdma.bin
* amdgpu/sienna_cichlid_smc.bin
* amdgpu/sienna_cichlid_sos.bin
* amdgpu/sienna_cichlid_ta.bin
* amdgpu/sienna_cichlid_vcn.bin
* amdgpu/tahiti_uvd.bin
* amdgpu/vega20_ta.bin
* amdgpu/verde_uvd.bin
* atmel/wilc1000_wifi_firmware-1.bin
* cmmb_vega_12mhz.inp
* cmmb_venice_12mhz.inp
* dvb_nova_12mhz.inp
* dvb_nova_12mhz_b0.inp
* i915/bxt_guc_33.0.0.bin
* i915/glk_guc_33.0.0.bin
* i915/icl_guc_33.0.0.bin
* i915/kbl_guc_33.0.0.bin
* i915/skl_guc_33.0.0.bin
* i915/tgl_dmc_ver2_04.bin
* i915/tgl_huc_7.5.0.bin
* isdbt_nova_12mhz.inp
* isdbt_nova_12mhz_b0.inp
* isdbt_rio.inp
* iwlwifi-Qu-b0-hr-b0-59.ucode
* iwlwifi-Qu-b0-jf-b0-50.ucode
* iwlwifi-Qu-b0-jf-b0-59.ucode
* iwlwifi-Qu-c0-hr-b0-50.ucode
* iwlwifi-Qu-c0-hr-b0-59.ucode
* iwlwifi-QuZ-a0-hr-b0-50.ucode
* iwlwifi-QuZ-a0-hr-b0-59.ucode
* iwlwifi-QuZ-a0-jf-b0-50.ucode
* iwlwifi-QuZ-a0-jf-b0-59.ucode
* iwlwifi-cc-a0-50.ucode
* iwlwifi-cc-a0-59.ucode
* mediatek/mt7663pr2h.bin
* mellanox/mlxsw_spectrum-13.2000.1886.mfa2
* mellanox/mlxsw_spectrum-13.2008.1310.mfa2
* mellanox/mlxsw_spectrum2-29.2008.1310.mfa2
* mellanox/mlxsw_spectrum3-30.2008.1310.mfa2
* mrvl/sdsd8977_combo_v2.bin
* mrvl/sdsd8997_combo_v4.bin
* rtl_nic/rtl8125a-3.fw
* rtl_nic/rtl8168fp-3.fw
* rtw88/rtw8822c_wow_fw.bin
* sms1xxx-hcw-55xxx-dvbt-02.fw
* sms1xxx-hcw-55xxx-isdbt-02.fw
* sms1xxx

[Kernel-packages] [Bug 1922350] Re: missing firmware reported when updating initramfs

[You-Sheng Yang]

SRU:
* hirsute: https://lists.ubuntu.com/archives/kernel-team/2021-April/119170.html
* groovy:  https://lists.ubuntu.com/archives/kernel-team/2021-April/119172.html
* focal:   https://lists.ubuntu.com/archives/kernel-team/2021-April/119175.html

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

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

Title:
  missing firmware reported when updating initramfs

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-firmware source package in Groovy:
  In Progress
Status in linux-firmware source package in Hirsute:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Some kernel firmwares might be landed after linux-firmware forked for
  each series, or for LTS series, kernels of new versions may claim
  additional ones that were not previously available. This leaves devices
  fail to function correctly while they ought to.

  With a checking script that enumerates all the blobs available in
  upstream repo and in the Ubuntu fork of a given series, e.g. hirsute,
  iterate through all the installed kernel modules of a given version to
  check if claimed firmware blobs are available in Ubuntu's fork.
  Following kernel version/series have been checked:

* 5.11.0-14-generic/hirsute
* 5.8.0-48-generic/groovy
* 5.4.0-70-generic/focal
* 5.6.0-1052-oem/focal
* 5.8.0-48-generic/focal
* 5.10.0-1019-oem/focal
* 4.15.0-140-generic/bionic
* 4.18.0-25-generic/bionic
* 5.0.0-65-generic/bionic
* 5.4.0-70-generic/bionic

  And it gives following files were missing in at least one of above
  cases:

* amdgpu/arcturus_asd.bin
* amdgpu/arcturus_gpu_info.bin
* amdgpu/arcturus_mec.bin
* amdgpu/arcturus_mec2.bin
* amdgpu/arcturus_rlc.bin
* amdgpu/arcturus_sdma.bin
* amdgpu/arcturus_smc.bin
* amdgpu/arcturus_sos.bin
* amdgpu/arcturus_ta.bin
* amdgpu/arcturus_vcn.bin
* amdgpu/navi12_asd.bin
* amdgpu/navi12_ce.bin
* amdgpu/navi12_dmcu.bin
* amdgpu/navi12_gpu_info.bin
* amdgpu/navi12_me.bin
* amdgpu/navi12_mec.bin
* amdgpu/navi12_mec2.bin
* amdgpu/navi12_pfp.bin
* amdgpu/navi12_rlc.bin
* amdgpu/navi12_sdma.bin
* amdgpu/navi12_sdma1.bin
* amdgpu/navi12_smc.bin
* amdgpu/navi12_sos.bin
* amdgpu/navi12_ta.bin
* amdgpu/navi12_vcn.bin
* amdgpu/navy_flounder_ce.bin
* amdgpu/navy_flounder_dmcub.bin
* amdgpu/navy_flounder_me.bin
* amdgpu/navy_flounder_mec.bin
* amdgpu/navy_flounder_mec2.bin
* amdgpu/navy_flounder_pfp.bin
* amdgpu/navy_flounder_rlc.bin
* amdgpu/navy_flounder_sdma.bin
* amdgpu/navy_flounder_smc.bin
* amdgpu/navy_flounder_sos.bin
* amdgpu/navy_flounder_ta.bin
* amdgpu/navy_flounder_vcn.bin
* amdgpu/oland_uvd.bin
* amdgpu/pitcairn_uvd.bin
* amdgpu/renoir_asd.bin
* amdgpu/renoir_ce.bin
* amdgpu/renoir_gpu_info.bin
* amdgpu/renoir_me.bin
* amdgpu/renoir_mec.bin
* amdgpu/renoir_mec2.bin
* amdgpu/renoir_pfp.bin
* amdgpu/renoir_rlc.bin
* amdgpu/renoir_sdma.bin
* amdgpu/renoir_ta.bin
* amdgpu/renoir_vcn.bin
* amdgpu/sienna_cichlid_ce.bin
* amdgpu/sienna_cichlid_dmcub.bin
* amdgpu/sienna_cichlid_me.bin
* amdgpu/sienna_cichlid_mec.bin
* amdgpu/sienna_cichlid_mec2.bin
* amdgpu/sienna_cichlid_pfp.bin
* amdgpu/sienna_cichlid_rlc.bin
* amdgpu/sienna_cichlid_sdma.bin
* amdgpu/sienna_cichlid_smc.bin
* amdgpu/sienna_cichlid_sos.bin
* amdgpu/sienna_cichlid_ta.bin
* amdgpu/sienna_cichlid_vcn.bin
* amdgpu/tahiti_uvd.bin
* amdgpu/vega20_ta.bin
* amdgpu/verde_uvd.bin
* atmel/wilc1000_wifi_firmware-1.bin
* cmmb_vega_12mhz.inp
* cmmb_venice_12mhz.inp
* dvb_nova_12mhz.inp
* dvb_nova_12mhz_b0.inp
* i915/bxt_guc_33.0.0.bin
* i915/glk_guc_33.0.0.bin
* i915/icl_guc_33.0.0.bin
* i915/kbl_guc_33.0.0.bin
* i915/skl_guc_33.0.0.bin
* i915/tgl_dmc_ver2_04.bin
* i915/tgl_huc_7.5.0.bin
* isdbt_nova_12mhz.inp
* isdbt_nova_12mhz_b0.inp
* isdbt_rio.inp
* iwlwifi-Qu-b0-hr-b0-59.ucode
* iwlwifi-Qu-b0-jf-b0-50.ucode
* iwlwifi-Qu-b0-jf-b0-59.ucode
* iwlwifi-Qu-c0-hr-b0-50.ucode
* iwlwifi-Qu-c0-hr-b0-59.ucode
* iwlwifi-QuZ-a0-hr-b0-50.ucode
* iwlwifi-QuZ-a0-hr-b0-59.ucode
* iwlwifi-QuZ-a0-jf-b0-50.ucode
* iwlwifi-QuZ-a0-jf-b0-59.ucode
* iwlwifi-cc-a0-50.ucode
* iwlwifi-cc-a0-59.ucode
* mediatek/mt7663pr2h.bin
* mellanox/mlxsw_spectrum-13.2000.1886.mfa2
* mellanox/mlxsw_spectrum-13.2008.1310.mfa2
* mellanox/mlxsw_spectrum2-29.2008.1310.mfa2
* mellanox/mlxsw_spectrum3-30.2008.1310.mfa2
* mrv

[Kernel-packages] [Bug 1922350] Re: missing firmware reported when updating initramfs

[You-Sheng Yang]

Note that not all the missing files listed in the original bug
description are going to be backported. Some of them might just be
unavailable even in upstream, e.g. amdgpu/vangogh_rlc.bin.

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ 
+ Some kernel firmwares might be landed after linux-firmware forked for
+ each series, or for LTS series, kernels of new versions may claim
+ additional ones that were not previously available. This leaves devices
+ fail to function correctly while they ought to.
+ 
+ With a checking script that enumerates all the blobs available in
+ upstream repo and in the Ubuntu fork of a given series, e.g. hirsute,
+ iterate through all the installed kernel modules of a given version to
+ check if claimed firmware blobs are available in Ubuntu's fork.
+ Following kernel version/series have been checked:
+ 
+   * 5.11.0-14-generic/hirsute
+   * 5.8.0-48-generic/groovy
+   * 5.4.0-70-generic/focal
+   * 5.6.0-1052-oem/focal
+   * 5.8.0-48-generic/focal
+   * 5.10.0-1019-oem/focal
+   * 4.15.0-140-generic/bionic
+   * 4.18.0-25-generic/bionic
+   * 5.0.0-65-generic/bionic
+   * 5.4.0-70-generic/bionic
+ 
+ And it gives following files were missing in at least one of above
+ cases:
+ 
+   * amdgpu/arcturus_asd.bin
+   * amdgpu/arcturus_gpu_info.bin
+   * amdgpu/arcturus_mec.bin
+   * amdgpu/arcturus_mec2.bin
+   * amdgpu/arcturus_rlc.bin
+   * amdgpu/arcturus_sdma.bin
+   * amdgpu/arcturus_smc.bin
+   * amdgpu/arcturus_sos.bin
+   * amdgpu/arcturus_ta.bin
+   * amdgpu/arcturus_vcn.bin
+   * amdgpu/navi12_asd.bin
+   * amdgpu/navi12_ce.bin
+   * amdgpu/navi12_dmcu.bin
+   * amdgpu/navi12_gpu_info.bin
+   * amdgpu/navi12_me.bin
+   * amdgpu/navi12_mec.bin
+   * amdgpu/navi12_mec2.bin
+   * amdgpu/navi12_pfp.bin
+   * amdgpu/navi12_rlc.bin
+   * amdgpu/navi12_sdma.bin
+   * amdgpu/navi12_sdma1.bin
+   * amdgpu/navi12_smc.bin
+   * amdgpu/navi12_sos.bin
+   * amdgpu/navi12_ta.bin
+   * amdgpu/navi12_vcn.bin
+   * amdgpu/navy_flounder_ce.bin
+   * amdgpu/navy_flounder_dmcub.bin
+   * amdgpu/navy_flounder_me.bin
+   * amdgpu/navy_flounder_mec.bin
+   * amdgpu/navy_flounder_mec2.bin
+   * amdgpu/navy_flounder_pfp.bin
+   * amdgpu/navy_flounder_rlc.bin
+   * amdgpu/navy_flounder_sdma.bin
+   * amdgpu/navy_flounder_smc.bin
+   * amdgpu/navy_flounder_sos.bin
+   * amdgpu/navy_flounder_ta.bin
+   * amdgpu/navy_flounder_vcn.bin
+   * amdgpu/oland_uvd.bin
+   * amdgpu/pitcairn_uvd.bin
+   * amdgpu/renoir_asd.bin
+   * amdgpu/renoir_ce.bin
+   * amdgpu/renoir_gpu_info.bin
+   * amdgpu/renoir_me.bin
+   * amdgpu/renoir_mec.bin
+   * amdgpu/renoir_mec2.bin
+   * amdgpu/renoir_pfp.bin
+   * amdgpu/renoir_rlc.bin
+   * amdgpu/renoir_sdma.bin
+   * amdgpu/renoir_ta.bin
+   * amdgpu/renoir_vcn.bin
+   * amdgpu/sienna_cichlid_ce.bin
+   * amdgpu/sienna_cichlid_dmcub.bin
+   * amdgpu/sienna_cichlid_me.bin
+   * amdgpu/sienna_cichlid_mec.bin
+   * amdgpu/sienna_cichlid_mec2.bin
+   * amdgpu/sienna_cichlid_pfp.bin
+   * amdgpu/sienna_cichlid_rlc.bin
+   * amdgpu/sienna_cichlid_sdma.bin
+   * amdgpu/sienna_cichlid_smc.bin
+   * amdgpu/sienna_cichlid_sos.bin
+   * amdgpu/sienna_cichlid_ta.bin
+   * amdgpu/sienna_cichlid_vcn.bin
+   * amdgpu/tahiti_uvd.bin
+   * amdgpu/vega20_ta.bin
+   * amdgpu/verde_uvd.bin
+   * atmel/wilc1000_wifi_firmware-1.bin
+   * cmmb_vega_12mhz.inp
+   * cmmb_venice_12mhz.inp
+   * dvb_nova_12mhz.inp
+   * dvb_nova_12mhz_b0.inp
+   * i915/bxt_guc_33.0.0.bin
+   * i915/glk_guc_33.0.0.bin
+   * i915/icl_guc_33.0.0.bin
+   * i915/kbl_guc_33.0.0.bin
+   * i915/skl_guc_33.0.0.bin
+   * i915/tgl_dmc_ver2_04.bin
+   * i915/tgl_huc_7.5.0.bin
+   * isdbt_nova_12mhz.inp
+   * isdbt_nova_12mhz_b0.inp
+   * isdbt_rio.inp
+   * iwlwifi-Qu-b0-hr-b0-59.ucode
+   * iwlwifi-Qu-b0-jf-b0-50.ucode
+   * iwlwifi-Qu-b0-jf-b0-59.ucode
+   * iwlwifi-Qu-c0-hr-b0-50.ucode
+   * iwlwifi-Qu-c0-hr-b0-59.ucode
+   * iwlwifi-QuZ-a0-hr-b0-50.ucode
+   * iwlwifi-QuZ-a0-hr-b0-59.ucode
+   * iwlwifi-QuZ-a0-jf-b0-50.ucode
+   * iwlwifi-QuZ-a0-jf-b0-59.ucode
+   * iwlwifi-cc-a0-50.ucode
+   * iwlwifi-cc-a0-59.ucode
+   * mediatek/mt7663pr2h.bin
+   * mellanox/mlxsw_spectrum-13.2000.1886.mfa2
+   * mellanox/mlxsw_spectrum-13.2008.1310.mfa2
+   * mellanox/mlxsw_spectrum2-29.2008.1310.mfa2
+   * mellanox/mlxsw_spectrum3-30.2008.1310.mfa2
+   * mrvl/sdsd8977_combo_v2.bin
+   * mrvl/sdsd8997_combo_v4.bin
+   * rtl_nic/rtl8125a-3.fw
+   * rtl_nic/rtl8168fp-3.fw
+   * rtw88/rtw8822c_wow_fw.bin
+   * sms1xxx-hcw-55xxx-dvbt-02.fw
+   * sms1xxx-hcw-55xxx-isdbt-02.fw
+   * sms1xxx-nova-a-dvbt-01.fw
+   * sms1xxx-nova-b-dvbt-01.fw
+   * sms1xxx-stellar-dvbt-01.fw
+   * tdmb_nova_12mhz.inp
+ 
+ [Fix]
+ 
+   * af1ca28f amdgpu: add arcturus firmware
+   * c82cb463 amdgpu: update sienna cichlid firmware for 20.50
+   * 25451a4f amdgpu: update navi12 firmware for 20.50
+   * 2542ba7a amdgpu: update renoir firmware for 20.50
+   * a29bdb2e amdgpu: add initial support for navy flounder
+   * 54c797a6 amdgpu: add sienna cichlid 

[Kernel-packages] [Bug 1913633] Re: nvidia-graphics-drivers-460 causes vlc to crash when taking video snapshot

[Launchpad Bug Tracker]

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

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

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

Title:
  nvidia-graphics-drivers-460 causes vlc to crash when taking video
  snapshot

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

Bug description:
  vlc 3.0.11.1-2 would happily take video snapshots with version 450
  (and earlier) of the drivers, but crashes instantly every time with
  460.

  me@mine ~$ vlc
  VLC media player 3.0.11.1 Vetinari (revision 3.0.11.1-0-g52483f3ca2)
  [55acea1745b0] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  [55acea213580] main playlist: playlist is empty
  (** attempt to take snapshot via GUI **)
  libEGL warning: DRI2: failed to authenticate
  [7f7f840045f0] gl gl: Initialized libplacebo v2.72.0 (API v72)
  [7f7f840045f0] glx gl error: cannot create GLX context
  libEGL warning: DRI2: failed to authenticate
  [7f7f840045f0] gles2 gl: Initialized libplacebo v2.72.0 (API v72)
  libEGL warning: DRI2: failed to authenticate
  [7f7f840045f0] gl gl: Initialized libplacebo v2.72.0 (API v72)
  Segmentation fault (core dumped)

  Using PrtSc to get a screenshot works, but doesn't capture the video
  shown in the vlc window.

  Ubuntu MATE 20.10, kernel 5.8.0-41-generic.
  nvidia-driver-460 460.32.03-0ubuntu0.20.10.1

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

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

[Kernel-packages] [Bug 1922350] Re: missing firmware reported when updating initramfs

[You-Sheng Yang]

update checker script used.

** Attachment added: "check-fw.sh v2"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1922350/+attachment/5487269/+files/check-fw.sh

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

Title:
  missing firmware reported when updating initramfs

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-firmware source package in Groovy:
  In Progress
Status in linux-firmware source package in Hirsute:
  In Progress

Bug description:
  I'm seeing the following:

  update-initramfs: Generating /boot/initrd.img-5.11.0-13-generic
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_ta.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_sos.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_toc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_asd.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_rlc.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_mec2.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_mec.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_me.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_pfp.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_ce.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_rlc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_mec2.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_mec.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_me.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_pfp.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_ce.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_sdma.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_sdma.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_vcn.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_smc.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_dmcub.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_dmcub.bin for 
module amdgpu
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Processing triggers for cups (2.3.3op2-3ubuntu3) ...
  Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.67.5-2) ...
  Processing triggers for libc-bin (2.33-0ubuntu4) ...
  Processing triggers for man-db (2.9.4-2) ...
  Processing triggers for dbus (1.12.20-1ubuntu3) ...

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-11-generic 5.11.0-11.12
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dad2584 F pulseaudio
   /dev/snd/controlC0:  dad2584 F pulseaudio
  CasperMD5CheckResult: unknown
  Curre