[Kernel-packages] [Bug 1943915] Re: Intel IPU6 GStreamer src plugin not working

[Stefan]

Yes, after installing these packages and adding the v4l2 relay config the 
camera works with ffplay and in firefox,not in cheese though, it still 
complains about:
"Buffer pool activation failed"

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

Title:
  Intel IPU6 GStreamer src plugin not working

Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.13 source package in Focal:
  Incomplete

Bug description:
  The device is properly detected but it seems there are still issues
  with gstreamer plugin. When I try to run cheese I get the following
  error message:

  ../src/intel/isl/isl.c:2018: FINISHME:
  ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is
  disabled, but a workaround is available.

  (cheese:3769): cheese-WARNING **: 08:02:37.506: Failed to allocate required 
memory.: gstv4l2src.c(660): gst_v4l2src_decide_allocation (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1:
  Buffer pool activation failed

  
  With VLC I get
  stefang@capella:~$ vlc v4l2:///dev/video0
  VLC media player 3.0.9.2 Vetinari (revision 3.0.9.2-0-gd4c1aefe4d)
  [55cfdb6a3670] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230001160] v4l2 demux error: cannot start streaming: Link has been 
severed
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: not a radio tuner device
  Using mplane plugin for capture 
  [7f0230007b70] v4l2 stream error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230007b70] v4l2 stream error: cannot start streaming: Link has been 
severed
  QObject::~QObject: Timers cannot be stopped from another thread

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-1012-oem 5.13.0-1012.16
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  Uname: Linux 5.13.0-1012-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Sep 17 07:59:51 2021
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-oem-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stefang1469 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. Latitude 9420
  Package: linux-oem-5.13 (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1012-oem 
root=UUID=e2704fd1-5330-4b87-9cdf-a353f5fe73b7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-1012-oem N/A
   linux-backports-modules-5.13.0-1012-oem  N/A
   linux-firmware   1.187.16
  Tags:  focal
  Uname: Linux 5.13.0-1012-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/13/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.2
  dmi.board.name: 08XKF8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd04/13/2021:br1.2:svnDellInc.:pnLatitude9420:pvr:sku0A32:rvnDellInc.:rn08XKF8:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9420
  dmi.product.sku: 0A32
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1943915/+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 1926142] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (error: ‘F_SEAL_FUTURE_WRITE’ undeclared)

[Po-Hsu Lin]

** Summary changed:

- memfd from ubuntu_kernel_selftests failed to build on B-5.4
+ memfd from ubuntu_kernel_selftests failed to build on B-5.4 (error: 
‘F_SEAL_FUTURE_WRITE’ undeclared)

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

Title:
  memfd from ubuntu_kernel_selftests failed to build on B-5.4 (error:
  ‘F_SEAL_FUTURE_WRITE’ undeclared)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-hwe source package in Bionic:
  Invalid
Status in linux-hwe-5.4 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-hwe source package in Focal:
  Invalid
Status in linux-hwe-5.4 source package in Focal:
  Invalid

Bug description:
  Test build on B-5.4 (5.4.0-73.82~18.04.1) failed with:
error: ‘F_SEAL_FUTURE_WRITE’ undeclared

  Build log:
  $ sudo make TARGETS=memfd
  make --no-builtin-rules ARCH=x86 -C ../../.. headers_install
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
INSTALL ./usr/include
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
  gcc -D_FILE_OFFSET_BITS=64 -I../../../../include/uapi/ -I../../../../include/ 
-I../../../../usr/include/memfd_test.c common.o  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test
  memfd_test.c: In function ‘test_seal_future_write’:
  memfd_test.c:749:27: error: ‘F_SEAL_FUTURE_WRITE’ undeclared (first use in 
this function); did you mean ‘F_SEAL_WRITE’?
mfd_assert_add_seals(fd, F_SEAL_FUTURE_WRITE);
 ^~~
 F_SEAL_WRITE
  memfd_test.c:749:27: note: each undeclared identifier is reported only once 
for each function it appears in
  ../lib.mk:141: recipe for target 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test'
 failed
  make[1]: *** 
[/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test]
 Error 1
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
  Makefile:143: recipe for target 'all' failed
  make: *** [all] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1926142/+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 1667750]

[dion]

I also have exactly same problem, but with a bit different HW.

Now it's USB DAC branded as "Qudelix-5K". As far as I understand it's
USB1 device.

[  174.358189] usb 5-2.3.2.2.1.1: new full-speed USB device number 17 using 
xhci_hcd
[  174.475229] usb 5-2.3.2.2.1.1: New USB device found, idVendor=0a12, 
idProduct=4025, bcdDevice=19.70
[  174.475232] usb 5-2.3.2.2.1.1: New USB device strings: Mfr=1, Product=8, 
SerialNumber=3
[  174.475233] usb 5-2.3.2.2.1.1: Product: Qudelix-5K USB DAC/MIC 48KHz
[  174.475234] usb 5-2.3.2.2.1.1: Manufacturer: QTIL
[  174.475235] usb 5-2.3.2.2.1.1: SerialNumber: ABCDEF0123456789

It produces corrupted sound (actually some noise) just after a few
seconds of playback if connected to Dell WD19TB thunderbolt dock
station. Issue happens with USB-A ports on dock plus one Type-C port
(front). Second Type-C port (named as "Type-C with Thunderbolt 3 port"
works.

When such noise happens I'm getting followed in dmesg:

xhci_hcd :3a:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 
ep_index 5 comp_code 1
xhci_hcd :3a:00.0: Looking for event-dma ffe940f0 trb-start 
ffe94100 trb-end ffe94100 seg-start ffe94000 seg-end 
ffe94ff0
xhci_hcd :3a:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 
ep_index 5 comp_code 1
xhci_hcd :3a:00.0: Looking for event-dma ffe949b0 trb-start 
ffe949c0 trb-end ffe949c0 seg-start ffe94000 seg-end 
ffe94ff0

I've tried to add/remove extra USB hubs (originally Qudelix was plugged
to internal USB3 hub of monitor). But even if plugged directly to dock,
it produces corrupted sound.

Another important thing: this dock has built-in Ethernet with r8153
chipset like mentioned above.

After reading comments here I've tried to disable soft retry using
followed patch:

diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index 1c9a7957c45c..07cbcf50160c 100644
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
@@ -189,10 +189,11 @@ static void xhci_pci_quirks(struct device *dev, struct 
xhci_hcd *xhci)
 
if (pdev->vendor == PCI_VENDOR_ID_INTEL) {
xhci->quirks |= XHCI_LPM_SUPPORT;
xhci->quirks |= XHCI_INTEL_HOST;
xhci->quirks |= XHCI_AVOID_BEI;
+   xhci->quirks |= XHCI_NO_SOFT_RETRY;
}
if (pdev->vendor == PCI_VENDOR_ID_INTEL &&
pdev->device == PCI_DEVICE_ID_INTEL_PANTHERPOINT_XHCI) {
xhci->quirks |= XHCI_EP_LIMIT_QUIRK;
xhci->limit_active_eps = 64;

And it completely fixed issue for me. DAC produces clear sound even if
connected through chain of two hubs!


PS. 
lspci -k -nn | grep -B2 xhci 
00:14.0 USB controller [0c03]: Intel Corporation Comet Lake PCH-LP USB 3.1 xHCI 
Host Controller [8086:02ed]
Subsystem: Hewlett-Packard Company Comet Lake PCH-LP USB 3.1 xHCI Host 
Controller [103c:8724]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
--
37:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)
Subsystem: Hewlett-Packard Company JHL7540 Thunderbolt 3 USB Controller 
[Titan Ridge 4C 2018] [103c:8723]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
--
3a:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge DD 2018] [8086:15f0] (rev 06)
Subsystem: Intel Corporation JHL7540 Thunderbolt 3 USB Controller 
[Titan Ridge DD 2018] [8086:]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

5.14.6 kernel

Hope that this will help to fix it

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  Fix Released
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) 

[Kernel-packages] [Bug 1926142] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4

[Po-Hsu Lin]

https://lists.ubuntu.com/archives/kernel-team/2021-August/123670.html
Patch from Luke.

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

Title:
  memfd from ubuntu_kernel_selftests failed to build on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-hwe source package in Bionic:
  Invalid
Status in linux-hwe-5.4 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-hwe source package in Focal:
  Invalid
Status in linux-hwe-5.4 source package in Focal:
  Invalid

Bug description:
  Test build on B-5.4 (5.4.0-73.82~18.04.1) failed with:
error: ‘F_SEAL_FUTURE_WRITE’ undeclared

  Build log:
  $ sudo make TARGETS=memfd
  make --no-builtin-rules ARCH=x86 -C ../../.. headers_install
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
INSTALL ./usr/include
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
  gcc -D_FILE_OFFSET_BITS=64 -I../../../../include/uapi/ -I../../../../include/ 
-I../../../../usr/include/memfd_test.c common.o  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test
  memfd_test.c: In function ‘test_seal_future_write’:
  memfd_test.c:749:27: error: ‘F_SEAL_FUTURE_WRITE’ undeclared (first use in 
this function); did you mean ‘F_SEAL_WRITE’?
mfd_assert_add_seals(fd, F_SEAL_FUTURE_WRITE);
 ^~~
 F_SEAL_WRITE
  memfd_test.c:749:27: note: each undeclared identifier is reported only once 
for each function it appears in
  ../lib.mk:141: recipe for target 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test'
 failed
  make[1]: *** 
[/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test]
 Error 1
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
  Makefile:143: recipe for target 'all' failed
  make: *** [all] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1926142/+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 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops

[Kuroš Taheri-Golværzi]

Just happened again with Nvidia-460. I'll try uninstalling VirtualBox
and see what happens.

** Attachment added: "prevboot-2021-09-21-a.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939966/+attachment/5526789/+files/prevboot-2021-09-21-a.txt

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

Title:
  [Asus TUF Gaming FA506IV] Random system stops

Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Every once in a while (it's been three times this week), the entire
  system will just stop. There's still electricity running. The keyboard
  is lit up, and the monitor is black (electricity-running black, and
  not shutdown-black). There's no picture and no sound. Just immediately
  before it does, I know it's about to happen because whatever audio is
  playing at the time will begin repeating, and then the computer goes
  down. I don't actually know if it's an Xorg problem. It just sounded
  like the closest possibility, based on the way the computer actually
  behaves.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  470.57.02  Tue Jul 13 
16:14:05 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Aug 14 19:34:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed
   nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed
   virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed
   virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2021-03-20 (147 days ago)
  InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  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.9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock

[AaronMa]

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

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

Title:
  External displays not working on Thinkpad T490 with ThinkPad
  Thunderbolt 3 Dock

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

Bug description:
  I have two external displays chained via Display port connected to the
  ThinkPad Thunderbolt 3 Dock.

  They are working with kernel 5.8.0-63 but not with the new 5.11.0-25
  kernel.

  I could reproduce this behavior several times for both kernels, as
  follows: I booted up with disconnected dock, logged in, then I
  connected it, disconnected it, and connected it again.

  With the 5.11.0-25 kernel the external displays go black; the main
  screen turns off and on several times. Sometimes the main screen
  remains working, but UI is lagging.

  I'm attaching the logs. Two separate boots for each variant are marked
  'a'/'b'.

  SRU Justifications:
  ===
  [Impact]
  External displays not working on Thinkpad T490 with ThinkPad Thunderbolt
  3 Dock

  [Fix]
  Some SKL systems DP output fails when AUX timeout of LTTPR detection.
  Disable the LTTPR detection until GLK to fix the link training.

  [Test]
  Verified on hardware, external DP work fine.
  Also tested on I+N GPU laptop and a iGPU only laptop, all displays with dock 
are good.

  [Where problems could occur]
  It may break output of external DP.

  This patch from 5.12-rc5, only Hirsute kernel is SRUed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938999/+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 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish

[Po-Hsu Lin]

Verified on F-oem-5.10.0-1047.49

ok 22 selftests: net: psock_snd.sh

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

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

Title:
  psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
  focal/groovy/hirsute/impish

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Won't Fix
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  The expected to fail 'raw gso min size - 1' test in psock_snd.sh is
  not failing as expected, and thus this test will fail with:

raw gso min size - 1 (expected to fail)
tx: 1524
rx: 1472
OK

  This is because after commit 7c6d2ec ("net: be more gentle about silly
  gso requests coming from user"), we relaxed the min gso_size check in
  virtio_net_hdr_to_skb().

  So when a packet which is smaller then the gso_size, GSO for this
  packet will not be set, the packet will be send/recv successfully.

  [Fix]
  * cfba3fb68960b4 selftests/net: remove min gso test in packet_snd

  This patch can be cherry-picked into all affected kernels.

  I decided to skip those 5.8 variants, as the current cycle
  (2021-09-06) might be the last cycle for them.

  [Test]
  Run this psock_snd.sh script, this test will no longer exist and the
  script can proceed with the next test.

  [Where problems could occur]
  Removing this broken test should not have any negative impact to our
  tests. We will need to update our hints later.

  
  [Original Bug Report]
  Testing failed on focal/linux 5.4.0-44.48:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz

  psock_snd.sh output:

  16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
  16:28:31 DEBUG| [stdout] # dgram
  16:28:31 DEBUG| [stdout] # tx: 128
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # dgram bind
  16:28:31 DEBUG| [stdout] # tx: 128
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw bind
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw qdisc bypass
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw vlan
  16:28:31 DEBUG| [stdout] # tx: 146
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw vnet hdr
  16:28:31 DEBUG| [stdout] # tx: 152
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw csum_off
  16:28:31 DEBUG| [stdout] # tx: 152
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
  16:28:31 DEBUG| [stdout] # raw min size
  16:28:31 

[Kernel-packages] [Bug 1944435] Re: Backlight on P17 Gen 1 not working Nvidia 470

[AaronMa]

Please use "i915.enable_dpcd_backlight=0" for WA, or use 5.13.0-1012-oem
kernel instead.

I will try to fix it in hirsute kernel.

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

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

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04

[Michael Reed]

Many of the patches were already in the impish kernel, so I have
summarized the impact statement for what was cherry picked.


SRU Justification:

[Impact]
This is a feature request to update the mpt3sas driver to latest version in 
upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04.
This will allow users to use fixes and enhancements that landed upstream in 
5.14. For this reason,
Broadcom and Dell have requested to pull these patches to update the
mpt3sas driver to the current upstream version.

I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver
v36.100.00.00, following are the commit ID's to update to 38.100.00.00


[FIXES]
The following fix patches are cosmetic patches which doesn't have any driver 
functionality impacts:
- 84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang
- cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue


The following patches are related to kernel APIs compatible changes and doesn't 
have any driver functionality impacts:
- f2b1e9c6f8 scsi: core: Introduce scsi_build_sense()
- 2910a4a9e9 scsi: mpt3sas: Documentation cleanup



Handle firmware faults gracefully during IOC initialization time:
Currently, if the driver detects any firmware fault during the IOC 
initialization then the driver terminates the IOC initialization operation. 
With this feature, the driver tries to recover the IOC from the fault state, if 
IOC successfully recovers from the fault state then driver continues with the 
IOC initialization operation.
- 19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init
- a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC 
init

[TESTING]
Load the driver
Run IO

[REGRESSION RISK]
No extra test cases are needed, normal regression test cases such as driver 
load & running IOs are enough.

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

Title:
  Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  New
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  Confirmed

Bug description:
  [Impact]
  This is a feature request to update the mpt3sas driver to latest version in 
upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04.
  This will allow users to use fixes and enhancements that landed upstream in 
5.14. For this reason,
  Broadcom and Dell have requested to pull these patches to update the
  mpt3sas driver to the current upstream version.

  I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver
  v36.100.00.00, following are the commit ID's to update to 38.100.00.00

  [Fixes]
  8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers()
  39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" -> 
"compatibility"
  bfb3f00c06 scsi: mpt3sas: Simplify bool comparison
  d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation
  664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug
  688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface
  446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00

  8278807abd scsi: core: Add scsi_device_busy() wrapper
  020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap

  e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic()
  2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap
  cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot
  54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params
  782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues
  a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context
  a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a 
static one
  d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within 
same 4 GB region
  7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 
GB region
  970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 
GB region
  58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 
GB region
  2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within 
same 4 GB region
  c569de899b scsi: mpt3sas: Force reply post array allocations to be within 
same 4 GB region
  37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00

  a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues
  3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach()

  206a3afa94 scsi: mpt3sas: Fix a typo
  4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi 
vSES
  c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement
  3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset
  16660db3fc scsi: mpt3sas: 

[Kernel-packages] [Bug 1943915] Re: Intel IPU6 GStreamer src plugin not working

[You-Sheng Yang]

I think you should be able to install following packages from the same
ppa:

  * gstreamer1.0-icamera
  * v4l2loopback-dkms
  * v4l2-relayd

These 3 should be sufficient for you to bring up IPU6. And you'll need
to create a config file /etc/v4l2-relayd:

  root$ echo  Incomplete

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

Title:
  Intel IPU6 GStreamer src plugin not working

Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.13 source package in Focal:
  Incomplete

Bug description:
  The device is properly detected but it seems there are still issues
  with gstreamer plugin. When I try to run cheese I get the following
  error message:

  ../src/intel/isl/isl.c:2018: FINISHME:
  ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is
  disabled, but a workaround is available.

  (cheese:3769): cheese-WARNING **: 08:02:37.506: Failed to allocate required 
memory.: gstv4l2src.c(660): gst_v4l2src_decide_allocation (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1:
  Buffer pool activation failed

  
  With VLC I get
  stefang@capella:~$ vlc v4l2:///dev/video0
  VLC media player 3.0.9.2 Vetinari (revision 3.0.9.2-0-gd4c1aefe4d)
  [55cfdb6a3670] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230001160] v4l2 demux error: cannot start streaming: Link has been 
severed
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: not a radio tuner device
  Using mplane plugin for capture 
  [7f0230007b70] v4l2 stream error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230007b70] v4l2 stream error: cannot start streaming: Link has been 
severed
  QObject::~QObject: Timers cannot be stopped from another thread

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-1012-oem 5.13.0-1012.16
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  Uname: Linux 5.13.0-1012-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Sep 17 07:59:51 2021
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-oem-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stefang1469 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. Latitude 9420
  Package: linux-oem-5.13 (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1012-oem 
root=UUID=e2704fd1-5330-4b87-9cdf-a353f5fe73b7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-1012-oem N/A
   linux-backports-modules-5.13.0-1012-oem  N/A
   linux-firmware   1.187.16
  Tags:  focal
  Uname: Linux 5.13.0-1012-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/13/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.2
  dmi.board.name: 08XKF8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd04/13/2021:br1.2:svnDellInc.:pnLatitude9420:pvr:sku0A32:rvnDellInc.:rn08XKF8:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9420
  dmi.product.sku: 0A32
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1943915/+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 1943469] Re: [Asus X541NC] wakes up from sleep mode after 1 second

[Daniel van Vugt]

To re-enable them is the same command, it only toggles the setting. Also
it may not be remembered between reboots so just rebooting likely will
reset them too.

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

Title:
  [Asus X541NC] wakes up from sleep mode after 1 second

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

Bug description:
  computer "wakes up" from sleep mode after 1 second no matter if i wait
  the given time for it to sleep, or if i put it to sleep with terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 13 18:56:14 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 
Series Integrated Graphics Controller [1043:16a0]
 Subsystem: ASUSTeK Computer Inc. GK107M [GeForce 810M] [1043:137e]
  InstallationDate: Installed on 2021-07-30 (44 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam
   Bus 001 Device 002: ID 0bda:b721 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541NC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=264f931b-e96b-44e9-a13d-bf5c3236a567 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541NC.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541NC
  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.:bvrX541NC.307:bd06/19/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX541NC:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX541NC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541NC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943469/+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 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops

[Daniel van Vugt]

Comment #34 appears to be a *different* kernel bug again:

  watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [apt-esm-hook:2930]

although what came before that is suspicious too:

  kernel: BUG: kernel NULL pointer dereference, address: 006c
  kernel: #PF: supervisor write access in kernel mode
  kernel: #PF: error_code(0x0002) - not-present page

So I would recommend trying:

 * Uninstalling VirtualBox and its kernel drivers to see if the crashes stop 
happening.
 * Testing the RAM overnight with https://www.memtest.org/ or 
https://www.memtest86.com/

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

Title:
  [Asus TUF Gaming FA506IV] Random system stops

Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Every once in a while (it's been three times this week), the entire
  system will just stop. There's still electricity running. The keyboard
  is lit up, and the monitor is black (electricity-running black, and
  not shutdown-black). There's no picture and no sound. Just immediately
  before it does, I know it's about to happen because whatever audio is
  playing at the time will begin repeating, and then the computer goes
  down. I don't actually know if it's an Xorg problem. It just sounded
  like the closest possibility, based on the way the computer actually
  behaves.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  470.57.02  Tue Jul 13 
16:14:05 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Aug 14 19:34:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed
   nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed
   virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed
   virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2021-03-20 (147 days ago)
  InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  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.9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: 

[Kernel-packages] [Bug 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04

[Michael Reed]

** Description changed:

- This is a feature request to update the mpt3sas driver to latest version in 
upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04. 
+ [Impact]
+ This is a feature request to update the mpt3sas driver to latest version in 
upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04.
  This will allow users to use fixes and enhancements that landed upstream in 
5.14. For this reason,
  Broadcom and Dell have requested to pull these patches to update the
  mpt3sas driver to the current upstream version.
  
  I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver
  v36.100.00.00, following are the commit ID's to update to 38.100.00.00
  
+ [Fixes]
  8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers()
  39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" -> 
"compatibility"
  bfb3f00c06 scsi: mpt3sas: Simplify bool comparison
  d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation
  664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug
  688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface
  446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00
  
  8278807abd scsi: core: Add scsi_device_busy() wrapper
  020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap
  
  e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic()
  2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap
  cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot
  54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params
  782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues
  a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context
  a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a 
static one
  d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within 
same 4 GB region
  7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 
GB region
  970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 
GB region
  58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 
GB region
  2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within 
same 4 GB region
  c569de899b scsi: mpt3sas: Force reply post array allocations to be within 
same 4 GB region
  37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00
  
  a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues
  3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach()
-   
   
+ 
  206a3afa94 scsi: mpt3sas: Fix a typo
  4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi 
vSES
  c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement
  3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset
  16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query
  3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers
  2910a4a9e9 scsi: mpt3sas: Documentation cleanup
  e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware 
event
  19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init
  a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC 
init
  
  f2b1e9c6f8 scsi: core: Introduce scsi_build_sense()
  
  84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang
  cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue
  d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add()
  
- 
  Note:
  We have  already posted patch to update  driver version to 38.100.00.00
  Other patches are already available in upstream .
+ 
+ [Testing]
+ Load the driver
+ Run IO
+ 
+ [Regression Risk]
+ No extra test cases are needed, normal regression test cases such as driver 
load & running IOs are enough.

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

Title:
  Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  New
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  Confirmed

Bug description:
  [Impact]
  This is a feature request to update the mpt3sas driver to latest version in 
upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04.
  This will allow users to use fixes and enhancements that landed upstream in 
5.14. For this reason,
  Broadcom and Dell have requested to pull these patches to update the
  mpt3sas driver to the current upstream version.

  I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver
  v36.100.00.00, following are the commit ID's to update to 38.100.00.00

  [Fixes]
  8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers()
 

[Kernel-packages] [Bug 1749961]

[dion]

I also have exactly same problem, but with a bit different HW.

Now it's USB DAC branded as "Qudelix-5K". As far as I understand it's
USB1 device.

[  174.358189] usb 5-2.3.2.2.1.1: new full-speed USB device number 17 using 
xhci_hcd
[  174.475229] usb 5-2.3.2.2.1.1: New USB device found, idVendor=0a12, 
idProduct=4025, bcdDevice=19.70
[  174.475232] usb 5-2.3.2.2.1.1: New USB device strings: Mfr=1, Product=8, 
SerialNumber=3
[  174.475233] usb 5-2.3.2.2.1.1: Product: Qudelix-5K USB DAC/MIC 48KHz
[  174.475234] usb 5-2.3.2.2.1.1: Manufacturer: QTIL
[  174.475235] usb 5-2.3.2.2.1.1: SerialNumber: ABCDEF0123456789

It produces corrupted sound (actually some noise) just after a few
seconds of playback if connected to Dell WD19TB thunderbolt dock
station. Issue happens with USB-A ports on dock plus one Type-C port
(front). Second Type-C port (named as "Type-C with Thunderbolt 3 port"
works.

When such noise happens I'm getting followed in dmesg:

xhci_hcd :3a:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 
ep_index 5 comp_code 1
xhci_hcd :3a:00.0: Looking for event-dma ffe940f0 trb-start 
ffe94100 trb-end ffe94100 seg-start ffe94000 seg-end 
ffe94ff0
xhci_hcd :3a:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 
ep_index 5 comp_code 1
xhci_hcd :3a:00.0: Looking for event-dma ffe949b0 trb-start 
ffe949c0 trb-end ffe949c0 seg-start ffe94000 seg-end 
ffe94ff0

I've tried to add/remove extra USB hubs (originally Qudelix was plugged
to internal USB3 hub of monitor). But even if plugged directly to dock,
it produces corrupted sound.

Another important thing: this dock has built-in Ethernet with r8153
chipset like mentioned above.

After reading comments here I've tried to disable soft retry using
followed patch:

diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index 1c9a7957c45c..07cbcf50160c 100644
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
@@ -189,10 +189,11 @@ static void xhci_pci_quirks(struct device *dev, struct 
xhci_hcd *xhci)
 
if (pdev->vendor == PCI_VENDOR_ID_INTEL) {
xhci->quirks |= XHCI_LPM_SUPPORT;
xhci->quirks |= XHCI_INTEL_HOST;
xhci->quirks |= XHCI_AVOID_BEI;
+   xhci->quirks |= XHCI_NO_SOFT_RETRY;
}
if (pdev->vendor == PCI_VENDOR_ID_INTEL &&
pdev->device == PCI_DEVICE_ID_INTEL_PANTHERPOINT_XHCI) {
xhci->quirks |= XHCI_EP_LIMIT_QUIRK;
xhci->limit_active_eps = 64;

And it completely fixed issue for me. DAC produces clear sound even if
connected through chain of two hubs!


PS. 
lspci -k -nn | grep -B2 xhci 
00:14.0 USB controller [0c03]: Intel Corporation Comet Lake PCH-LP USB 3.1 xHCI 
Host Controller [8086:02ed]
Subsystem: Hewlett-Packard Company Comet Lake PCH-LP USB 3.1 xHCI Host 
Controller [103c:8724]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
--
37:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)
Subsystem: Hewlett-Packard Company JHL7540 Thunderbolt 3 USB Controller 
[Titan Ridge 4C 2018] [103c:8723]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
--
3a:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge DD 2018] [8086:15f0] (rev 06)
Subsystem: Intel Corporation JHL7540 Thunderbolt 3 USB Controller 
[Titan Ridge DD 2018] [8086:]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

5.14.6 kernel

Hope that this will help to fix it

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd 

[Kernel-packages] [Bug 1922334] Re: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16)

[koba]

@Georgi, would you please try 5.15, please get the ARCH=amd generic files and a 
header with "all" postfix file.
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15-rc2/

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

Title:
  External monitor does not wake up on Titan Ridge laptops when docked
  (9500, TB16)

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-meta-oem-5.6 package in Ubuntu:
  New
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux-oem-5.13 package in Ubuntu:
  New

Bug description:
  I've recently upgraded my workhorse from XPS 9560 (2016) to a newer
  generation XPS 9500 (2020) and ran into several things that feel like
  regressions, but are probably related to hardware changes. This is one
  of them.

  tl;dr:
  When using XPS 9500 with a TB16 dock and an external monitor (Benq EX2780Q) 
connected to the dock via USB-C to USB-C (DP alternate mode), most of the time 
the monitor fails to wake up after going blank.

  
  details:
  Simplest way to reproduce is for hit Super+L, wait for the monitor to 
properly go in standby, then type something in or move the mouse to wake it up. 
8 times out of 10 it does not wake up when using XPS 9500. Most of the time 
this can be fixed by power cycling the monitor, however this has a seemingly 
random chance of triggering two other issues:

  1. The system to lose sight of the monitor for a brief period of time, which 
sometimes causes it to hang with a black screen and needs some combination of 
restarting the monitor, the dock, and the laptop, because there is a separate 
USB issue making hot-plugging unusable.
  2. The monitor itself gets stuck in a weird standby state where it stops 
reacting to button presses and I need to hold the power button a bit longer for 
it to sort of hard reset?

  Notably, it wakes up fine every time when using XPS 9560 or Precision
  5520 in the same setup which I have been using for ages.

  This becomes particularly troublesome when screens go into short-lived
  standby during boot: after the Dell logo, after entering the LUKS
  password, after logging in. Each of these points has a chance of
  triggering the bug, because it looks like there is some sort of mode
  change and waking signal submission happening between them that
  triggers it. I had to disable screen timeout as a temporary workaround
  to be able to work on this system at all without having to play
  "monitor wake lottery" every time I go brew a cuppa. The workaround at
  boot time is to either re-roll the lottery, or boot with the dock
  connected and lid open, then close the lid and keep working from
  there.

  The dock, the monitor, all USB peripherals are the same in both cases
  - it's literally just the TB16 cable plugged into a different laptop.

  I have attempted  5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM
  (-20.04b and -20.04-edge) kernels on the 9500 with same results. I
  have attempted disabling USB autosuspend via a GRUB kernel parameter
  to usbcore. I have attempted both NVidia and Intel GPUs. I have
  attempted playing with BIOS settings: wake on dell usb-c docks,
  disable early sign of life for both checkboxes, disabling SGX and SMM,
  checking all 3 boxes for Thunderbolt and switching off Thunderbolt
  security. None of these make a noticeable difference.

  Since it was fine with 9560, 5520 and a friend with a 9570 has no
  issues either, my gut feeling is that this is due to the upgrade from
  Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in
  this generation - something wrong with the driver, or the firmware may
  have missed some of the "lessons learned" in Alpine Ridge and caused
  this regression. That would also make it applicable to 9300, which has
  a "developer edition" option under Project Sputnik and several reports
  of the same problem scattered across the internet:

  
https://www.dell.com/community/XPS/XPS-13-9300-with-WD19TB-External-display-not-coming-on-after/td-p/7676922
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342 (may be a 
duplicate, but for WD19TB dock on 9300, so may be slightly different too)
  
https://www.reddit.com/r/linuxquestions/comments/ka0w2j/monitor_doesnt_wake_from_sleep/

  etc etc. Those reports suggest high bandwidth usage sometimes affects
  it, so it's worth noting that my external monitor is a 1440p 144Hz one
  that uses tons of bandwidth indeed.

  The only hint in terms of logs seems to be this message in dmesg that
  I see when power cycling the monitor and getting back into the system:

  [  250.777684] pcieport :09:04.0: pciehp: Slot(0-1): Card not present
  [  250.777695] xhci_hcd :0b:00.0: can't change power state from D3cold to 
D0 (config space inaccessible)
  [  250.778293] xhci_hcd :0b:00.0: can't change power state from D3hot to 
D0 

[Kernel-packages] [Bug 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock

[Kelsey Skunberg]

Thank you for the note, Tomas. Aaron, may you please help with the
verification on this? Thank you!

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

Title:
  External displays not working on Thinkpad T490 with ThinkPad
  Thunderbolt 3 Dock

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

Bug description:
  I have two external displays chained via Display port connected to the
  ThinkPad Thunderbolt 3 Dock.

  They are working with kernel 5.8.0-63 but not with the new 5.11.0-25
  kernel.

  I could reproduce this behavior several times for both kernels, as
  follows: I booted up with disconnected dock, logged in, then I
  connected it, disconnected it, and connected it again.

  With the 5.11.0-25 kernel the external displays go black; the main
  screen turns off and on several times. Sometimes the main screen
  remains working, but UI is lagging.

  I'm attaching the logs. Two separate boots for each variant are marked
  'a'/'b'.

  SRU Justifications:
  ===
  [Impact]
  External displays not working on Thinkpad T490 with ThinkPad Thunderbolt
  3 Dock

  [Fix]
  Some SKL systems DP output fails when AUX timeout of LTTPR detection.
  Disable the LTTPR detection until GLK to fix the link training.

  [Test]
  Verified on hardware, external DP work fine.
  Also tested on I+N GPU laptop and a iGPU only laptop, all displays with dock 
are good.

  [Where problems could occur]
  It may break output of external DP.

  This patch from 5.12-rc5, only Hirsute kernel is SRUed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938999/+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 1929902] Re: [EHL] enable USB-dw3

[Kelsey Skunberg]

Hi Chao or Hsuan-Yu, may you please verify the kernel in -proposed for
Focal-intel resolves this bug? Thank you.

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

Title:
  [EHL] enable USB-dw3

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete
Status in linux-intel package in Ubuntu:
  Fix Committed

Bug description:
  Description
  Enable USB-dw3 for Elkhart Lake

  Hardware: Elkhart Lake

  Target Release: 21.04
  Target Kernel: TBD

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1929902/+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 1934923] Re: Sync up mlxbf-gige driver with upstreamed version

[Kelsey Skunberg]

Hi Asmaa. May you please verify the kernel is -proposed for focal
bluefield resolves this bug? Thank you.

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

Title:
  Sync up mlxbf-gige driver with upstreamed version

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  The mlxbf-gige driver has just been upstreamed so linux-bluefield needs to be 
synced up with what we have upstreamed.
  IMPORTANT: during testing, make sure the latest UEFI (bootloader) is loaded 
on top of these changes, otherwise both the gpio driver and mlxbf-gige driver 
will fail to load.

  [Fix]

  * reverted 20 commits related to the mlxbf-gige driver and 1 commit related 
to gpio-mlxbf2 driver since there are dependencies between them.
  * Cherry-picked f92e1869d74e1acc6551256eb084a1c14a054e19 from net-next 
branch. The upstreamed version of the GPIO driver removed the dependency 
between the mlxbf-gige driver and gpio-mlxbf2 driver.
  * added code that was left out of the upstreamed version. and added code that 
got reverted in gpio-mlxbf2.c
  * updated the UEFI ACPI table to reflect the above changes (so the bootloader 
and the linux drivers need to be in sync)

  [Test Case]

  * oob_net0 coming up after several SW_RESET or reboot
  * oob_net0 coming up after several powercycles
  * oob_net0 coming up after pushing a new Ubuntu/CentOS/Yocto
  * rmmod/modprove mlxbf_gige several times
  * OOB PXE boot multiple times from UEFI menu
  * automate OOB PXE boot and do reboot
  * automate OOB PXE boot and do powercycle
  * Test that GPIO7 reset still works on BlueSphere like boards

  [Regression Potential]

  Any of the test cases above could be impacted due to these changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934923/+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 1938818] Re: Add support for packet-per-second policing

[Kelsey Skunberg]

Hi Bodong. May you please verify the kernel in -proposed for Focal-
bluefield resolves this bug? Thank you!

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

Title:
  Add support for packet-per-second policing

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  
  * Explain the bug(s)

  It’s a missing feature in current kernel. 
   
  * brief explanation of fixes

  Cherry-pick and backport the related patches from upstream kernel.

  * How to test

  Add tc filter rule with police action, and check it is offloaded.
  For example:
  tc filter add dev enp8s0f0_0 ingress protocol ip  flower \
  dst_mac b8:ce:f6:7b:d9:24 \
  action police pkts_rate 1000 pkts_burst 100 conform-exceed drop/pipe \
  action mirred egress redirect dev enp8s0f0

  * What it could break.

  New feature, doesn't break existing features.

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


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

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

[Kelsey Skunberg]

seems focal got automatically set back to `fix released`. due to
reverting the commit, setting this back to triaged, again.

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

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

Title:
  Medion Notebook Keyboard not working

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Triaged
Status in linux-oem-5.10 source package in Focal:
  Fix Committed

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

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

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.4.0.1047.46)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-kvm (5.4.0.1047.46) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3 (amd64)
glibc/2.31-0ubuntu9.2 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
rtl8821ce/5.5.2.1-0ubuntu4~20.04.3 (amd64)
lttng-modules/2.12.5-1ubuntu2~20.04.1 (amd64)
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64)
oss4/4.2-build2010-5ubuntu6~20.04.3 (amd64)
evdi/1.9.1-1ubuntu4~20.04.1 (amd64)
v4l2loopback/0.12.3-1ubuntu0.4 (amd64)
sl-modem/2.9.11~20110321-16ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-kvm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1944472] 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 1944472

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

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

Title:
  Bug configuration monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bug in the monitor settings, when clicking on the icon it does not open 
making it impossible to change the monitor configuration.
  Ex: Monitor resolution, position change and wallpaper.

  
  5.11.0-36-generic #40~20.04.1-Ubuntu SMP Sat Sep 18 02:14:19 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944472/+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 1944472] [NEW] Bug configuration monitor

[Samuel Jesus]

Public bug reported:

Bug in the monitor settings, when clicking on the icon it does not open making 
it impossible to change the monitor configuration.
Ex: Monitor resolution, position change and wallpaper.


5.11.0-36-generic #40~20.04.1-Ubuntu SMP Sat Sep 18 02:14:19 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux

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

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

Title:
  Bug configuration monitor

Status in linux package in Ubuntu:
  New

Bug description:
  Bug in the monitor settings, when clicking on the icon it does not open 
making it impossible to change the monitor configuration.
  Ex: Monitor resolution, position change and wallpaper.

  
  5.11.0-36-generic #40~20.04.1-Ubuntu SMP Sat Sep 18 02:14:19 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944472/+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 1943616] Re: CD-ROM tray opens on wake from suspend on Ubuntu 20.04 LTS Focal

[Angus]

I've done the upgrade to kernel 5.4.0-86, and the problem is still
present.  Leaving a unsed CD/DVD in the drawer and unmounting it is
still an effective workaround.

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

Title:
  CD-ROM tray opens on wake from suspend on Ubuntu 20.04 LTS Focal

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

Bug description:
  I'm using Ubuntu 20.04.3 LTS amd64.
  Updating to kernel 5.4.0-84 seems to have been the cause.

  It's a known bug in the Linux kernel

  This is the upstream bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=213795

  There's a patch there too.

  Related launchpad bugs:

  After hibernation #1943379
  https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1943379

  On Impish #1942299
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942299

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1943616/+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 1937897] Re: GPIO error logs in start and dmesg after update of kernel

[Saša Marjanović]

I've just updated to kernel 5.11.0-36.40~20.04.1 (I'm on HWE stack on
Linux Mint 20.2). I'm still getting the same log errors as OP reported.

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

Title:
  GPIO error logs in start and dmesg after update of kernel

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

Bug description:
  [Impact]
  After upgrade kernel to 5.11.0-25 which introduce some ODM patches from 
AAEON, user encounters below errors
  [   5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  [Fix]
  AAEON provides a patch to check the BFPI version before loading the driver.
  Which fixes the issue introduced by
  Hirsute:
 45a8bb8699cc UBUNTU: ODM: mfd: Add support for IO functions of AAEON 
devices
  Impish:
 424945128781 UBUNTU: ODM: mfd: Add support for IO functions of AAEON 
devices

  
  [Test]
  Verified by AAEON.

  [Where problems could occur]
  It adds a check while probing the driver, should have no impact to normal 
user.

  =

  After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error
  to gpio:

     5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  On pc:

  description: Desktop Computer
  product: System Product Name (SKU)
  vendor: ASUS
  version: System Version
  serial: System Serial Number
  width: 64 bits
  capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32
  configuration: boot=normal chassis=desktop family=To be filled by O.E.M. 
sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4
    *-core
     description: Motherboard
     product: TUF GAMING B550M-PLUS (WI-FI)
     vendor: ASUSTeK COMPUTER INC.
     physical id: 0
     version: Rev X.0x
     serial: 201176738701636
     slot: Default string
   *-firmware
    description: BIOS
    vendor: American Megatrends Inc.
    physical id: 0
    version: 2403
    date: 06/16/2021
    size: 64KiB
    capacity: 16MiB
    capabilities: pci apm upgrade shadowing cdboot bootselect 
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen 
int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
   *-memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+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 1944389] Re: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz

[Brian Murray]

** Tags added: regression-update

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

Title:
  Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz

Status in thermald package in Ubuntu:
  New

Bug description:
  After update to 1.9.1-1ubuntu0.6 from 1.9.1-1ubuntu0.4 thermald keeps 
Tigerlake Iris Xe GPU frequency on 400 MHz after reaching some high temperature 
value. It became impossible to play video games on the laptop.
  System: Ubuntu 20.04.3 LTS
  Kernel: 5.10.0-1045-oem
  Laptop: Dell XPS 9310, CPU: Intel Core i7-1165G7 (Tigerlake), Integrated GPU 
Iris Xe.
  BIOS 2.1.1 03/25/2021
  Display: 2560x1440 144Hz HDMI USB-C connection
  Room temperature is 23.5-25.4 degrees
  Game: Stalker Clear Sky (Wine/Proton Steam)
  Note: The game itself is very old and loads 100% of one CPU core disregarding 
of frequency.

  GPU frequency is monitored by intel-gpu-top
  GPU frequencies (according to /sys/class/drm/card0/) 
min/max/boost/efficiency: 100/1300/1300/400

  Previous behavior (1.9.1-1ubuntu0.4)
  After starting the game at first GPU reaches the boost value of 1300 MHz and 
CPU/package temperatures continuously increase. At this point game renders at 
~80FPS. 
  After some time when threshold temperature value (~78 degrees) is reached the 
GPU frequency decreases to ~660 MHz and FPS to 40-48 FPS. Package temperature 
decreases to 66-68 degrees. It's possible to play for indefinite amount of time.

  New behavior (1.9.1-1ubuntu0.4)
  After starting the game at first GPU reaches the boost value of 1300 MHz and 
CPU/package temperatures continuously increase. At this point game renders at 
~80FPS.
  But after reaching the threshold temperature (about 81 degrees) GPU frequency 
decreases to 400 MHz (gt_RP1_freq_mhz -- "efficiency" temperature for the GPU) 
and stays on this value for the indefinite amount of time. The temperature is 
maintained on 70-74 degrees. FPS is about 25-30 FPS, it is not possible to play 
the game anymore. The only way to return the good FPS and frequency is to fold 
the game window, wait some time and open it again.

  
  Also there is a workaround -- limit the CPU frequency to 2001 MHz and disable 
Intel turbo boost. With such approach package temperature never reaches 80 
degrees and it is possible to play game with 500 MHz and 35-40 FPS. Better than 
nothing.

  
  If it is needed I can perform any additional checks, provide CPU frequencies 
and so on. Most probably regression happened with 1.9.1-1ubuntu0.5, but I tried 
only versions 0.4 and 0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389/+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 1786013] Autopkgtest regression report (linux-meta-kvm/4.15.0.1100.96)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-kvm (4.15.0.1100.96) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64)
kpatch/0.5.0-0ubuntu1.1 (amd64)
ddcci-driver-linux/0.3.1-2ubuntu0.1 (amd64)
glibc/2.27-3ubuntu1.4 (amd64)
lttng-modules/2.10.8-1ubuntu2~18.04.3 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-kvm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

[Rex Tsai]

Hi,

WW38.2'21: Confirmed Intel LAN issue; promoted to LAN engineering. Please see 
further details below.
Please verify the issue again with FIA wa.7z, which should be final solution 
candidate.

Root cause:

The power management flow on TGL shut down a clock that is required for
exiting from K1 (K1 Is the equivalent of L1 for the proprietary PCIe
like interface between the MAC and the PHY).

Due to missing configuration, the clock request was not asserted
properly which caused a long K1 exit latency which is the reason for the
performance issue.

Solution:

Update the HW MAC initialization flow. Do not gate DMA clock from the
modPHY block. Keeping this clock will prevent drop packets sent in burst
mode on the Kumaran interface.

** Attachment added: "FIA wa.7z"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927925/+attachment/5526765/+files/FIA%20wa.7z

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

Title:
  Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently got a Thinkpad T14 Gen2 with a I219-V network adapter
  (8086:15fc). I get very slow connection speeds and even total loss of
  connectivity without seeing much in the logs (like dmesg etc.).
  ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel
  5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried
  the e1000e driver directly from upstream (3.8.7) with no success.

  A strange behaviour I observed: if connectivity is lost (notebook is
  not reachable via ping from another host), if I do something like
  "ping 8.8.8.8" on the notebook itself, it becomes reachable from the
  other host again.

  Downloads in general are very slow if they work at all.

  WLAN (AX210) seems to work fine, wired network using a USB-network adapter 
works fine, too.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros3285 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-05-07 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20W0004MGE
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0004MGE
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros1673 F pulseaudio
   /dev/snd/controlC1:  ros1673 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-05-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20W0004MGE
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   

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

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

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

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

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

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

Title:
  System Lockup during failover

Status in linux package in Ubuntu:
  Incomplete
Status in multipath-tools package in Ubuntu:
  Confirmed

Bug description:
  When testing failover for configured multipath devices, I am seeing
  some nodes lock up and become unresponsive.  These nodes have frozen
  consoles, but can be pinged.  So some of the network stack is
  functional, but ssh is not possible to them.

  1) 20.04 focal
  2) 0.8.3-1ubuntu2
  3) multipathing failover would be successful across all nodes and the nodes 
would continue to be responsive
  4) some of the nodes lock up when attempting to failover and cannot be 
reached via ssh or console

  Here is the ubuntu-bug output:
  https://pastebin.canonical.com/p/6MyWBggtS2/

  Here is the kern.log: https://pastebin.canonical.com/p/rG42gzXG9X/

  Here is the syslog: https://pastebin.canonical.com/p/C99ZprphZn/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944005/+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 1944005] Re: System Lockup during failover

[jarred wilson]

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

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

Title:
  System Lockup during failover

Status in linux package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  Confirmed

Bug description:
  When testing failover for configured multipath devices, I am seeing
  some nodes lock up and become unresponsive.  These nodes have frozen
  consoles, but can be pinged.  So some of the network stack is
  functional, but ssh is not possible to them.

  1) 20.04 focal
  2) 0.8.3-1ubuntu2
  3) multipathing failover would be successful across all nodes and the nodes 
would continue to be responsive
  4) some of the nodes lock up when attempting to failover and cannot be 
reached via ssh or console

  Here is the ubuntu-bug output:
  https://pastebin.canonical.com/p/6MyWBggtS2/

  Here is the kern.log: https://pastebin.canonical.com/p/rG42gzXG9X/

  Here is the syslog: https://pastebin.canonical.com/p/C99ZprphZn/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944005/+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 1935855] Re: dbgsym contains no debug symbols

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-kvm/5.4.0-1047.49
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

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

Title:
  dbgsym contains no debug symbols

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

Bug description:
  [Impact]

  linux-image-unsigned-5.4.0-77-generic-dbgsym provides a
  /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm, but it does not contain
  any debug symbols.

  Turn on CONFIG_DEBUG_INFO to include those debug symbols.

  [Test Case]

  Compare:

  $ file /usr/lib/debug/boot/vmlinux-*
  /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm:   ELF 64-bit LSB executable, 
x86-64, version 1 (SYSV), statically linked, 
BuildID[sha1]=514891d64a7d18db4fa58aa5cfea213e0951ca9d, not stripped
  /usr/lib/debug/boot/vmlinux-5.4.0-77-generic: ELF 64-bit LSB executable, 
x86-64, version 1 (SYSV), statically linked, 
BuildID[sha1]=773d8ee85333fe092635f65d2b6850909085c11d, with debug_info, not 
stripped

  [What Could Go Wrong]

  Since linux-kvm is tuned for performance, it's possible there's some
  side-effect of producing debug symbols that negatively impacts this. I've not
  noticed any issues empirically, but I didn't try to measure it.

  This config is already successfully turned on in Hirsute/kvm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1935855/+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 1942633] Re: Can not boot impish in Cavium ThunderX

[dann frazier]

Root caused and reported upstream:
 https://www.spinics.net/lists/arm-kernel/msg921821.html

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

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

Title:
  Can not boot impish in Cavium ThunderX

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic
  5.11.7) in

  arm64
  description: Computer
  product: Cavium ThunderX CN88XX board
  width: 64 bits

  
  I tried 2 releases:
   - 20210817 ( 
https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ )
   - 20210830 ( 
https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ )

  
  20210817:
   Ends the deploy successfully but fails to boot from disk:

  ```
  [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11]
  [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc 
(Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) 
#14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1)
  [0.00] Machine model: Cavium ThunderX CN88XX board
  
  [  139.896752] raid6:  xor() 1224 MB/s, rmw enabled
  [  139.957046] raid6: using neon recovery algorithm
  [  140.020937] xor: measuring software checksum speed
  [  140.085571]8regs   :  2432 MB/sec
  [  140.149834]32regs  :  2687 MB/sec
  [  140.212202]arm64_neon  :  4390 MB/sec
  [  140.271985] xor: using function: arm64_neon (4390 MB/sec)
  [  140.335013] async_tx: api initialized (async)
  done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
done.
  Begin: Running /scripts/local-premount ... [  140.569847] Btrfs loaded, 
crc32c=crc32c-generic, zoned=yes
  Scanning for Btrfs filesystems
  done.
  Begin: Waiting for root file system ... Begin: Running /scripts/local-block 
... mdadm: No devices listed in conf file were found.
  done.
  mdadm: No devices listed in conf file were found.
  ```

  
  20210830

  Fails the network boot:
  ```
  [  140.351066] async_tx: api initialized (async)
  done.
  Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no 
find a nic with 1c:1b:0d:0d:52:7c
  done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: 
Interface BOOTIF did not appear in time
  done.
  ipconfig: BOOTIF: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ```

  I will attach full logs of each try.

  JFYI, this is the same machine as
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+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 1943960] Re: s390x BPF JIT vulnerabilities

[Thadeu Lima de Souza Cascardo]

** Information type changed from Private Security to Public Security

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

Title:
  s390x BPF JIT vulnerabilities

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  s390 BPF JIT vulnerabilities allow the eBPF verifier to be bypassed, leading 
to possible local privilege escalation.

  [Mitigation]
  Disable unprivileged eBPF.
  sysctl -w kernel.unprivileged_bpf_disabled=1

  [Potential regression]
  BPF programs might execute incorrectly, affecting seccomp, socket filters, 
tracing and other BPF users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943960/+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 1786013] Autopkgtest regression report (linux-meta-raspi-5.4/5.4.0.1044.47)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1044.47) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/unknown (arm64)
acpi-call/unknown (arm64)
bbswitch/0.8-4ubuntu1 (arm64)
v4l2loopback/unknown (arm64)
dm-writeboost/unknown (arm64)
langford/unknown (arm64)
west-chamber/unknown (arm64)
glibc/unknown (arm64)
ktap/unknown (arm64)
dpdk/unknown (arm64)
ddcci-driver-linux/unknown (arm64)
wireguard-linux-compat/unknown (arm64)
zfs-linux/unknown (arm64)
xtables-addons/unknown (arm64)
nat-rtsp/unknown (arm64)
spl-linux/unknown (arm64)
lxc/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-raspi-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1935855] Re: dbgsym contains no debug symbols

[dann frazier]

= verification =
root@dannf-lp1935855:~# wget 
https://launchpad.net/ubuntu/+archive/primary/+files/linux-image-4.15.0-1100-kvm-dbgsym_4.15.0-1100.102_amd64.ddeb
--2021-09-21 17:13:41--  
https://launchpad.net/ubuntu/+archive/primary/+files/linux-image-4.15.0-1100-kvm-dbgsym_4.15.0-1100.102_amd64.ddeb
Resolving launchpad.net (launchpad.net)... 91.189.89.223, 91.189.89.222, 
2001:67c:1560:8003::8004, ...
Connecting to launchpad.net (launchpad.net)|91.189.89.223|:443... connected.
HTTP request sent, awaiting response... 303 See Other
Location: 
https://launchpadlibrarian.net/559404908/linux-image-4.15.0-1100-kvm-dbgsym_4.15.0-1100.102_amd64.ddeb
 [following]
--2021-09-21 17:13:41--  
https://launchpadlibrarian.net/559404908/linux-image-4.15.0-1100-kvm-dbgsym_4.15.0-1100.102_amd64.ddeb
Resolving launchpadlibrarian.net (launchpadlibrarian.net)... 91.189.89.228, 
91.189.89.229, 2001:67c:1560:8003::8008, ...
Connecting to launchpadlibrarian.net 
(launchpadlibrarian.net)|91.189.89.228|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 131805596 (126M) [application/octet-stream]
Saving to: ‘linux-image-4.15.0-1100-kvm-dbgsym_4.15.0-1100.102_amd64.ddeb’

linux-image-4.15.0- 100%[===>] 125.70M  30.3MB/sin
7.2s

2021-09-21 17:13:49 (17.5 MB/s) - ‘linux-image-4.15.0-1100-kvm-
dbgsym_4.15.0-1100.102_amd64.ddeb’ saved [131805596/131805596]

root@dannf-lp1935855:~# dpkg -i 
linux-image-4.15.0-1100-kvm-dbgsym_4.15.0-1100.102_amd64.ddeb 
Selecting previously unselected package linux-image-4.15.0-1100-kvm-dbgsym.
(Reading database ... 33352 files and directories currently installed.)
Preparing to unpack 
linux-image-4.15.0-1100-kvm-dbgsym_4.15.0-1100.102_amd64.ddeb ...
Unpacking linux-image-4.15.0-1100-kvm-dbgsym (4.15.0-1100.102) ...
Setting up linux-image-4.15.0-1100-kvm-dbgsym (4.15.0-1100.102) ...
root@dannf-lp1935855:~# apt -f install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 40 not upgraded.
root@dannf-lp1935855:~# file /usr/lib/debug/boot/vmlinux-4.15.0-1100-kvm 
/usr/lib/debug/boot/vmlinux-4.15.0-1100-kvm: ELF 64-bit LSB executable, x86-64, 
version 1 (SYSV), statically linked, 
BuildID[sha1]=2ef10554e712a31bd03eba202c31d1e9fda95eab, with debug_info, not 
stripped


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

** Description changed:

  [Impact]
  
  linux-image-unsigned-5.4.0-77-generic-dbgsym provides a
  /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm, but it does not contain any
  debug symbols.
  
  Turn on CONFIG_DEBUG_INFO to include those debug symbols.
  
  [Test Case]
  
  Compare:
  
  $ file /usr/lib/debug/boot/vmlinux-*
  /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm:   ELF 64-bit LSB executable, 
x86-64, version 1 (SYSV), statically linked, 
BuildID[sha1]=514891d64a7d18db4fa58aa5cfea213e0951ca9d, not stripped
  /usr/lib/debug/boot/vmlinux-5.4.0-77-generic: ELF 64-bit LSB executable, 
x86-64, version 1 (SYSV), statically linked, 
BuildID[sha1]=773d8ee85333fe092635f65d2b6850909085c11d, with debug_info, not 
stripped
  
  [What Could Go Wrong]
  
  Since linux-kvm is tuned for performance, it's possible there's some
  side-effect of producing debug symbols that negatively impacts this. I've not
  noticed any issues empirically, but I didn't try to measure it.
  
- This config is already succesfully turned on in Hirsute/kvm.
+ This config is already successfully turned on in Hirsute/kvm.

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

Title:
  dbgsym contains no debug symbols

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

Bug description:
  [Impact]

  linux-image-unsigned-5.4.0-77-generic-dbgsym provides a
  /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm, but it does not contain
  any debug symbols.

  Turn on CONFIG_DEBUG_INFO to include those debug symbols.

  [Test Case]

  Compare:

  $ file /usr/lib/debug/boot/vmlinux-*
  /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm:   ELF 64-bit LSB executable, 
x86-64, version 1 (SYSV), statically linked, 
BuildID[sha1]=514891d64a7d18db4fa58aa5cfea213e0951ca9d, not stripped
  /usr/lib/debug/boot/vmlinux-5.4.0-77-generic: ELF 64-bit LSB executable, 
x86-64, version 1 (SYSV), statically linked, 
BuildID[sha1]=773d8ee85333fe092635f65d2b6850909085c11d, with debug_info, not 
stripped

  [What Could Go Wrong]

  Since linux-kvm is tuned for performance, it's possible there's some
  side-effect of producing 

[Kernel-packages] [Bug 1943915] Re: Intel IPU6 GStreamer src plugin not working

[Stefan]

I have managed to compile locally from:
https://github.com/intel/icamerasrc/tree/icamerasrc_slim_api
and got the camera to work with gst-launch-1.0
sudo -E gst-launch-1.0 icamerasrc device-name=ov01a1s-uf ! 
video/x-raw,format=YUY2,width=1280,height=720 ! videoconvert ! xvimagesink

Note: I need to run this command with sudo.

I have no idea what's required to get cheese and ffplay and other
application to work properly.

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

Title:
  Intel IPU6 GStreamer src plugin not working

Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.13 source package in Focal:
  New

Bug description:
  The device is properly detected but it seems there are still issues
  with gstreamer plugin. When I try to run cheese I get the following
  error message:

  ../src/intel/isl/isl.c:2018: FINISHME:
  ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is
  disabled, but a workaround is available.

  (cheese:3769): cheese-WARNING **: 08:02:37.506: Failed to allocate required 
memory.: gstv4l2src.c(660): gst_v4l2src_decide_allocation (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1:
  Buffer pool activation failed

  
  With VLC I get
  stefang@capella:~$ vlc v4l2:///dev/video0
  VLC media player 3.0.9.2 Vetinari (revision 3.0.9.2-0-gd4c1aefe4d)
  [55cfdb6a3670] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230001160] v4l2 demux error: cannot start streaming: Link has been 
severed
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: not a radio tuner device
  Using mplane plugin for capture 
  [7f0230007b70] v4l2 stream error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230007b70] v4l2 stream error: cannot start streaming: Link has been 
severed
  QObject::~QObject: Timers cannot be stopped from another thread

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-1012-oem 5.13.0-1012.16
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  Uname: Linux 5.13.0-1012-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Sep 17 07:59:51 2021
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-oem-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stefang1469 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. Latitude 9420
  Package: linux-oem-5.13 (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1012-oem 
root=UUID=e2704fd1-5330-4b87-9cdf-a353f5fe73b7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-1012-oem N/A
   linux-backports-modules-5.13.0-1012-oem  N/A
   linux-firmware   1.187.16
  Tags:  focal
  Uname: Linux 5.13.0-1012-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/13/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.2
  dmi.board.name: 08XKF8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd04/13/2021:br1.2:svnDellInc.:pnLatitude9420:pvr:sku0A32:rvnDellInc.:rn08XKF8:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9420
  dmi.product.sku: 0A32
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1943915/+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 1935855] Re: dbgsym contains no debug symbols

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-kvm/4.15.0-1100.102
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-bionic' to 'verification-done-bionic'. If the
problem still exists, change the tag 'verification-needed-bionic' to
'verification-failed-bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  dbgsym contains no debug symbols

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

Bug description:
  [Impact]

  linux-image-unsigned-5.4.0-77-generic-dbgsym provides a
  /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm, but it does not contain
  any debug symbols.

  Turn on CONFIG_DEBUG_INFO to include those debug symbols.

  [Test Case]

  Compare:

  $ file /usr/lib/debug/boot/vmlinux-*
  /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm:   ELF 64-bit LSB executable, 
x86-64, version 1 (SYSV), statically linked, 
BuildID[sha1]=514891d64a7d18db4fa58aa5cfea213e0951ca9d, not stripped
  /usr/lib/debug/boot/vmlinux-5.4.0-77-generic: ELF 64-bit LSB executable, 
x86-64, version 1 (SYSV), statically linked, 
BuildID[sha1]=773d8ee85333fe092635f65d2b6850909085c11d, with debug_info, not 
stripped

  [What Could Go Wrong]

  Since linux-kvm is tuned for performance, it's possible there's some
  side-effect of producing debug symbols that negatively impacts this. I've not
  noticed any issues empirically, but I didn't try to measure it.

  This config is already succesfully turned on in Hirsute/kvm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1935855/+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 1943469] Re: [Asus X541NC] wakes up from sleep mode after 1 second

[João Sousa]

Well, i tried installing nvidia but nothing changed. I am going now to
try to disable those controllers. But aren't they going to mess other
things in computer? Can you please tell me how to enable them if
something goes not right?

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

Title:
  [Asus X541NC] wakes up from sleep mode after 1 second

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

Bug description:
  computer "wakes up" from sleep mode after 1 second no matter if i wait
  the given time for it to sleep, or if i put it to sleep with terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 13 18:56:14 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 
Series Integrated Graphics Controller [1043:16a0]
 Subsystem: ASUSTeK Computer Inc. GK107M [GeForce 810M] [1043:137e]
  InstallationDate: Installed on 2021-07-30 (44 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam
   Bus 001 Device 002: ID 0bda:b721 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541NC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=264f931b-e96b-44e9-a13d-bf5c3236a567 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541NC.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541NC
  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.:bvrX541NC.307:bd06/19/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX541NC:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX541NC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541NC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943469/+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 1942633] Re: Can not boot impish in Cavium ThunderX

[dann frazier]

Update: The issue does not follow toolchain, which is good. Rather I did
find that upstream v5.13-rc1 is stable - with the patch in comment #15
reverted - while upstream v5.13 is not. I bisected v5.13-rc1..v5.13,
reverting the comment #15 patch at each test. A "bad" kernel wouldn't
always fail the same way, but would always fail before completing boot.
The bisect hit this commit:

commit 0c6c2d3615efb7c292573f2e6c886929a2b2da6c (HEAD, refs/bisect/bad)
Author: Mark Brown 
Date:   Wed Apr 28 13:12:31 2021 +0100

arm64: Generate cpucaps.h

While this looks innocuous, it is messing with the code that chooses
which "features" a CPU has, which includes erratum that may need kernel
workarounds. So I went back and compared the CPU features messages
between a "good" kernel and a "bad" one. Noticeably missing from a "bad"
one was this message:

[0.00] CPU features: kernel page table isolation forced OFF by
ARM64_WORKAROUND_CAVIUM_27456

I went back and tested Ubuntu's 5.13.0-16 w/ kpti=off, and it booted
fine. As does upstream v5.15-rc2, where previously I was also seeing
stack overflows/corruption. So, seems like the above change is likely
the problem, next step is to figure out why.

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

Title:
  Can not boot impish in Cavium ThunderX

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic
  5.11.7) in

  arm64
  description: Computer
  product: Cavium ThunderX CN88XX board
  width: 64 bits

  
  I tried 2 releases:
   - 20210817 ( 
https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ )
   - 20210830 ( 
https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ )

  
  20210817:
   Ends the deploy successfully but fails to boot from disk:

  ```
  [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11]
  [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc 
(Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) 
#14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1)
  [0.00] Machine model: Cavium ThunderX CN88XX board
  
  [  139.896752] raid6:  xor() 1224 MB/s, rmw enabled
  [  139.957046] raid6: using neon recovery algorithm
  [  140.020937] xor: measuring software checksum speed
  [  140.085571]8regs   :  2432 MB/sec
  [  140.149834]32regs  :  2687 MB/sec
  [  140.212202]arm64_neon  :  4390 MB/sec
  [  140.271985] xor: using function: arm64_neon (4390 MB/sec)
  [  140.335013] async_tx: api initialized (async)
  done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
done.
  Begin: Running /scripts/local-premount ... [  140.569847] Btrfs loaded, 
crc32c=crc32c-generic, zoned=yes
  Scanning for Btrfs filesystems
  done.
  Begin: Waiting for root file system ... Begin: Running /scripts/local-block 
... mdadm: No devices listed in conf file were found.
  done.
  mdadm: No devices listed in conf file were found.
  ```

  
  20210830

  Fails the network boot:
  ```
  [  140.351066] async_tx: api initialized (async)
  done.
  Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no 
find a nic with 1c:1b:0d:0d:52:7c
  done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: 
Interface BOOTIF did not appear in time
  done.
  ipconfig: BOOTIF: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ```

  I will attach full logs of each try.

  JFYI, this is the same machine as
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+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 1786013] Autopkgtest regression report (linux-meta-raspi2/4.15.0.1096.94)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-raspi2 (4.15.0.1096.94) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

r8168/unknown (arm64)
systemd/unknown (arm64)
lttng-modules/unknown (arm64)
rtl8821ce/unknown (arm64)
rtl8821ce/5.5.2.1-0ubuntu3~18.04.1 (armhf)
langford/unknown (arm64)
snapd/unknown (arm64)
langford/0.0.20130228-5ubuntu1 (armhf)
lime-forensics/unknown (arm64)
adv-17v35x/unknown (arm64)
wireguard-linux-compat/unknown (arm64)
fwts/unknown (arm64)
rtl8812au/unknown (arm64)
acpi-call/unknown (arm64)
xtables-addons/unknown (arm64)
west-chamber/unknown (arm64)
glibc/unknown (arm64)
nat-rtsp/unknown (arm64)
v4l2loopback/unknown (arm64)
dm-writeboost/unknown (arm64)
zfs-linux/unknown (arm64)
bbswitch/unknown (arm64)
ktap/unknown (arm64)
spl-linux/unknown (arm64)
r8168/8.045.08-2ubuntu1 (armhf)
ddcci-driver-linux/unknown (arm64)
asic0x/unknown (arm64)
dpdk/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-raspi2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1944435] acpidump.txt

[David Ober]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1944435/+attachment/5526690/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] ProcModules.txt

[David Ober]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1944435/+attachment/5526685/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] PulseList.txt

[David Ober]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1944435/+attachment/5526686/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] RfKill.txt

[David Ober]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1944435/+attachment/5526687/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] Lsusb-t.txt

[David Ober]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1944435/+attachment/5526680/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] WifiSyslog.txt

[David Ober]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1944435/+attachment/5526689/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] ProcCpuinfoMinimal.txt

[David Ober]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1944435/+attachment/5526683/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] ProcInterrupts.txt

[David Ober]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1944435/+attachment/5526684/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] UdevDb.txt

[David Ober]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1944435/+attachment/5526688/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] CRDA.txt

[David Ober]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1944435/+attachment/5526674/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] Lsusb-v.txt

[David Ober]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1944435/+attachment/5526681/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] Lspci-vt.txt

[David Ober]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1944435/+attachment/5526678/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] IwConfig.txt

[David Ober]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1944435/+attachment/5526676/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] ProcCpuinfo.txt

[David Ober]

apport information

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

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

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] Lsusb.txt

[David Ober]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1944435/+attachment/5526679/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] CurrentDmesg.txt

[David Ober]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1944435/+attachment/5526675/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] Lspci.txt

[David Ober]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1944435/+attachment/5526677/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] Re: Backlight on P17 Gen 1 not working Nvidia 470

[David Ober]

apport information

** Tags added: apport-collected focal

** Description changed:

- Updated to the Nvidia 460 driver and backlight (screen brightness) was
- not working so updated to the 470.63.01 before opening ticket as it also
- is not wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was
- working fine before the updates
+ Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.20
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  z  2151 F pulseaudio
+  /dev/snd/controlC1:  z  2151 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistributionChannelDescriptor:
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2021-01-04 (259 days ago)
+ InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
+ MachineType: LENOVO 20SNZ5GCUS
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
+ ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
+ RelatedPackageVersions:
+  linux-restricted-modules-5.11.0-34-generic N/A
+  linux-backports-modules-5.11.0-34-generic  N/A
+  linux-firmware 1.187.16
+ Tags:  focal
+ Uname: Linux 5.11.0-34-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/03/2021
+ dmi.bios.release: 1.23
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N30ET40W (1.23 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20SNZ5GCUS
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40697 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.ec.firmware.release: 1.11
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad P17 Gen 1
+ dmi.product.name: 20SNZ5GCUS
+ dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
+ dmi.product.version: ThinkPad P17 Gen 1
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1944435/+attachment/5526673/+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/1944435

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   

[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops

[Kuroš Taheri-Golværzi]

And, I'm honestly hesitant to suspect Nvidia, because I also use Nvidia
470 on my Kubuntu installation. I very clearly remember installing 470
because I use Kubuntu for gaming, and I had to update my Nvidia drivers
for a couple of games to work properly. I'll find out how it goes,
though.

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

Title:
  [Asus TUF Gaming FA506IV] Random system stops

Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Every once in a while (it's been three times this week), the entire
  system will just stop. There's still electricity running. The keyboard
  is lit up, and the monitor is black (electricity-running black, and
  not shutdown-black). There's no picture and no sound. Just immediately
  before it does, I know it's about to happen because whatever audio is
  playing at the time will begin repeating, and then the computer goes
  down. I don't actually know if it's an Xorg problem. It just sounded
  like the closest possibility, based on the way the computer actually
  behaves.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  470.57.02  Tue Jul 13 
16:14:05 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Aug 14 19:34:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed
   nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed
   virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed
   virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2021-03-20 (147 days ago)
  InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  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.9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug 

[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops

[Kuroš Taheri-Golværzi]

Also, here's a report from yesterday's third crash. Hopefully, there's
some useful information in it.

** Attachment added: "prevboot-2021-09-20-c.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939966/+attachment/5526672/+files/prevboot-2021-09-20-c.txt

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

Title:
  [Asus TUF Gaming FA506IV] Random system stops

Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Every once in a while (it's been three times this week), the entire
  system will just stop. There's still electricity running. The keyboard
  is lit up, and the monitor is black (electricity-running black, and
  not shutdown-black). There's no picture and no sound. Just immediately
  before it does, I know it's about to happen because whatever audio is
  playing at the time will begin repeating, and then the computer goes
  down. I don't actually know if it's an Xorg problem. It just sounded
  like the closest possibility, based on the way the computer actually
  behaves.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  470.57.02  Tue Jul 13 
16:14:05 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Aug 14 19:34:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed
   nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed
   virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed
   virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2021-03-20 (147 days ago)
  InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  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.9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops

[Kuroš Taheri-Golværzi]

I tried purging `nvidia-*` and installed `nvidia-driver-460` (since when
I kept trying to install -465, it kept installing -470. So, I'll find
how that goes.

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

Title:
  [Asus TUF Gaming FA506IV] Random system stops

Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Every once in a while (it's been three times this week), the entire
  system will just stop. There's still electricity running. The keyboard
  is lit up, and the monitor is black (electricity-running black, and
  not shutdown-black). There's no picture and no sound. Just immediately
  before it does, I know it's about to happen because whatever audio is
  playing at the time will begin repeating, and then the computer goes
  down. I don't actually know if it's an Xorg problem. It just sounded
  like the closest possibility, based on the way the computer actually
  behaves.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  470.57.02  Tue Jul 13 
16:14:05 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Aug 14 19:34:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed
   nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed
   virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed
   virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2021-03-20 (147 days ago)
  InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  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.9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


-- 
Mailing list: 

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

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

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

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

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

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

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was
  not working so updated to the 470.63.01 before opening ticket as it
  also is not wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It
  was working fine before the updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] [NEW] Backlight on P17 Gen 1 not working Nvidia 470

[David Ober]

Public bug reported:

Updated to the Nvidia 460 driver and backlight (screen brightness) was
not working so updated to the 470.63.01 before opening ticket as it also
is not wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was
working fine before the updates

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

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

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  New

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was
  not working so updated to the 470.63.01 before opening ticket as it
  also is not wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It
  was working fine before the updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1943915] Re: Intel IPU6 GStreamer src plugin not working

[Stefan]

I have managed to compile the GST plugin locally from:
https://github.com/intel/icamerasrc/tree/icamerasrc_slim_api
after reverting:
https://github.com/intel/icamerasrc/commit/329ec92139f26594a00681c2a048c31c3de498d8

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

Title:
  Intel IPU6 GStreamer src plugin not working

Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.13 source package in Focal:
  New

Bug description:
  The device is properly detected but it seems there are still issues
  with gstreamer plugin. When I try to run cheese I get the following
  error message:

  ../src/intel/isl/isl.c:2018: FINISHME:
  ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is
  disabled, but a workaround is available.

  (cheese:3769): cheese-WARNING **: 08:02:37.506: Failed to allocate required 
memory.: gstv4l2src.c(660): gst_v4l2src_decide_allocation (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1:
  Buffer pool activation failed

  
  With VLC I get
  stefang@capella:~$ vlc v4l2:///dev/video0
  VLC media player 3.0.9.2 Vetinari (revision 3.0.9.2-0-gd4c1aefe4d)
  [55cfdb6a3670] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230001160] v4l2 demux error: cannot start streaming: Link has been 
severed
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: not a radio tuner device
  Using mplane plugin for capture 
  [7f0230007b70] v4l2 stream error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230007b70] v4l2 stream error: cannot start streaming: Link has been 
severed
  QObject::~QObject: Timers cannot be stopped from another thread

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-1012-oem 5.13.0-1012.16
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  Uname: Linux 5.13.0-1012-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Sep 17 07:59:51 2021
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-oem-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stefang1469 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. Latitude 9420
  Package: linux-oem-5.13 (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1012-oem 
root=UUID=e2704fd1-5330-4b87-9cdf-a353f5fe73b7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-1012-oem N/A
   linux-backports-modules-5.13.0-1012-oem  N/A
   linux-firmware   1.187.16
  Tags:  focal
  Uname: Linux 5.13.0-1012-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/13/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.2
  dmi.board.name: 08XKF8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd04/13/2021:br1.2:svnDellInc.:pnLatitude9420:pvr:sku0A32:rvnDellInc.:rn08XKF8:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9420
  dmi.product.sku: 0A32
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1943915/+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 1944425] Re: touchpad isn't working at all since its installation but it is used to work with windows

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  touchpad isn't working at all since its installation but it is used to
  work with windows

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

Bug description:
  i've recently installled ubuntu 20.04 on my lenovo ideapad 3 15iil
  since its installation laptop's touchpad isn't working at all. But it
  does work really well with remote touchpad.

  this is what i got when i run "xinput"

  
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=9[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 21 15:16:56 2021
  InstallationDate: Installed on 2021-09-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1944425/+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 1944425] [NEW] touchpad isn't working at all since its installation but it is used to work with windows

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

i've recently installled ubuntu 20.04 on my lenovo ideapad 3 15iil since
its installation laptop's touchpad isn't working at all. But it does
work really well with remote touchpad.

this is what i got when i run "xinput"


⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ Integrated Camera: Integrated C   id=9[slave  keyboard (3)]
↳ Ideapad extra buttons id=10   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)]

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 21 15:16:56 2021
InstallationDate: Installed on 2021-09-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal
-- 
touchpad isn't working at all since its installation but it is used to work 
with windows
https://bugs.launchpad.net/bugs/1944425
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-signed-hwe-5.11 in Ubuntu.

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

[Kernel-packages] [Bug 1943915] Re: Intel IPU6 GStreamer src plugin not working

[Stefan]

I needed to install libdrm-dev when trying to locally compile 
gst-plugins-icamera even with libdrm-dev installed the compilation fails with:
utils.cpp:64:41: error: ‘V4L2_PIX_FMT_P010’ was not declared in this scope; did 
you mean ‘V4L2_PIX_FMT_Y10’?
   64 |   { "P010", GST_VIDEO_FORMAT_P010_10BE, V4L2_PIX_FMT_P010 },
  | ^
  | V4L2_PIX_FMT_Y10
utils.cpp: In function ‘int CameraSrcUtils::get_number_of_valid_lines(int, 
int)’:
utils.cpp:123:10: error: ‘V4L2_PIX_FMT_P010’ was not declared in this scope; 
did you mean ‘V4L2_PIX_FMT_Y10’?
  123 | case V4L2_PIX_FMT_P010:
  |  ^
  |  V4L2_PIX_FMT_Y10
make[4]: *** [Makefile:670: libgsticamerasrc_la-utils.lo] Error 1
make[4]: *** Waiting for unfinished jobs
gstcameraformat.cpp: In function ‘GstStructure* create_structure(guint32)’:
gstcameraformat.cpp:154:10: error: ‘V4L2_PIX_FMT_P010’ was not declared in this 
scope; did you mean ‘V4L2_PIX_FMT_Y10’?
  154 | case V4L2_PIX_FMT_P010:{
  |  ^
  |  V4L2_PIX_FMT_Y10
make[4]: *** [Makefile:635: libgsticamerasrc_la-gstcameraformat.lo] Error 1
gstcamerasrc.cpp: In function ‘gboolean gst_camerasrc_start(GstCamBaseSrc*)’:
gstcamerasrc.cpp:2688:67: error: too many arguments to function ‘int 
icamera::camera_device_open(int)’
 2688 |   ret = camera_device_open(camerasrc->device_id, camerasrc->num_vc);
  |   ^

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

Title:
  Intel IPU6 GStreamer src plugin not working

Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.13 source package in Focal:
  New

Bug description:
  The device is properly detected but it seems there are still issues
  with gstreamer plugin. When I try to run cheese I get the following
  error message:

  ../src/intel/isl/isl.c:2018: FINISHME:
  ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is
  disabled, but a workaround is available.

  (cheese:3769): cheese-WARNING **: 08:02:37.506: Failed to allocate required 
memory.: gstv4l2src.c(660): gst_v4l2src_decide_allocation (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1:
  Buffer pool activation failed

  
  With VLC I get
  stefang@capella:~$ vlc v4l2:///dev/video0
  VLC media player 3.0.9.2 Vetinari (revision 3.0.9.2-0-gd4c1aefe4d)
  [55cfdb6a3670] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230001160] v4l2 demux error: cannot start streaming: Link has been 
severed
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: not a radio tuner device
  Using mplane plugin for capture 
  [7f0230007b70] v4l2 stream error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230007b70] v4l2 stream error: cannot start streaming: Link has been 
severed
  QObject::~QObject: Timers cannot be stopped from another thread

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-1012-oem 5.13.0-1012.16
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  Uname: Linux 5.13.0-1012-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Sep 17 07:59:51 2021
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-oem-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stefang1469 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. Latitude 9420
  Package: linux-oem-5.13 (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1012-oem 
root=UUID=e2704fd1-5330-4b87-9cdf-a353f5fe73b7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-1012-oem N/A
   

[Kernel-packages] [Bug 1853797] Re: pmu in ubuntu_kvm_unit_tests fails

[Krzysztof Kozlowski]

Found on impish/linux-oracle/5.13.0-1005.7 (instance: VM.Standard2.1) with only 
one FAIL:
FAIL: all counters

** Tags added: 5.13 impish

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

Title:
  pmu in ubuntu_kvm_unit_tests fails

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-oracle package in Ubuntu:
  Confirmed
Status in linux-oracle-5.0 package in Ubuntu:
  Confirmed
Status in linux-oracle-5.4 package in Ubuntu:
  New

Bug description:
  4 failures:
   FAIL: rdpmc: fixed cntr-0
   FAIL: rdpmc: fixed cntr-1
   FAIL: rdpmc: fixed cntr-2
   FAIL: all counters

  
  Test log:
   Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/pmu'
   BUILD_HEAD=e2c275c4
   timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel 
/tmp/tmp.UfviUpwSjB -smp 1 -cpu host # -initrd /tmp/tmp.7jA5GK5kyl
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 45a000
   cr4 = 20
   PMU version: 2
   GP counters: 4
   GP counter width: 48
   Mask length: 7
   Fixed counters: 3
   Fixed counter width: 48
   PASS: core cycles-0
   PASS: core cycles-1
   PASS: core cycles-2
   PASS: core cycles-3
   PASS: instructions-0
   PASS: instructions-1
   PASS: instructions-2
   PASS: instructions-3
   PASS: ref cycles-0
   PASS: ref cycles-1
   PASS: ref cycles-2
   PASS: ref cycles-3
   PASS: llc refference-0
   PASS: llc refference-1
   PASS: llc refference-2
   PASS: llc refference-3
   PASS: llc misses-0
   PASS: llc misses-1
   PASS: llc misses-2
   PASS: llc misses-3
   PASS: branches-0
   PASS: branches-1
   PASS: branches-2
   PASS: branches-3
   PASS: branch misses-0
   PASS: branch misses-1
   PASS: branch misses-2
   PASS: branch misses-3
   PASS: fixed-0
   PASS: fixed-1
   PASS: fixed-2
   PASS: rdpmc: cntr-0
   PASS: rdpmc: fast-0
   PASS: rdpmc: cntr-1
   PASS: rdpmc: fast-1
   PASS: rdpmc: cntr-2
   PASS: rdpmc: fast-2
   PASS: rdpmc: cntr-3
   PASS: rdpmc: fast-3
   FAIL: rdpmc: fixed cntr-0
   PASS: rdpmc: fixed fast-0
   FAIL: rdpmc: fixed cntr-1
   PASS: rdpmc: fixed fast-1
   FAIL: rdpmc: fixed cntr-2
   PASS: rdpmc: fixed fast-2
   FAIL: all counters
   PASS: overflow: cntr-0
   PASS: overflow: status-0
   PASS: overflow: status clear-0
   PASS: overflow: irq-0
   PASS: overflow: cntr-1
   PASS: overflow: status-1
   PASS: overflow: status clear-1
   PASS: overflow: irq-1
   PASS: overflow: cntr-2
   PASS: overflow: status-2
   PASS: overflow: status clear-2
   PASS: overflow: irq-2
   PASS: overflow: cntr-3
   PASS: overflow: status-3
   PASS: overflow: status clear-3
   PASS: overflow: irq-3
   PASS: overflow: cntr-4
   PASS: overflow: status-4
   PASS: overflow: status clear-4
   PASS: overflow: irq-4
   PASS: cmask
   SUMMARY: 67 tests, 4 unexpected failures
   FAIL pmu (67 tests, 4 unexpected failures)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9
  ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21
  Uname: Linux 5.0.0-1005-oracle x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Mon Nov 25 04:29:43 2019
  SourcePackage: linux-signed-oracle
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853797/+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 1943915] Re: Intel IPU6 GStreamer src plugin not working

[Stefan]

It looks like the gst-plugins-icamera failed to build:
https://launchpad.net/~oem-solutions-group/+archive/ubuntu/intel-ipu6/+build/21995982

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

Title:
  Intel IPU6 GStreamer src plugin not working

Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.13 source package in Focal:
  New

Bug description:
  The device is properly detected but it seems there are still issues
  with gstreamer plugin. When I try to run cheese I get the following
  error message:

  ../src/intel/isl/isl.c:2018: FINISHME:
  ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is
  disabled, but a workaround is available.

  (cheese:3769): cheese-WARNING **: 08:02:37.506: Failed to allocate required 
memory.: gstv4l2src.c(660): gst_v4l2src_decide_allocation (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1:
  Buffer pool activation failed

  
  With VLC I get
  stefang@capella:~$ vlc v4l2:///dev/video0
  VLC media player 3.0.9.2 Vetinari (revision 3.0.9.2-0-gd4c1aefe4d)
  [55cfdb6a3670] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230001160] v4l2 demux error: cannot start streaming: Link has been 
severed
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: not a radio tuner device
  Using mplane plugin for capture 
  [7f0230007b70] v4l2 stream error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230007b70] v4l2 stream error: cannot start streaming: Link has been 
severed
  QObject::~QObject: Timers cannot be stopped from another thread

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-1012-oem 5.13.0-1012.16
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  Uname: Linux 5.13.0-1012-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Sep 17 07:59:51 2021
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-oem-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stefang1469 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. Latitude 9420
  Package: linux-oem-5.13 (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1012-oem 
root=UUID=e2704fd1-5330-4b87-9cdf-a353f5fe73b7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-1012-oem N/A
   linux-backports-modules-5.13.0-1012-oem  N/A
   linux-firmware   1.187.16
  Tags:  focal
  Uname: Linux 5.13.0-1012-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/13/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.2
  dmi.board.name: 08XKF8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd04/13/2021:br1.2:svnDellInc.:pnLatitude9420:pvr:sku0A32:rvnDellInc.:rn08XKF8:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9420
  dmi.product.sku: 0A32
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1943915/+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 1943915] Re: Intel IPU6 GStreamer src plugin not working

[Stefan]

I have installed the missing packages from:
ppa:oem-solutions-group/intel-ipu6

Here is the result of the commands you asked for:
stefang@capella:~$ sudo apt-cache policy v4l2-relayd libipu6 libcamhal0
v4l2-relayd:
  Installed: 0~git202104290610.f14d6d4~ubuntu20.04.1
  Candidate: 0~git202104290610.f14d6d4~ubuntu20.04.1
  Version table:
 *** 0~git202104290610.f14d6d4~ubuntu20.04.1 500
500 http://ppa.launchpad.net/oem-solutions-group/intel-ipu6/ubuntu 
focal/main amd64 Packages
100 /var/lib/dpkg/status
libipu6:
  Installed: 0~git202104021802.45905c6-1~ubuntu20.04.1
  Candidate: 0~git202104021802.45905c6-1~ubuntu20.04.1
  Version table:
 *** 0~git202104021802.45905c6-1~ubuntu20.04.1 500
500 http://ppa.launchpad.net/oem-solutions-group/intel-ipu6/ubuntu 
focal/main amd64 Packages
100 /var/lib/dpkg/status
libcamhal0:
  Installed: 0~git202108110731.5b056cf~ubuntu20.04.1
  Candidate: 0~git202108110731.5b056cf~ubuntu20.04.1
  Version table:
 *** 0~git202108110731.5b056cf~ubuntu20.04.1 500
500 http://ppa.launchpad.net/oem-solutions-group/intel-ipu6/ubuntu 
focal/main amd64 Packages
100 /var/lib/dpkg/status
stefang@capella:~$ cat /etc/default/v4l2-relayd 
# GStreamer source element name:
#VIDEOSRC="videotest"
#SPLASHSRC="filesrc location=/.../splash.png ! pngdec ! imagefreeze 
num-buffers=4 ! videoscale ! videoconvert"

# Output format, width, height, and frame rate:
#FORMAT=YUV2
#WIDTH=1280
#HEIGHT=720
#FRAMERATE=30/1

# Virtual video device name:
#CARD_LABEL="Virtual Camera"

# Extra options to pass to v4l2-relayd:
#EXTRA_OPTS=-d
stefang@capella:~$ cat /etc/v4l2-relayd 
cat: /etc/v4l2-relayd: No such file or directory

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

Title:
  Intel IPU6 GStreamer src plugin not working

Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.13 source package in Focal:
  New

Bug description:
  The device is properly detected but it seems there are still issues
  with gstreamer plugin. When I try to run cheese I get the following
  error message:

  ../src/intel/isl/isl.c:2018: FINISHME:
  ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is
  disabled, but a workaround is available.

  (cheese:3769): cheese-WARNING **: 08:02:37.506: Failed to allocate required 
memory.: gstv4l2src.c(660): gst_v4l2src_decide_allocation (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1:
  Buffer pool activation failed

  
  With VLC I get
  stefang@capella:~$ vlc v4l2:///dev/video0
  VLC media player 3.0.9.2 Vetinari (revision 3.0.9.2-0-gd4c1aefe4d)
  [55cfdb6a3670] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230001160] v4l2 demux error: cannot start streaming: Link has been 
severed
  Using mplane plugin for capture 
  [7f0230001160] v4l2 demux error: not a radio tuner device
  Using mplane plugin for capture 
  [7f0230007b70] v4l2 stream error: cannot get streaming parameters: 
Inappropriate ioctl for device
  libv4l2: error turning on stream: Link has been severed
  [7f0230007b70] v4l2 stream error: cannot start streaming: Link has been 
severed
  QObject::~QObject: Timers cannot be stopped from another thread

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-1012-oem 5.13.0-1012.16
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  Uname: Linux 5.13.0-1012-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Sep 17 07:59:51 2021
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-oem-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stefang1469 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. Latitude 9420
  Package: linux-oem-5.13 (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1012-oem 
root=UUID=e2704fd1-5330-4b87-9cdf-a353f5fe73b7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
 

[Kernel-packages] [Bug 1938697] Re: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic

[Chris Chiu]

Thanks for the information although the fix is for the WLAN driver.
That's quite surprising to me. Anyway, it's good to know the bug is
gone.

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

Title:
  Kernel driver support issue between  5.4.0-74-generic and
  5.4.0-80-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have found an issue after upgrading my Kernel from 5.4.0-74-generic
  to 5.4.0-80-generic on Ubuntu 20.04.

  It appears that support for the second ethernet port on my Lenovo
  m90n-1 has been dropped or isn't working as expected.  After upgrading
  to 5.4.0-80-generic my second ethernet port

  Both ethernet ports use the r8169 driver.  If I switch back to the
  previous kernel 5.4.0-74-generic.  The second ethernet port is usable
  again.

  I did attempt under 5.4.0-80-generic to see if I could get an error
  message.  When the driver attempts to discover the second ethernet
  port the following error is thrown.

 "unknown chip XID fcf"

  Support output below:

  
  --- Before update.

  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64)

  root@lenovo-test-3:~# lshw -c network
*-network DISABLED
 description: Wireless interface
 product: Cannon Point-LP CNVi [Wireless-AC]
 vendor: Intel Corporation
 physical id: 14.3
 bus info: pci@:00:14.3
 logical name: wlo1
 version: 30
 serial: 54:8d:5a:ab:41:77
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
 resources: irq:16 memory:a141c000-a141
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: enp2s0
 version: 15
 serial: 98:fa:9b:c9:eb:c6
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 
link=yes multicast=yes port=MII speed=1Gbit/s
 resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff 
memory:a130-a1303fff
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:04:00.0
 logical name: enp4s0
 version: 1b
 serial: 98:fa:9b:c9:eb:c7
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII
 resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff 
memory:a120-a1203fff

  
  --- After update

  root@lenovo-test-3:~# uname -r
  5.4.0-80-generic

  root@lenovo-test-3:~# lshw -c network
*-network DISABLED
 description: Wireless interface
 product: Cannon Point-LP CNVi [Wireless-AC]
 vendor: Intel Corporation
 physical id: 14.3
 bus info: pci@:00:14.3
 logical name: wlo1
 version: 30
 serial: 54:8d:5a:ab:41:77
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
 resources: irq:16 memory:a141c000-a141
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: enp2s0
 version: 15
 serial: 98:fa:9b:c9:eb:c6
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on 

[Kernel-packages] [Bug 1779756] Re: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04)

[Suphanat]

I would like to know how to resolve my issue? I'm facing with the issue
like this. Initially, I have the information of driver, kernel, NIC card
as the below and performed to change fiber link but this issue still
alive.

$ ethtool -i enp175s0f0
driver: i40e
version: 2.1.14-k
firmware-version: 6.01 0x80003554 1.1747.0
Ethernet Controller XXV710

Linux kernel: 4.15.0-106-generic
Operation System: Ubuntu 18.04 LTS

$dmesg | grep enp175s0f0
[33183121.471105] i40e :af:00.0 enp175s0f0: speed changed to 0 for port 
enp175s0f0
[33183121.973729] i40e :af:00.0 enp175s0f0: NIC Link is Up, 25 Gbps Full 
Duplex, Requested FEC: None, FEC: CL74 FC-FEC/BASE-R, Autoneg: False, Flow 
Control: None
[33183122.320007] i40e :af:00.0 enp175s0f0: NIC Link is Down

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

Title:
  Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu
  18.04)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The i40e driver can get stalled on tx timeouts. This can happen when
  DCB is enabled on the connected switch. This can also trigger a
  second situation when a tx timeout occurs before the recovery of
  a previous timeout has completed due to CPU load, which is not
  handled correctly. This leads to networking delays, drops and
  application timeouts and hangs. Note that the first tx timeout
  cause is just one of the ways to end up in the second situation.

  This issue was seen on a heavily loaded Kafka broker node running
  the 4.15.0-38-generic kernel on Xenial.

  Symptoms include messages in the kernel log of the form:

  ---
  [4733544.982116] i40e :18:00.1 eno2: tx_timeout: VSI_seid: 390, Q 6, NTC: 
0x1a0, HWB: 0x66, NTU: 0x66, TAIL: 0x66, INT: 0x0
  [4733544.982119] i40e :18:00.1 eno2: tx_timeout recovery level 1, 
hung_queue 6
  

  With the test kernel provided in this LP bug which had these
  two commits compiled in, the problem has not been seen again,
  and has been running successfully for several months:

  "i40e: Fix for Tx timeouts when interface is brought up if
   DCB is enabled"
  Commit: fa38e30ac73fbb01d7e5d0fd1b12d412fa3ac3ee

  "i40e: prevent overlapping tx_timeout recover"
  Commit: d5585b7b6846a6d0f9517afe57be3843150719da

  * The first commit is already in Disco, Cosmic
  * The second commit is already in Disco
  * Bionic needs both patches and Cosmic needs the second

  [Test Case]
  * We are considering the case of both issues above occurring.
  * Seen by reporter on a Kafka broker node with heavy traffic.
  * Not easy to reproduce as it requires something like the
    following example environment and heavy load:

    Kernel: 4.15.0-38-generic
    Network driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
    NIC: Intel 40Gb XL710
    DCB enabled

  [Regression Potential]
  Low, as the first only impacts i40e DCB environment, and has
  been running for several months in production-load testing
  successfully.

  --- Original Description
  Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel 4.13 to 
the Kernel 4.15.0-24-generic.

  On a "Dell PowerEdge R330" server with a network adapter "Intel
  Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network
  card no longer works and permanently displays these three lines :

  [   98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, 
NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1
  [   98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, 
hung_queue 8
  [   98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779756/+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 1795587] Re: Upgrade i40e driver to support 6.01 Firmware - Intel XL710

[Suphanat]

I would like to know how to resolve my issue? I'm facing with the issue
like this. Initially, I have the information of driver, kernel, NIC card
as the below and performed to change fiber link but this issue still
alive.

$ ethtool -i enp175s0f0
driver: i40e
version: 2.1.14-k
firmware-version: 6.01 0x80003554 1.1747.0
Ethernet Controller XXV710

Linux kernel: 4.15.0-106-generic
Operation System: Ubuntu 18.04 LTS

$dmesg | grep enp175s0f0
[33183121.471105] i40e :af:00.0 enp175s0f0: speed changed to 0 for port 
enp175s0f0
[33183121.973729] i40e :af:00.0 enp175s0f0: NIC Link is Up, 25 Gbps Full 
Duplex, Requested FEC: None, FEC: CL74 FC-FEC/BASE-R, Autoneg: False, Flow 
Control: None
[33183122.320007] i40e :af:00.0 enp175s0f0: NIC Link is Down

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

Title:
  Upgrade i40e driver to support 6.01 Firmware - Intel XL710

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Intel released the 6.01 Firmware for the Intel XL710 network cards. As
  stated in the feature support matrix [1] in the table 9 on page 18,
  the minimum kernel driver version for the 6.01 Firmware i40e must be
  2.1.26, the recent driver version is 2.4.10 [2]

  The i40 driver version included in the 4.15.0-36 (Bionic, LTS) is
  2.1.14-k.

  $ uname -a
  Linux ubuntu-bionic 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  $ modinfo i40e
  filename:   
/lib/modules/4.15.0-36-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko
  version:2.1.14-k
  license:GPL
  description:Intel(R) Ethernet Connection XL710 Network Driver

  Release notes: [3] [4] [5] [6] [7]

  The firmware 6.01 introduce better performance for DPDK and SR-IOV
  applications for those cards, and  NFV application workloads would
  perform better.

  
  [1] Intel® Ethernet Controller X710/ XXV710/XL710 Feature Support Matrix
  
https://www.intel.com/content/dam/www/public/us/en/documents/release-notes/xl710-ethernet-controller-feature-matrix.pdf

  [2] Intel® Network Adapter Driver for PCIe* 40 Gigabit Ethernet Network 
Connections Under Linux* 
  
https://downloadcenter.intel.com/download/24411/Intel-Network-Adapter-Driver-for-PCIe-40-Gigabit-Ethernet-Network-Connections-Under-Linux-?product=75021

  [3] Intel(R) Network Connections Software Version 23.2 Release Notes
  https://downloadmirror.intel.com/24411/eng/readme.txt

  [4] Intel(R) Network Connections Software Version 23.1 Release Notes
  https://downloadmirror.intel.com/27869/eng/readme.txt

  [5] Intel(R) Network Connections Software Version 22.10 Release Notes
  https://downloadmirror.intel.com/27547/eng/readme.txt

  [6] Intel(R) Network Connections Software Version 22.9 Release Notes
  https://downloadmirror.intel.com/27547/eng/readme.txt

  [7] Intel(R) Network Connections Software Version 22.6 Release Notes
  https://downloadmirror.intel.com/27189/eng/readme.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795587/+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 1944426] [NEW] Delay sending data after wireless roaming between APs

[Mjohnson459]

Public bug reported:

## Summary
Any time I roam from one access point to another (same SSID) I start receiving 
packets instantly after the roam is successful but experience a delay of 
roughly 1 second before I can send packets out. I have seen this with  
multiple configurations listed below. I started seeing this delay after 
upgrading from Ubuntu 16.04 to 18.04 and using the debians from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/ I can see the bug was 
introduced between v4.19 and v4.20-rc1. 

## Configurations
I have tested multiple laptops and machines with different software to narrow 
down where the bug might be. All of these configurations showed the bug.
- Distro(kernel) version - 20.04 (5.4, 5.8, 5.11, 5.14-rc7), Kali 2021.2 (5.10) 
 
- Hardware(driver): intel (iwlwifi), qualcomm (ath10k), realtek.  
- Supplicant: iwd and wpa_supplicant  
- Manager: iwd, systemd-networkd, NetworkManager  
- Data: ping, iperf3 (tcp and udp), custom python udp script  
- APs:  Meraki MR46, tp-link decos  
 
## Reproduction
The bug is relatively easy to reproduce if you have multiple APs on the same 
SSID available. The simplest way is to start up a `ping -i 0.2 ` and 
then walk between the APs until it roams. It is also possible to use `wpa_cli 
roam `. For more accurate testing I was using a simple python script 
that spams udp packets and then using `tcpdump` to record the packets for 
viewing in wireshark.
 
## Example output
Here is the output of the simplest test that still shows the issue  
(ping + tcpdump + iwd + 5.11.0-27-generic):  
[https://pastebin.com/92TKKktb](https://pastebin.com/92TKKktb)  
  
My naive tl;dr of that data is:  
- 30.322638 - we start to roam which falls between icmp_seq=121 and 
icmp_seq=122.  
- 30.415411 - roam is complete  
- 30.424277 - iwd is sending and receiving neighbor reports over the link  
- 31.358491 - an ARP request is sent out (why is the ARP cache cleared?)  
- 31.367930 - ARP response - packets start being sent again

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 21 10:12:40 2021
InstallationDate: Installed on 2019-08-09 (773 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: linux-signed-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Delay sending data after wireless roaming between APs

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

Bug description:
  ## Summary
  Any time I roam from one access point to another (same SSID) I start 
receiving packets instantly after the roam is successful but experience a delay 
of roughly 1 second before I can send packets out. I have seen this with  
  multiple configurations listed below. I started seeing this delay after 
upgrading from Ubuntu 16.04 to 18.04 and using the debians from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/ I can see the bug was 
introduced between v4.19 and v4.20-rc1. 

  ## Configurations
  I have tested multiple laptops and machines with different software to narrow 
down where the bug might be. All of these configurations showed the bug.
  - Distro(kernel) version - 20.04 (5.4, 5.8, 5.11, 5.14-rc7), Kali 2021.2 
(5.10)  
  - Hardware(driver): intel (iwlwifi), qualcomm (ath10k), realtek.  
  - Supplicant: iwd and wpa_supplicant  
  - Manager: iwd, systemd-networkd, NetworkManager  
  - Data: ping, iperf3 (tcp and udp), custom python udp script  
  - APs:  Meraki MR46, tp-link decos  
   
  ## Reproduction
  The bug is relatively easy to reproduce if you have multiple APs on the same 
SSID available. The simplest way is to start up a `ping -i 0.2 ` and 
then walk between the APs until it roams. It is also possible to use `wpa_cli 
roam `. For more accurate testing I was using a simple python script 
that spams udp packets and then using `tcpdump` to record the packets for 
viewing in wireshark.
   
  ## Example output
  Here is the output of the simplest test that still shows the issue  
  (ping + tcpdump + iwd + 5.11.0-27-generic):  
  [https://pastebin.com/92TKKktb](https://pastebin.com/92TKKktb)  

  My naive tl;dr of that data is:  
  - 30.322638 - we start to roam which falls between icmp_seq=121 and 
icmp_seq=122.  
  - 30.415411 - roam is complete  
  - 30.424277 - iwd is sending and receiving neighbor reports over the link  
  - 31.358491 - an ARP 

[Kernel-packages] [Bug 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04

[Suganath Prabu]

Only below two patches have a driver functionality fix, but these are
not that critical.

1. d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation
Here is SRU for this bug fix patch,
[Impact] 
Driver always allocates ReplyPostFree queue pools as a set of 16 ReplyPostFree 
queues. So, on a VM where there are only one or two CPUs assigned to it and 
with less RAM memory then there are chances that the kernel cannot allocate a 
continuous memory segment for a ReplyPostFree queues set, and hence IOC 
initialization is terminated.
[Fix] 
On a system with the number of CPUs less than 16, the driver doesn't need 16 
ReplyPostFree queues, it just needs the CPU count number of ReplyPostFree 
queues.  So the driver allocates only the CPU count of ReplyPostFree queues 
instead of allocating 16 ReplyPostFree queues and IOC gets initialized 
successfully.
[Testing]
Load driver on a VM with one or two CPUs and less RAM size (such as 1GB) and 
driver should successfully Initialize the IOC.
[REGRESSION RISK]
There is no regression risk with this bug-fix patch.

2. e2fac6c44a SCSI: mpt3sas: Fix deadlock while canceling the running firmware 
event
Here is SRU for this bug fix patch,

[Impact]
Will observe driver hang if any MPT request message gets timeout and which 
requires hard reset while processing the Firmware Event.
[Fix]
During hard reset operation, don't call canel_work_sync() API for the Firmware 
event work if this hard reset operation is invoked while processing this 
corresponding firmware event. 
[Testing]
Load the driver and perform more target drive's hot plug and unplug operations 
(such that more firmware events get generated).  
[REGRESSION RISK]
There is no regression risk with this bugfix patch. 


Below fix patches are cosmetic patches which doesn't have any driver 
functionality impacts,
bfb3f00c06 scsi: mpt3sas: Simplify bool comparison
cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot
54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params
782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues
a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues
206a3afa94 scsi: mpt3sas: Fix a typo
c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement
16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query
3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers
2910a4a9e9 scsi: mpt3sas: Documentation cleanup
e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware 
event
84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang
cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue
d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add()

Below patches are related to kernel APIs compatible changes and doesn't have 
any driver functionality impacts,
8278807abd scsi: core: Add scsi_device_busy() wrapper
020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap
f2b1e9c6f8 scsi: core: Introduce scsi_build_sense()

Below patches are the driver enhancement patches that we have added in
Phase18 & Phase19.

1.  Add host tagset support:
Through this feature, the driver can emulate the number of request queues to 
more than one at kernel level even though IOC supports only one request queue. 
By default this feature is disabled, if users want this feature then they have 
to enable it through module parameter.  
64f0dce20 SCSI: mpt3sas: Add support for shared host tagset for CPU hotplug

[REGRESSION RISK]
No extra test cases are needed, normal regression test cases such as driver 
load & running IOs are enough.

2.  Additional diagnostic buffer query interface:
Currently whenever any diag trigger event hits the driver releases the diag 
buffer, but the application doesn't know for which trigger event the diag 
buffer got released. So added a new additional diagnostic buffer query IOCTL 
interface through which the application queries the driver about the reason 
(i.e. trigger event information) for which the diag buffer got released.  
688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface

[REGRESSION RISK]
No extra test cases are needed, normal regression test cases which cover the 
IOCTL paths are enough.

3.  Allocate memory pools within 4GB memory region:
According to the MPI spec chain, sense reply, reply post, etc pool buffers need 
to be allocated within the 4GB memory region. So, through the below patches 
driver makes sure that these pools are allocated within the 4GB memory region 
(i.e. higher 32 address bits should be the same for the entire buffer pool).

d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within same 
4 GB region
7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 GB 
region
970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 GB 
region
58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 GB 
region
2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to 

[Kernel-packages] [Bug 1944417] [NEW] Add support for 5.14

[Timo Aaltonen]

Public bug reported:

zfs-linux needs at least these two compat changes in order to build
against 5.14 kernel like oem-5.14 in focal:

https://github.com/openzfs/zfs/commit/1b06b03a7be88f4565c2c3114b8d3f2dc9f9408a
https://github.com/openzfs/zfs/commit/1c24bf966c373009f2be77438e8696aabf50a7e7

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

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

Title:
  Add support for 5.14

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  zfs-linux needs at least these two compat changes in order to build
  against 5.14 kernel like oem-5.14 in focal:

  https://github.com/openzfs/zfs/commit/1b06b03a7be88f4565c2c3114b8d3f2dc9f9408a
  https://github.com/openzfs/zfs/commit/1c24bf966c373009f2be77438e8696aabf50a7e7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1944417/+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

[Amrit Singh]

Hi All,
Please try with the EnableBrightnessControl =1 as kernel parameter or add it in 
xorg.conf file.
You can add it in device section as shown below - 

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName  "NVIDIA RTX A3000 Laptop GPU"
Option "RegistryDwords" "EnableBrightnessControl=1"
EndSection

After change in the xorg, please uninstall / install the driver.

-- 
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 1944411] Re: ubuntu_bpf: build failure with kernel 5.13

[Andrea Righi]

We likely need this commit to fix this build issue, but it's not trivial
to backport it, we are going to hint the test for now:

commit 4d1b62986125b6de596c98310543652a7892e097
Author: Alexei Starovoitov 
Date:   Thu May 13 17:36:20 2021 -0700

selftests/bpf: Convert few tests to light skeleton.

Convert few tests that don't use CO-RE to light skeleton.

Signed-off-by: Alexei Starovoitov 
Signed-off-by: Daniel Borkmann 
Acked-by: Andrii Nakryiko 
Link: 
https://lore.kernel.org/bpf/20210514003623.28033-19-alexei.starovoi...@gmail.com


** Description changed:

- 12886   Warning: Kernel ABI header at 
'tools/include/uapi/linux/if_link.h' differs from latest version at 
'include/uapi/linux/if_link.h'
-   12887 libbpf: elf: skipping unrecognized data 
section(5) .rodata.str1.1
-   12888 libbpf: elf: skipping unrecognized data 
section(5) .rodata.str1.1
-   12889 libbpf: elf: skipping unrecognized data 
section(6) .rodata.str1.1
-   12890 libbpf: elf: skipping unrecognized data 
section(7) .rodata.str1.1
-   12891 libbpf: elf: skipping unrecognized data 
section(8) .rodata.cst16
-   12892 libbpf: elf: skipping unrecognized data 
section(8) .rodata.str1.1
-   12893 libbpf: elf: skipping unrecognized data 
section(7) .rodata.str1.1
-   12894 libbpf: elf: skipping unrecognized data 
section(8) .rodata.str1.1
-   12895 libbpf: elf: skipping unrecognized data 
section(7) .maps.btf_map
-   12896 libbpf: elf: skipping unrecognized data 
section(7) .maps.btf_map_legacy
-   12897 libbpf: elf: skipping unrecognized data 
section(8) .rodata.str1.1
-   12898 libbpf: elf: skipping unrecognized data 
section(27) .rodata.str1.1
-   12899 libbpf: elf: skipping unrecognized data 
section(15) .rodata.str1.1
-   12900 libbpf: elf: skipping unrecognized data 
section(5) .rodata.cst16
-   12901 libbpf: elf: skipping unrecognized data 
section(27) .rodata.str1.1
-   12902 libbpf: elf: skipping unrecognized data 
section(4) .rodata.str1.1
-   12903 libbpf: elf: skipping unrecognized data 
section(7) .rodata.str1.1
-   12904 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/ringbuf.c:
 In function ‘test_ringbuf’:
-   12905 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/ringbuf.c:105:35:
 error: ‘skel->maps.ringbuf’ is a pointer; did you mean to use ‘->’?
-   12906   105 | rb_fd = 
skel->maps.ringbuf.map_fd;
-   12907   |   ^
-   12908   |   ->
-   12909 make[1]: *** [Makefile:456: 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/ringbuf.test.o]
 Error 1
-   12910 make: *** [Makefile:159: all] Error 2
-   12911   21:28:05 INFO | END ERROR
ubuntu_bpf.setup
+ We get this failure with the ubuntu_bpf
+ 
+ 12test886   Warning: Kernel ABI header at 
'tools/include/uapi/linux/if_link.h' differs from latest version at 
'include/uapi/linux/if_link.h'
+   12887 libbpf: elf: skipping unrecognized data section(5) 
.rodata.str1.1
+   12888 libbpf: elf: skipping unrecognized data section(5) 
.rodata.str1.1
+   12889 libbpf: elf: skipping unrecognized data section(6) 
.rodata.str1.1
+   12890 libbpf: elf: skipping unrecognized data section(7) 
.rodata.str1.1
+   12891 libbpf: elf: skipping unrecognized data section(8) 
.rodata.cst16
+   12892 libbpf: elf: skipping unrecognized data section(8) 
.rodata.str1.1
+   12893 libbpf: elf: skipping unrecognized data section(7) 
.rodata.str1.1
+   12894 libbpf: elf: skipping unrecognized data section(8) 
.rodata.str1.1
+   12895 libbpf: elf: skipping unrecognized data section(7) 
.maps.btf_map
+   12896 libbpf: elf: skipping unrecognized data section(7) 
.maps.btf_map_legacy
+   12897 libbpf: elf: skipping unrecognized data section(8) 
.rodata.str1.1
+   12898 libbpf: elf: skipping unrecognized data section(27) 
.rodata.str1.1
+   12899 libbpf: elf: skipping unrecognized data section(15) 
.rodata.str1.1
+   12900 libbpf: elf: skipping unrecognized data section(5) 
.rodata.cst16
+   12901 libbpf: elf: skipping 

[Kernel-packages] [Bug 1874186] Re: vmx_vmcs_shadow_test from ubuntu_kvm_unit_tests timeout on E-KVM

[Krzysztof Kozlowski]

Found on impish/linux-oracle/5.13.0-1005.7 (instance: VM.Standard2.1)

** Summary changed:

- vmx_vmcs_shadow_test from ubunut_kvm_unit_tests timeout on E-KVM
+ vmx_vmcs_shadow_test from ubuntu_kvm_unit_tests timeout on E-KVM

** Tags added: 5.13 hinted impish oracle

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

Title:
  vmx_vmcs_shadow_test from ubuntu_kvm_unit_tests timeout on E-KVM

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-kvm package in Ubuntu:
  Invalid

Bug description:
  Issue found on E-KVM 5.3.0-1016.17-kvm and can be reproduced on
  5.3.0-1015-kvm as well, thus this is not a regression.

  PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: 
shadowed for VMWRITE (in 21056 cycles) 
  PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU 
flags after VMWRITE (1) are as expected (1)
  PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: 
shadowed for VMREAD (in 20236 cycles)
  PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU 
flags after VMREAD (1) are as expected (1)
  qemu-system-x86_64: terminating on signal 15 from pid 2874 (timeout) 
  FAIL vmx_vmcs_shadow_test (timeout; duration=180)

  Need to test it with a longer timeout setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-1015-kvm 5.3.0-1015.16
  ProcVersionSignature: User Name 5.3.0-1015.16-kvm 5.3.18
  Uname: Linux 5.3.0-1015-kvm x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Wed Apr 22 04:37:11 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1874186/+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 1944411] 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 1944411

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

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

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

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

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

Title:
  ubuntu_bpf: build failure with kernel 5.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  12886   Warning: Kernel ABI header at 
'tools/include/uapi/linux/if_link.h' differs from latest version at 
'include/uapi/linux/if_link.h'
12887 libbpf: elf: skipping unrecognized data 
section(5) .rodata.str1.1
12888 libbpf: elf: skipping unrecognized data 
section(5) .rodata.str1.1
12889 libbpf: elf: skipping unrecognized data 
section(6) .rodata.str1.1
12890 libbpf: elf: skipping unrecognized data 
section(7) .rodata.str1.1
12891 libbpf: elf: skipping unrecognized data 
section(8) .rodata.cst16
12892 libbpf: elf: skipping unrecognized data 
section(8) .rodata.str1.1
12893 libbpf: elf: skipping unrecognized data 
section(7) .rodata.str1.1
12894 libbpf: elf: skipping unrecognized data 
section(8) .rodata.str1.1
12895 libbpf: elf: skipping unrecognized data 
section(7) .maps.btf_map
12896 libbpf: elf: skipping unrecognized data 
section(7) .maps.btf_map_legacy
12897 libbpf: elf: skipping unrecognized data 
section(8) .rodata.str1.1
12898 libbpf: elf: skipping unrecognized data 
section(27) .rodata.str1.1
12899 libbpf: elf: skipping unrecognized data 
section(15) .rodata.str1.1
12900 libbpf: elf: skipping unrecognized data 
section(5) .rodata.cst16
12901 libbpf: elf: skipping unrecognized data 
section(27) .rodata.str1.1
12902 libbpf: elf: skipping unrecognized data 
section(4) .rodata.str1.1
12903 libbpf: elf: skipping unrecognized data 
section(7) .rodata.str1.1
12904 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/ringbuf.c:
 In function ‘test_ringbuf’:
12905 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/ringbuf.c:105:35:
 error: ‘skel->maps.ringbuf’ is a pointer; did you mean to use ‘->’?
12906   105 | rb_fd = 
skel->maps.ringbuf.map_fd;
12907   |   ^
12908   |   ->
12909 make[1]: *** [Makefile:456: 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/ringbuf.test.o]
 Error 1
12910 make: *** [Makefile:159: all] Error 2
12911   21:28:05 INFO | END ERROR
ubuntu_bpf.setup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944411/+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 1944411] [NEW] ubuntu_bpf: build failure with kernel 5.13

[Andrea Righi]

Public bug reported:

  12886   Warning: Kernel ABI header at 
'tools/include/uapi/linux/if_link.h' differs from latest version at 
'include/uapi/linux/if_link.h'
12887 libbpf: elf: skipping unrecognized data 
section(5) .rodata.str1.1
12888 libbpf: elf: skipping unrecognized data 
section(5) .rodata.str1.1
12889 libbpf: elf: skipping unrecognized data 
section(6) .rodata.str1.1
12890 libbpf: elf: skipping unrecognized data 
section(7) .rodata.str1.1
12891 libbpf: elf: skipping unrecognized data 
section(8) .rodata.cst16
12892 libbpf: elf: skipping unrecognized data 
section(8) .rodata.str1.1
12893 libbpf: elf: skipping unrecognized data 
section(7) .rodata.str1.1
12894 libbpf: elf: skipping unrecognized data 
section(8) .rodata.str1.1
12895 libbpf: elf: skipping unrecognized data 
section(7) .maps.btf_map
12896 libbpf: elf: skipping unrecognized data 
section(7) .maps.btf_map_legacy
12897 libbpf: elf: skipping unrecognized data 
section(8) .rodata.str1.1
12898 libbpf: elf: skipping unrecognized data 
section(27) .rodata.str1.1
12899 libbpf: elf: skipping unrecognized data 
section(15) .rodata.str1.1
12900 libbpf: elf: skipping unrecognized data 
section(5) .rodata.cst16
12901 libbpf: elf: skipping unrecognized data 
section(27) .rodata.str1.1
12902 libbpf: elf: skipping unrecognized data 
section(4) .rodata.str1.1
12903 libbpf: elf: skipping unrecognized data 
section(7) .rodata.str1.1
12904 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/ringbuf.c:
 In function ‘test_ringbuf’:
12905 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/ringbuf.c:105:35:
 error: ‘skel->maps.ringbuf’ is a pointer; did you mean to use ‘->’?
12906   105 | rb_fd = 
skel->maps.ringbuf.map_fd;
12907   |   ^
12908   |   ->
12909 make[1]: *** [Makefile:456: 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/ringbuf.test.o]
 Error 1
12910 make: *** [Makefile:159: all] Error 2
12911   21:28:05 INFO | END ERROR
ubuntu_bpf.setup

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

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

Title:
  ubuntu_bpf: build failure with kernel 5.13

Status in linux package in Ubuntu:
  New

Bug description:
  12886   Warning: Kernel ABI header at 
'tools/include/uapi/linux/if_link.h' differs from latest version at 
'include/uapi/linux/if_link.h'
12887 libbpf: elf: skipping unrecognized data 
section(5) .rodata.str1.1
12888 libbpf: elf: skipping unrecognized data 
section(5) .rodata.str1.1
12889 libbpf: elf: skipping unrecognized data 
section(6) .rodata.str1.1
12890 libbpf: elf: skipping unrecognized data 
section(7) .rodata.str1.1
12891 libbpf: elf: skipping unrecognized data 
section(8) .rodata.cst16
12892 libbpf: elf: skipping unrecognized data 
section(8) .rodata.str1.1
12893 libbpf: elf: skipping unrecognized data 
section(7) .rodata.str1.1
12894 libbpf: elf: skipping unrecognized data 
section(8) .rodata.str1.1
12895 libbpf: elf: skipping unrecognized data 
section(7) .maps.btf_map
12896 libbpf: elf: skipping unrecognized data 
section(7) .maps.btf_map_legacy
12897 libbpf: elf: skipping unrecognized data 
section(8) .rodata.str1.1
12898 libbpf: elf: skipping unrecognized data 
section(27) .rodata.str1.1
12899 libbpf: elf: skipping unrecognized data 
section(15) .rodata.str1.1
12900 libbpf: elf: skipping unrecognized data 
section(5) .rodata.cst16
12901 libbpf: elf: skipping unrecognized data 
section(27) .rodata.str1.1
12902 libbpf: elf: skipping unrecognized data 
section(4) 

[Kernel-packages] [Bug 1943902] Re: NVME errors in confidential vms

[Stefan Bader]

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

** Changed in: linux-gcp (Ubuntu Focal)
   Status: New => In Progress

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

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

Title:
  NVME errors in confidential vms

Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp-5.4 package in Ubuntu:
  Invalid
Status in linux-gcp-5.4 source package in Bionic:
  New
Status in linux-gcp source package in Focal:
  In Progress

Bug description:
  See
  https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view
  for more info

  [Impact]
  Using nvme with swiotlb in confidential VMs can encounter hardware read/write 
errors.

  [Fix]

  The following upstream patches from v5.12 address this:

  3d2d861eb03e nvme-pci: set min_align_mask
  1f221a0d0dbf swiotlb: respect min_align_mask
  16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single
  26a7e094783d swiotlb: refactor swiotlb_tbl_map_single
  ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single
  c32a77fd1878 swiotlb: factor out a nr_slots helper
  c7fbeca757fe swiotlb: factor out an io_tlb_offset helper
  b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define

  [Test]

  Using a confidential VM, with 'swiotlb=force' set on the kernel
  command line, and an additional nvme device attached:

  $ sudo mkfs.xfs -f /dev/nvme2n1
  meta-data=/dev/nvme2n1   isize=512agcount=4, agsize=131072 blks
   =   sectsz=512   attr=2, projid32bit=1
   =   crc=1finobt=1, sparse=0, rmapbt=0, 
refl
  ink=0
  data =   bsize=4096   blocks=524288, imaxpct=25
   =   sunit=0  swidth=0 blks
  naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
  log  =internal log   bsize=4096   blocks=2560, version=2
   =   sectsz=512   sunit=0 blks, lazy-count=1
  realtime =none   extsz=4096   blocks=0, rtextents=0
  mkfs.xfs: pwrite failed: Input/output error

  Note the input/output error

  The error no longer happens with the fixes applied.

  [Regression Potential]

  Low risk as the patches are mostly clean-up and refactor.
  Regression in swiotlb could cause hardware read/write errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1943902/+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 1931660] Re: PANIC at zfs_znode.c:339:zfs_znode_sa_init()

[Doki]

It stared to happen recently on my encrypted pool. The FS scrub reported
no errors.

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

Title:
  PANIC at zfs_znode.c:339:zfs_znode_sa_init()

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing a non-deterministic panic in the ZFS code. Last boot, this
  occurred in systemd-udevd, resulting in a failed boot. The boot before
  that, firefox hit the same thing, and this boot it looks like it's hit
  an Evolution component.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.11.0-18-generic 5.11.0-18.19+21.10.1
  ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  4988 F pulseaudio
   /dev/snd/controlC1:  chris  4988 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 11 11:49:47 2021
  InstallationDate: Installed on 2021-05-13 (28 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_z8j7yc@/vmlinuz-5.11.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_z8j7yc ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware 1.198
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-05-13 (28 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931660/+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 1944407] [NEW] Linux didnt detect my touchpad upon installation

[Creative Forever]

Public bug reported:

After installing Ubuntu 20.04 LTS I couldnt use my touch pad at all.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 21 14:56:54 2021
InstallationDate: Installed on 2021-09-19 (2 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-signed-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Linux didnt detect my touchpad upon installation

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

Bug description:
  After installing Ubuntu 20.04 LTS I couldnt use my touch pad at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 21 14:56:54 2021
  InstallationDate: Installed on 2021-09-19 (2 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1944407/+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