date:20210406

** Tags added: sru-20210315

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

Title:
  memcg_stat_rss from controllers in ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New

Bug description:
  This issue was spotted on an i386 node "pepe" with Disco kernel,
  it failed with:

  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

  memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up

  
  <<>>
  tag=memcg_stat_rss stime=1563448062
  cmdline="memcg_stat_rss.sh"
  contacts=""
  analysis=exit
  <<>>
  memcg_stat_rss 1 TINFO: Starting test 1
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168
  memcg_stat_rss 1 TINFO: Warming up pid: 1784
  memcg_stat_rss 1 TINFO: Process is still here after warm up: 1784
  memcg_stat_rss 1 TPASS: rss is 135168 as expected
  memcg_stat_rss 2 TINFO: Starting test 2
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096
  memcg_stat_rss 2 TINFO: Warming up pid: 1804
  memcg_stat_rss 2 TINFO: Process is still here after warm up: 1804
  memcg_stat_rss 2 TPASS: rss is 0 as expected
  memcg_stat_rss 3 TINFO: Starting test 3
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096
  memcg_stat_rss 3 TINFO: Warming up pid: 1825
  memcg_stat_rss 3 TINFO: Process is still here after warm up: 1825
  memcg_stat_rss 3 TPASS: rss is 0 as expected
  memcg_stat_rss 4 TINFO: Starting test 4
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm 
-s 135168
  memcg_stat_rss 4 TINFO: Warming up pid: 1845
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

  memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up
  memcg_stat_rss 5 TINFO: Starting test 5
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168
  memcg_stat_rss 5 TINFO: Warming up pid: 1858
  memcg_stat_rss 5 TINFO: Process is still here after warm up: 1858
  memcg_stat_rss 5 TPASS: rss is 135168 as expected
  memcg_stat_rss 6 TINFO: Starting test 6
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168
  memcg_stat_rss 6 TINFO: Warming up pid: 1878
  memcg_stat_rss 6 TINFO: Process is still here after warm up: 1878
  memcg_stat_rss 6 TPASS: rss is 135168 as expected
  memcg_stat_rss 7 TPASS: rss is 0 as expected
  memcg_stat_rss 8 TINFO: Starting test 7
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096
  memcg_stat_rss 8 TINFO: Warming up pid: 1901
  memcg_stat_rss 8 TINFO: Process is still here after warm up: 1901
  memcg_stat_rss 8 TPASS: rss is 0 as expected
  memcg_stat_rss 9 TPASS: rss is 0 as expected
  memcg_stat_rss 10 TINFO: Starting test 8
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096
  memcg_stat_rss 10 TINFO: Warming up pid: 1925
  memcg_stat_rss 10 TINFO: Process is still here after warm up: 1925
  memcg_stat_rss 10 TPASS: rss is 0 as expected
  memcg_stat_rss 11 TPASS: rss is 0 as expected
  memcg_stat_rss 12 TINFO: Starting test 9
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 12 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 12 TINFO: Running memcg_process --mmap-anon --mmap-file --shm 
-s 135168
  memcg_stat_rss 12 TINFO: Warming up pid: 1948
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

  memcg_stat_rss 12 TFAIL: Process 1948 exited with 1 after warm up
  memcg_stat_rss 13 TINFO: Starting test 10

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

2021-04-06 Thread Daniel van Vugt

** Tags added: hirsute raspi

** Changed in: bluez (Ubuntu)
   Importance: Undecided => Low

** Changed in: bluez (Ubuntu)
   Status: New => Triaged

** Summary changed:

- Bluez should notify users when they need to reboot to apply changes
+ Bluez should notify users when they need to reboot to apply changes on arm64

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

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

Status in bluez package in Ubuntu:
  Triaged

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

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

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

[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux

** Tags added: sru-20210315

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

Title:
  psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
  focal/linux

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  New

Bug description:
  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 DEBUG| [stdout] # tx: 42
  16:28:31 DEBUG| [stdout] # rx: 0
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw mtu size
  16:28:31 DEBUG| [stdout] # tx: 1514
  16:28:31 DEBUG| [stdout] # rx: 1472
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:32 DEBUG| [stdout] # dgram mtu size
  16:28:32 DEBUG| [stdout] # tx: 1500
  16:28:32 DEBUG| [stdout] # rx: 1472
  16:28:32 DEBUG| [stdout] # OK
  16:28:32 DEBUG| [stdout] # 
  16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails)
  16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive)
  16:28:32 DEBUG| [stdout] # tx: 14
  16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable
  16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL)
  16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
  16:28:32 DEBUG| [stdout] # raw gso min size
  16:28:32 DEBUG| [stdout] # tx: 1525
  16:28:32 DEBUG| [stdout] # rx: 1473
  16:28:32 DEBUG| [stdout] # OK
  16:28:32 DEBUG| [stdout] # 
  16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails)
  16:28:32 DEBUG| [stdout] # tx: 1524
  16:28:32 DEBUG| [stdout] # rx: 1472
  16:28:32 DEBUG| [stdout] # OK
  16:28:32 DEBUG| [stdout] # 
  16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # exit=1

  This failure is similar to bug 1884234, however, this test didn't fail
  on ADT with focal/linux before 5.4.0-44.48.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1828026] Re: gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64

** Tags added: hwe

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

Title:
  gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64

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

Bug description:
  Failed on Moonshot nodes.

  
  FAIL gicv2-mmio-up (17 tests, 2 unexpected failures)

  # TESTNAME=gicv2-mmio-up TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 1 
-machine gic-version=2 -append 'mmio'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/gic.flat -smp 1 -machine gic-version=2 
-append mmio # -initrd /tmp/tmp.6k28Ehxzim
  INFO: gicv2: mmio: number of implemented SPIs: 256
  PASS: gicv2: mmio: all 1 CPUs have interrupts
  INFO: gicv2: mmio: IIDR: 0x
  PASS: gicv2: mmio: GICD_TYPER is read-only
  PASS: gicv2: mmio: GICD_IIDR is read-only
  PASS: gicv2: mmio: ICPIDR2 is read-only (0x0004)
  PASS: gicv2: mmio: IPRIORITYR: consistent priority masking (0x)
  PASS: gicv2: mmio: IPRIORITYR: implements at least 4 priority bits (8)
  PASS: gicv2: mmio: IPRIORITYR: clearing priorities
  PASS: gicv2: mmio: IPRIORITYR: accesses beyond limit RAZ/WI
  PASS: gicv2: mmio: IPRIORITYR: accessing last SPIs
  PASS: gicv2: mmio: IPRIORITYR: priorities are preserved
  PASS: gicv2: mmio: IPRIORITYR: byte reads successful (0xff7fbf3f => 0xbf)
  PASS: gicv2: mmio: IPRIORITYR: byte writes successful (0x1f => 0xff1fbf3f)
  PASS: gicv2: mmio: ITARGETSR: bits for 7 non-existent CPUs masked
  PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI
  FAIL: gicv2: mmio: ITARGETSR: register content preserved (01010001 => 
)
  PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x01010001 => 0x00)
  FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x)
  SUMMARY: 17 tests, 2 unexpected failures

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51~16.04.1
  ProcVersionSignature: User Name 4.15.0-48.51~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-48-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: arm64
  Date: Tue May  7 11:25:30 2019
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed

** Tags added: hwe

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

Title:
  memcg_usage_in_bytes from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in linux-aws source package in Cosmic:
  New

Bug description:
   startup='Wed May 22 05:59:09 2019'
   memcg_usage_in_bytes_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 
4194304
   memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689
   memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689
   memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 
expected
   memcg_usage_in_bytes_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled
   tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no 
cu=5 cs=3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed

** Tags added: hwe

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

Title:
  getaddrinfo_01 from ipv6_lib test suite in LTP failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Eoan:
  New
Status in linux-aws source package in Eoan:
  New

Bug description:
  startup='Wed May 22 08:02:52 2019'
  getaddrinfo_011  TPASS  :  getaddrinfo IPv4 basic lookup
  getaddrinfo_012  TFAIL  :  getaddrinfo_01.c:140: getaddrinfo IPv4 
canonical name ("curly.maas") doesn't match hostname ("curly")
  getaddrinfo_013  TFAIL  :  getaddrinfo_01.c:578: getaddrinfo IPv6 basic 
lookup ("curly") returns -5 ("No address associated with hostname")
  tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed May 22 08:04:30 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed

** Tags added: hwe

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

Title:
  cpuset_hotplug from controllers in ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux-aws source package in Focal:
  New
Status in linux-azure source package in Focal:
  New

Bug description:
  Issue found on node amaura:
  <<>>
  tag=cpuset_hotplug stime=1561372131
  cmdline="cpuset_hotplug_test.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
  cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
  cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded.
  cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, 
Expect: 0-7).
  cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded.
  cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded.
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=1 corefile=no
  cutime=19 cstime=81
  <<>>

  Test script:
  
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-22-generic 4.18.0-22.23
  ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 24 10:25 seq
   crw-rw 1 root audio 116, 33 Jun 24 10:25 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jun 24 10:30:59 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-22-generic N/A
   linux-backports-modules-4.18.0-22-generic  N/A
   linux-firmware 1.175.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes

** Tags added: hwe

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

Title:
  cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing
  nodes

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

Bug description:
  <<>>
  incrementing stop
  Name:   cpuhotplug03
  Date:   Thu Jul 11 08:31:48 UTC 2019
  Desc:   Do tasks get scheduled to a newly on-lined CPU?

  CPU is 1
  sh: echo: I/O error
  cpuhotplug03 1 TBROK: CPU1 cannot be offlined
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  root  4642  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4643  0.0  0.0   2020   480 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4644  0.0  0.0   2020   468 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4645  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4646  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4647  0.0  0.0   2020   480 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4648  0.0  0.0   2020   456 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4649  0.0  0.0   2020   508 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4650  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4651  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4652  0.0  0.0   2020   484 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4653  0.0  0.0   2020   496 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4654  0.0  0.0   2020   464 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4655  0.0  0.0   2020   492 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4656  0.0  0.0   2020   448 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4657  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4661  0.0  0.0   7540   648 pts/0S08:31   0:00 grep 
cpuhotplug_do_spin_loop
  cpuhotplug03 1 TINFO: Onlining CPU 1
7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  cpuhotplug03 1 TPASS: 2 cpuhotplug_do_spin_loop processes found onCPU1
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=2 corefile=no
  cutime=1060 cstime=9
  <<>>

  
  Test passed on ThunderX ARM64, probably a test case issue.

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jul 11 08:22:51 2019

[Kernel-packages] [Bug 1853610] Re: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails

** Tags added: hwe

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

Title:
  mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in
  ubuntu_ltp fails

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

Bug description:
  Series: E
  Problem: commands test in ubuntu_ltp fails on E, test cases listed below:
   * mkfs01_ext3_sh
   * mkfs01_ext4_sh
   * nm01_sh

   startup='Fri Dec 6 02:30:45 2019'
   mkfs01 1 TINFO: timeout per run is 0h 5m 0s
   tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop2'
   mkfs01 1 TPASS: 'mkfs -t ext3 /dev/loop2 ' passed.
   mkfs01 2 TFAIL: 'mkfs -t ext3 /dev/loop2 16000' failed, not expected.
   mkfs01 3 TPASS: 'mkfs -t ext3 -c /dev/loop2 ' passed.
   mkfs01 4 TPASS: 'mkfs -V ' passed.
   mkfs01 5 TPASS: 'mkfs -h ' passed.
   mkfs01 6 TINFO: AppArmor enabled, this may affect test results
   mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root) 
   mkfs01 6 TINFO: loaded AppArmor profiles: none

   Summary:
   passed 4
   failed 1
   skipped 0
   warnings 0
   tag=mkfs01_ext3_sh stime=1575599445 dur=2 exit=exited stat=1 core=no cu=8 
cs=12

   tag=mkfs01_ext3_sh stime=1575599445 dur=2 exit=exited stat=1 core=no cu=8 
cs=12
   startup='Fri Dec 6 02:30:52 2019'
   mkfs01 1 TINFO: timeout per run is 0h 5m 0s
   tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop2'
   mkfs01 1 TPASS: 'mkfs -t ext4 /dev/loop2 ' passed.
   mkfs01 2 TFAIL: 'mkfs -t ext4 /dev/loop2 16000' failed, not expected.
   mkfs01 3 TPASS: 'mkfs -t ext4 -c /dev/loop2 ' passed.
   mkfs01 4 TPASS: 'mkfs -V ' passed.
   mkfs01 5 TPASS: 'mkfs -h ' passed.
   mkfs01 6 TINFO: AppArmor enabled, this may affect test results
   mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root) 
   mkfs01 6 TINFO: loaded AppArmor profiles: none

   Summary:
   passed 4
   failed 1
   skipped 0
   warnings 0
   tag=mkfs01_ext4_sh stime=1575599452 dur=2 exit=exited stat=1 core=no cu=4 
cs=1

   startup='Fri Dec 6 02:28:44 2019'
   nm01 1 TINFO: timeout per run is 0h 5m 0s
   nm01 1 TPASS: nm -f posix -A lib.a > nm.out passed as expected
   nm01 1 TPASS: Got correct listing
   nm01 1 TPASS: nm -f posix -A dir/lib.a > nm.out passed as expected
   nm01 1 TPASS: Got correct listing
   nm01 2 TPASS: nm -f posix -g /opt/ltp/testcases/data/nm01/f1 > nm.out passed 
as expected
   nm01 2 TPASS: Got only external symbols with -g
   nm01 3 TPASS: nm -f posix -t o /opt/ltp/testcases/data/nm01/f1 > nm.out 
passed as expected
   nm01 3 TPASS: Got an octal symbol values with -f
   nm01 4 TPASS: nm -f sysv /opt/ltp/testcases/data/nm01/f1 > nm.out passed as 
expected
   nm01 4 TPASS: Got SysV format with -f sysv
   nm01 5 TPASS: nm -f bsd /opt/ltp/testcases/data/nm01/f1 > nm_bsd.out passed 
as expected
   nm01 5 TPASS: nm -f posix /opt/ltp/testcases/data/nm01/f1 > nm_posix.out 
passed as expected
   nm01 5 TFAIL: Got wrong format with -f bsd
   3dc8 d _DYNAMIC
   3fb8 d _GLOBAL_OFFSET_TABLE_
   2000 R _IO_stdin_used
   w _ITM_deregisterTMCloneTable
   w _ITM_registerTMCloneTable
   2154 r __FRAME_END__
   2010 r __GNU_EH_FRAME_HDR
   4010 D __TMC_END__
   4010 B __bss_start
   w __cxa_finalize@@GLIBC_2.2.5
   4000 D __data_start
   1120 t __do_global_dtors_aux
   3dc0 d __do_global_dtors_aux_fini_array_entry
   4008 D __dso_handle
   3db8 d __frame_dummy_init_array_entry
   w __gmon_start__
   3dc0 d __init_array_end
   3db8 d __init_array_start
   11e0 T __libc_csu_fini
   1170 T __libc_csu_init
   U __libc_start_main@@GLIBC_2.2.5
   4010 D _edata
   4018 B _end
   11e8 T _fini
   1000 t _init
   1080 T _start
   4010 b completed.8055
   4000 W data_start
   10b0 t deregister_tm_clones
   1160 t frame_dummy
   1060 T main
   U puts@@GLIBC_2.2.5
   10e0 t register_tm_clones
   nm01 6 TPASS: nm -f sysv -u /opt/ltp/testcases/data/nm01/f1 > nm.out passed 
as expected
   nm01 6 TPASS: Got undefined symbols with -u
   nm01 7 TPASS: nm -s /opt/ltp/testcases/data/nm01/lib.a > nm.out passed as 
expected
   nm01 7 TPASS: Got index with -s
   nm01 8 TINFO: AppArmor enabled, this may affect test results
   nm01 8 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
   nm01 8 TINFO: loaded AppArmor profiles: none

   Summary:
   passed 16
   failed 1
   skipped 0
   warnings 0
   tag=nm01_sh stime=1575599324 dur=0 exit=exited stat=1 core=no cu=3 cs=0

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

--

[Kernel-packages] [Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed

** Tags added: hwe

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

Title:
  crypto_user02 in crypto from ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This is a new test, test will fail with:

  <<>>
  tag=crypto_user02 stime=1563881396
  cmdline="crypto_user02"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  crypto_user02.c:59: INFO: Starting crypto_user larval deletion test.  May 
crash buggy kernels.
  crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY

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

  
  Nothing interesting in syslog:
  Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu.
  Jul 23 11:29:56 amaura kernel: [  619.646330] LTP: starting crypto_user02
  Jul 23 11:30:23 amaura kernel: [  646.554403] cfg80211: Loading compiled-in 
X.509 certificates for regulatory database

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-21-generic 5.0.0-21.22
  ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 23 11:19 seq
   crw-rw 1 root audio 116, 33 Jul 23 11:19 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 23 11:30:15 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-21-generic N/A
   linux-backports-modules-5.0.0-21-generic  N/A
   linux-firmware1.178.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1844493] Re: ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 / 5.6 /5.8 / 5.10 kernels

** Tags added: hwe

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

Title:
  ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 / 5.6 /5.8 / 5.10 kernels

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux source package in Eoan:
  Incomplete
Status in linux-aws source package in Eoan:
  New
Status in linux-azure source package in Eoan:
  New
Status in linux-gcp source package in Eoan:
  New
Status in linux source package in Focal:
  New
Status in linux-aws source package in Focal:
  New
Status in linux-azure source package in Focal:
  New
Status in linux-gcp source package in Focal:
  New

Bug description:
  Test failed with:
FAILED (trace at least 25 reads of /dev/zero by dd)
FAILED (trace at least 25 writes to /dev/null by dd)

  Steps:
sudo apt-get install git python-minimal python-yaml gdb -y
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_sysdig_smoke_test/control

  Test output:
== sysdig smoke test to trace dd, cat, read and writes ==
Limiting raw capture file to 16384 blocks
Try 1 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 18 Mbytes
Try 2 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 22 Mbytes
Try 3 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 4 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 5 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 6 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 7 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 8 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 9 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 10 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Found:
   279845 sysdig events
   29882 context switches
   0 reads from /dev/zero by dd
   0 writes to /dev/null by dd
PASSED (trace at least 25 context switches)
FAILED (trace at least 25 reads of /dev/zero by dd)
FAILED (trace at least 25 writes to /dev/null by dd)
 
Summary: 1 passed, 2 failed

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-10-generic 5.3.0-10.11
  ProcVersionSignature: User Name 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 18 08:10 seq
   crw-rw 1 root audio 116, 33 Sep 18 08:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed Sep 18 08:18:54 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17

[Kernel-packages] [Bug 1847982] Re: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E

** Tags added: 5.8 hwe

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

Title:
  memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux-kvm source package in Disco:
  Won't Fix
Status in linux-oracle source package in Disco:
  Won't Fix

Bug description:
  Issue found on Azure Disco kernel 5.0.0-1023.24

  Failed on instance:
* Standard_GS2
* Standard_D16s_v3

  Passed on instance:
* Standard_F32s_v2
* Standard_L8s_v2
* Standard_L4s
* Standard_L8s_v2

  (Although it has passed on these instances, but they all have the same
  test output, just the pids are different)

  
  Test failed with:
    /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error

   tag=memcg_subgroup_charge stime=1570239843 dur=3 exit=exited stat=1 core=no 
cu=7 cs=11
   startup='Sat Oct 5 01:44:03 2019'
   memcg_subgroup_charge 1 TINFO: Starting test 1
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 1 TINFO: Warming up pid: 119041
   memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 119041
   memcg_subgroup_charge 1 TPASS: rss is 135168 as expected
   memcg_subgroup_charge 2 TPASS: rss is 0 as expected
   memcg_subgroup_charge 3 TINFO: Starting test 2
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 3 TINFO: Warming up pid: 119071
   memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 119071
   memcg_subgroup_charge 3 TFAIL: rss is 0, 135168 expected
   memcg_subgroup_charge 4 TPASS: rss is 0 as expected
   memcg_subgroup_charge 5 TINFO: Starting test 3
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 5 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 5 TINFO: Warming up pid: 119094
   memcg_subgroup_charge 5 TINFO: Process is still here after warm up: 119094
   memcg_subgroup_charge 5 TPASS: rss is 135168 as expected
   memcg_subgroup_charge 6 TPASS: rss is 0 as expected

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

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

[Kernel-packages] [Bug 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'

** Tags added: hwe

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

Title:
  tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With bug 1868707 fixed, the tpci test can finish now, and it's reporting 
another issue here:
     test_pci  489  TFAIL  :  tpci.c:73: PCI bus 01 slot 01 : Test-case '13'

  Please find attachment for dmesg log and the full test log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 13 10:08 seq
   crw-rw 1 root audio 116, 33 May 13 10:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Wed May 13 10:19:01 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H

** Tags added: hwe

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

Title:
  icmp_redirect.sh in net from ubuntu_kernel_selftests failed on
  F-OEM-5.6 / G / H

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-signed-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux-signed-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  Issue found on Focal 5.6.0-1011.11-oem


  
ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$
  sudo ./icmp_redirect.sh

  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [ OK ]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [ OK ]
  TEST: IPv6: mtu exception plus redirect [FAIL]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [ OK ]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [ OK ]
  TEST: IPv6: mtu exception plus redirect [FAIL]

  ###
  Routing with nexthop objects
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [ OK ]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [ OK ]
  TEST: IPv6: mtu exception plus redirect [FAIL]

  ###
  Routing with nexthop objects and VRF
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [ OK ]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [ OK ]
  TEST: IPv6: mtu exception plus redirect [FAIL]

  Tests passed:  36
  Tests failed:   4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.6.0-1011-oem 5.6.0-1011.11
  ProcVersionSignature: User Name 5.6.0-1011.11-oem 5.6.14
  Uname: Linux 5.6.0-1011-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64

[Kernel-packages] [Bug 1892860] Re: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B-arm64

** Tags added: hwe

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

Title:
  af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on
  B-arm64

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

Bug description:
  Issue found on 4.15.0-114.115-generic with ARM64 node appleton-kernel
  and wright-kernel.

  Looks like this is a new test case added 13 days ago:
  
https://github.com/linux-test-project/ltp/commit/fdff6139e43aa9b19f27907f6d7f2cb4765632a1#diff-8a83d6b2c6c7d74e750e3af47e3f4a79

  The test will fail with:
   startup='Fri Aug 14 10:13:27 2020'
   tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
   tst_taint.c:88: CONF: Ignoring already set kernel warning taint
   ../../../include/tst_fuzzy_sync.h:507: INFO: Minimum sampling period ended
   ../../../include/tst_fuzzy_sync.h:331: INFO: loop = 1024, delay_bias = 0
   ../../../include/tst_fuzzy_sync.h:320: INFO: start_a - start_b: { avg = 
-2259470ns, avg_dev = 13695382ns, dev_ratio = 6.06 }
   ../../../include/tst_fuzzy_sync.h:320: INFO: end_a - start_a : { avg = 
13968ns, avg_dev = 4310ns, dev_ratio = 0.31 } 
   ../../../include/tst_fuzzy_sync.h:320: INFO: end_b - start_b : { avg = 
15975ns, avg_dev = 50ns, dev_ratio = 0.00 } 
   ../../../include/tst_fuzzy_sync.h:320: INFO: end_a - end_b : { avg = 
-2261477ns, avg_dev = 13699742ns, dev_ratio = 6.06 }
   ../../../include/tst_fuzzy_sync.h:320: INFO: spins : { avg = 3575095 , 
avg_dev = 4553 , dev_ratio = 0.00 } 
   ../../../include/tst_fuzzy_sync.h:637: INFO: Exceeded execution time, 
requesting exit
   af_alg07.c:97: FAIL: fchownat() failed to fail, kernel may be vulnerable

   HINT: You _MAY_ be missing kernel fixes, see:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9060cb719e61

   HINT: You _MAY_ be vulnerable to CVE(s), see:

   https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8912

   Summary:
   passed 0
   failed 1
   skipped 1
   warnings 0
   tag=af_alg07 stime=159747 dur=150 exit=exited stat=33 core=no cu=15051 
cs=0

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

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

[Kernel-packages] [Bug 1897764] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM

** Tags added: hwe

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

Title:
  mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests
  failed on X-gcp-4.15 / F-5.4 zVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  Issue found on Focal 5.4.0-49.53 zVM kernel04

  Test failed with:
   # selftests: memory-hotplug: mem-on-off-test.sh
   # Test scope: 2% hotplug memory
   # online all hot-pluggable memory in offline state:
   # SKIPPED - no hot-pluggable memory in offline state
   # offline 2% hot-pluggable memory in online state
   # trying to offline 1 out of 16 memory block(s):
   # online->offline memory0
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 0: unexpected fail
   # online->offline memory1
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 1: unexpected fail
   # online->offline memory10
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 10: unexpected fail
   # online->offline memory11
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 11: unexpected fail
   # online->offline memory12
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 12: unexpected fail
   # online->offline memory13
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 13: unexpected fail
   # online->offline memory14
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 14: unexpected fail
   # online->offline memory15
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 15: unexpected fail
   # online->offline memory2
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 2: unexpected fail
   # online->offline memory3
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 3: unexpected fail
   # online->offline memory4
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 4: unexpected fail
   # online->offline memory5
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 5: unexpected fail
   # online->offline memory6
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 6: unexpected fail
   # online->offline memory7
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 7: unexpected fail
   # online->offline memory8
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 8: unexpected fail
   # online->offline memory9
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 9: unexpected fail
   # FAILED - unable to offline some memory blocks, device busy?
   # online all hot-pluggable memory in offline state:
   # SKIPPED - no hot-pluggable memory in offline state
   # Test with memory notifier error injection
   not ok 1 selftests: memory-hotplug: mem-on-off-test.sh # exit=1

  This issue can be found on 5.4.0-46.50, 5.4.0-45.49 zVM as well.
  Passed with 5.4.0-44.48
  Passed with 5.4.0-43.47
  Failed with 5.4.0-42.46

  Looks like it's not very stable.

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

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

[Kernel-packages] [Bug 1828026] Re: gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64

Seeing this on Focal/linux 5.8.0-49.55~20.04.1 generic-64k. Both tests
gicv2-mmio-3p and gicv2-mmio-up are failing (similar to LP#1802492 which
was marked as a duplicate of this bug). These failures look to only be
appearing with the host mcdivitt34-kernel


gicv2-mmio-3p output:

03/27 17:50:48 DEBUG| utils:0153| [stdout] FAIL: gicv2: mmio: ITARGETSR: 
bits for 5 non-existent CPUs masked
03/27 17:50:48 DEBUG| utils:0153| [stdout] PASS: gicv2: mmio: ITARGETSR: 
accesses beyond limit RAZ/WI
03/27 17:50:48 DEBUG| utils:0153| [stdout] FAIL: gicv2: mmio: ITARGETSR: 
register content preserved (01030207 => 0103020f)
03/27 17:50:48 DEBUG| utils:0153| [stdout] PASS: gicv2: mmio: ITARGETSR: 
byte reads successful (0x01030207 => 0x02)
03/27 17:50:48 DEBUG| utils:0153| [stdout] FAIL: gicv2: mmio: ITARGETSR: 
byte writes successful (0x1f => 0x011f020f)
03/27 17:50:48 DEBUG| utils:0153| [stdout] SUMMARY: 17 tests, 3 unexpected 
failures
03/27 17:50:48 DEBUG| utils:0153| [stdout] FAIL gicv2-mmio-3p (17 tests, 3 
unexpected failures)


gicv2-mmio-up output:

03/27 17:50:50 DEBUG| utils:0153| [stdout] FAIL: gicv2: mmio: ITARGETSR: 
register content preserved (01010001 => )
03/27 17:50:50 DEBUG| utils:0153| [stdout] PASS: gicv2: mmio: ITARGETSR: 
byte reads successful (0x01010001 => 0x00)
03/27 17:50:50 DEBUG| utils:0153| [stdout] FAIL: gicv2: mmio: ITARGETSR: 
byte writes successful (0x1f => 0x)
03/27 17:50:50 DEBUG| utils:0153| [stdout] SUMMARY: 17 tests, 2 unexpected 
failures
03/27 17:50:50 DEBUG| utils:0153| [stdout] FAIL gicv2-mmio-up (17 tests, 2 
unexpected failures)


** Tags added: 5.8 focal sru-20210315

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

Title:
  gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64

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

Bug description:
  Failed on Moonshot nodes.

  
  FAIL gicv2-mmio-up (17 tests, 2 unexpected failures)

  # TESTNAME=gicv2-mmio-up TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 1 
-machine gic-version=2 -append 'mmio'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/gic.flat -smp 1 -machine gic-version=2 
-append mmio # -initrd /tmp/tmp.6k28Ehxzim
  INFO: gicv2: mmio: number of implemented SPIs: 256
  PASS: gicv2: mmio: all 1 CPUs have interrupts
  INFO: gicv2: mmio: IIDR: 0x
  PASS: gicv2: mmio: GICD_TYPER is read-only
  PASS: gicv2: mmio: GICD_IIDR is read-only
  PASS: gicv2: mmio: ICPIDR2 is read-only (0x0004)
  PASS: gicv2: mmio: IPRIORITYR: consistent priority masking (0x)
  PASS: gicv2: mmio: IPRIORITYR: implements at least 4 priority bits (8)
  PASS: gicv2: mmio: IPRIORITYR: clearing priorities
  PASS: gicv2: mmio: IPRIORITYR: accesses beyond limit RAZ/WI
  PASS: gicv2: mmio: IPRIORITYR: accessing last SPIs
  PASS: gicv2: mmio: IPRIORITYR: priorities are preserved
  PASS: gicv2: mmio: IPRIORITYR: byte reads successful (0xff7fbf3f => 0xbf)
  PASS: gicv2: mmio: IPRIORITYR: byte writes successful (0x1f => 0xff1fbf3f)
  PASS: gicv2: mmio: ITARGETSR: bits for 7 non-existent CPUs masked
  PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI
  FAIL: gicv2: mmio: ITARGETSR: register content preserved (01010001 => 
)
  PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x01010001 => 0x00)
  FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x)
  SUMMARY: 17 tests, 2 unexpected failures

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51~16.04.1
  ProcVersionSignature: User Name 4.15.0-48.51~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-48-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: arm64
  Date: Tue May  7 11:25:30 2019
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

** Tags added: hwe sru-20210315

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

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

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

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

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

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

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

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

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

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

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

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

2021-04-06 Thread koba

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

** Tags added: originate-from-1912745

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

Title:
  Update - Fix no screen show on display after S3 on CML-R

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  New

Bug description:
  [Impact]
  On CML-R, after S3, No screen show on all three connector(3*DP).

  [Fix]
  Here's v4 patch and has been landed on drm-tip,
  
https://patchwork.freedesktop.org/patch/msgid/20210217180016.1937401-1-ly...@redhat.com,
  so revert the old and resend the v4 patch. 
  For Legacy S3 suspend/resume GEN9 BC needs to enable and setup TGP PCH.

  [Test Case]
  1. Connected the monitor on one of 3*DP on CML-R.
  2. Suspend the machine.
  3. Check the monitor can output something.

  [Where problems could occur]
  Just Enable the hpd detection in IRQ installer and during suspend

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

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

[Kernel-packages] [Bug 1892860] Re: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B-arm64

** Tags added: sru-20210315

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

Title:
  af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on
  B-arm64

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

Bug description:
  Issue found on 4.15.0-114.115-generic with ARM64 node appleton-kernel
  and wright-kernel.

  Looks like this is a new test case added 13 days ago:
  
https://github.com/linux-test-project/ltp/commit/fdff6139e43aa9b19f27907f6d7f2cb4765632a1#diff-8a83d6b2c6c7d74e750e3af47e3f4a79

  The test will fail with:
   startup='Fri Aug 14 10:13:27 2020'
   tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
   tst_taint.c:88: CONF: Ignoring already set kernel warning taint
   ../../../include/tst_fuzzy_sync.h:507: INFO: Minimum sampling period ended
   ../../../include/tst_fuzzy_sync.h:331: INFO: loop = 1024, delay_bias = 0
   ../../../include/tst_fuzzy_sync.h:320: INFO: start_a - start_b: { avg = 
-2259470ns, avg_dev = 13695382ns, dev_ratio = 6.06 }
   ../../../include/tst_fuzzy_sync.h:320: INFO: end_a - start_a : { avg = 
13968ns, avg_dev = 4310ns, dev_ratio = 0.31 } 
   ../../../include/tst_fuzzy_sync.h:320: INFO: end_b - start_b : { avg = 
15975ns, avg_dev = 50ns, dev_ratio = 0.00 } 
   ../../../include/tst_fuzzy_sync.h:320: INFO: end_a - end_b : { avg = 
-2261477ns, avg_dev = 13699742ns, dev_ratio = 6.06 }
   ../../../include/tst_fuzzy_sync.h:320: INFO: spins : { avg = 3575095 , 
avg_dev = 4553 , dev_ratio = 0.00 } 
   ../../../include/tst_fuzzy_sync.h:637: INFO: Exceeded execution time, 
requesting exit
   af_alg07.c:97: FAIL: fchownat() failed to fail, kernel may be vulnerable

   HINT: You _MAY_ be missing kernel fixes, see:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9060cb719e61

   HINT: You _MAY_ be vulnerable to CVE(s), see:

   https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8912

   Summary:
   passed 0
   failed 1
   skipped 1
   warnings 0
   tag=af_alg07 stime=159747 dur=150 exit=exited stat=33 core=no cu=15051 
cs=0

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

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

[Kernel-packages] [Bug 1912511] Re: [SRU] Add support for E810 NIC to Ice Driver in Focal

2021-04-06 Thread Michael Reed

I have created a test kernel with this patch.

https://people.canonical.com/~mreed/lp1912511_e810/

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

Title:
  [SRU] Add support for E810 NIC to Ice Driver in Focal

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact] 
  The Intel Ice driver in 5.4 does not contain the PCIIDs necessary to allow 
the driver to see the E810 network cards.  Without this, users running Focal GA 
will be unable to deploy Ubuntu via MAAS, or use these cards at all 
post-install when installing from an ISO.

  The patch to resolve this landed in Groovy, so this should be a pretty
  straightforward pick to 5.4.  The patch set is small.

  [Test Case]

  This is easily reproducible by simply trying to install Focal onto a
  system with an E810 NIC.  The NIC is not recognized and thus is not
  configurable or usable.

  [Where problems could occur]

  All this patch does is add PCI ID information for E810 to the driver
  to enable a wider set of cards to be used. Problems should not involve
  regressions to existing supported hardware, if anything the biggest
  issue could be discovering that after adding the PCI IDs, further
  patches are necessary to fully enable support in the Ice driver.

  [Other Info]
   
  This was reported by a hardware partner and blocks certification for systems 
that use E810 based NICs as their primary network devices.

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

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

[Kernel-packages] [Bug 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes

** Tags added: sru-20210315

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

Title:
  cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing
  nodes

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

Bug description:
  <<>>
  incrementing stop
  Name:   cpuhotplug03
  Date:   Thu Jul 11 08:31:48 UTC 2019
  Desc:   Do tasks get scheduled to a newly on-lined CPU?

  CPU is 1
  sh: echo: I/O error
  cpuhotplug03 1 TBROK: CPU1 cannot be offlined
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  root  4642  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4643  0.0  0.0   2020   480 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4644  0.0  0.0   2020   468 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4645  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4646  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4647  0.0  0.0   2020   480 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4648  0.0  0.0   2020   456 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4649  0.0  0.0   2020   508 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4650  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4651  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4652  0.0  0.0   2020   484 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4653  0.0  0.0   2020   496 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4654  0.0  0.0   2020   464 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4655  0.0  0.0   2020   492 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4656  0.0  0.0   2020   448 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4657  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4661  0.0  0.0   7540   648 pts/0S08:31   0:00 grep 
cpuhotplug_do_spin_loop
  cpuhotplug03 1 TINFO: Onlining CPU 1
7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  cpuhotplug03 1 TPASS: 2 cpuhotplug_do_spin_loop processes found onCPU1
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=2 corefile=no
  cutime=1060 cstime=9
  <<>>

  
  Test passed on ThunderX ARM64, probably a test case issue.

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jul 11 08:22:51

[Kernel-packages] [Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed

** Tags added: sru-20210315

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

Title:
  getaddrinfo_01 from ipv6_lib test suite in LTP failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Eoan:
  New
Status in linux-aws source package in Eoan:
  New

Bug description:
  startup='Wed May 22 08:02:52 2019'
  getaddrinfo_011  TPASS  :  getaddrinfo IPv4 basic lookup
  getaddrinfo_012  TFAIL  :  getaddrinfo_01.c:140: getaddrinfo IPv4 
canonical name ("curly.maas") doesn't match hostname ("curly")
  getaddrinfo_013  TFAIL  :  getaddrinfo_01.c:578: getaddrinfo IPv6 basic 
lookup ("curly") returns -5 ("No address associated with hostname")
  tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed May 22 08:04:30 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1853610] Re: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails

** Tags added: sru-20210315

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

Title:
  mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in
  ubuntu_ltp fails

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

Bug description:
  Series: E
  Problem: commands test in ubuntu_ltp fails on E, test cases listed below:
   * mkfs01_ext3_sh
   * mkfs01_ext4_sh
   * nm01_sh

   startup='Fri Dec 6 02:30:45 2019'
   mkfs01 1 TINFO: timeout per run is 0h 5m 0s
   tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop2'
   mkfs01 1 TPASS: 'mkfs -t ext3 /dev/loop2 ' passed.
   mkfs01 2 TFAIL: 'mkfs -t ext3 /dev/loop2 16000' failed, not expected.
   mkfs01 3 TPASS: 'mkfs -t ext3 -c /dev/loop2 ' passed.
   mkfs01 4 TPASS: 'mkfs -V ' passed.
   mkfs01 5 TPASS: 'mkfs -h ' passed.
   mkfs01 6 TINFO: AppArmor enabled, this may affect test results
   mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root) 
   mkfs01 6 TINFO: loaded AppArmor profiles: none

   Summary:
   passed 4
   failed 1
   skipped 0
   warnings 0
   tag=mkfs01_ext3_sh stime=1575599445 dur=2 exit=exited stat=1 core=no cu=8 
cs=12

   tag=mkfs01_ext3_sh stime=1575599445 dur=2 exit=exited stat=1 core=no cu=8 
cs=12
   startup='Fri Dec 6 02:30:52 2019'
   mkfs01 1 TINFO: timeout per run is 0h 5m 0s
   tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop2'
   mkfs01 1 TPASS: 'mkfs -t ext4 /dev/loop2 ' passed.
   mkfs01 2 TFAIL: 'mkfs -t ext4 /dev/loop2 16000' failed, not expected.
   mkfs01 3 TPASS: 'mkfs -t ext4 -c /dev/loop2 ' passed.
   mkfs01 4 TPASS: 'mkfs -V ' passed.
   mkfs01 5 TPASS: 'mkfs -h ' passed.
   mkfs01 6 TINFO: AppArmor enabled, this may affect test results
   mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root) 
   mkfs01 6 TINFO: loaded AppArmor profiles: none

   Summary:
   passed 4
   failed 1
   skipped 0
   warnings 0
   tag=mkfs01_ext4_sh stime=1575599452 dur=2 exit=exited stat=1 core=no cu=4 
cs=1

   startup='Fri Dec 6 02:28:44 2019'
   nm01 1 TINFO: timeout per run is 0h 5m 0s
   nm01 1 TPASS: nm -f posix -A lib.a > nm.out passed as expected
   nm01 1 TPASS: Got correct listing
   nm01 1 TPASS: nm -f posix -A dir/lib.a > nm.out passed as expected
   nm01 1 TPASS: Got correct listing
   nm01 2 TPASS: nm -f posix -g /opt/ltp/testcases/data/nm01/f1 > nm.out passed 
as expected
   nm01 2 TPASS: Got only external symbols with -g
   nm01 3 TPASS: nm -f posix -t o /opt/ltp/testcases/data/nm01/f1 > nm.out 
passed as expected
   nm01 3 TPASS: Got an octal symbol values with -f
   nm01 4 TPASS: nm -f sysv /opt/ltp/testcases/data/nm01/f1 > nm.out passed as 
expected
   nm01 4 TPASS: Got SysV format with -f sysv
   nm01 5 TPASS: nm -f bsd /opt/ltp/testcases/data/nm01/f1 > nm_bsd.out passed 
as expected
   nm01 5 TPASS: nm -f posix /opt/ltp/testcases/data/nm01/f1 > nm_posix.out 
passed as expected
   nm01 5 TFAIL: Got wrong format with -f bsd
   3dc8 d _DYNAMIC
   3fb8 d _GLOBAL_OFFSET_TABLE_
   2000 R _IO_stdin_used
   w _ITM_deregisterTMCloneTable
   w _ITM_registerTMCloneTable
   2154 r __FRAME_END__
   2010 r __GNU_EH_FRAME_HDR
   4010 D __TMC_END__
   4010 B __bss_start
   w __cxa_finalize@@GLIBC_2.2.5
   4000 D __data_start
   1120 t __do_global_dtors_aux
   3dc0 d __do_global_dtors_aux_fini_array_entry
   4008 D __dso_handle
   3db8 d __frame_dummy_init_array_entry
   w __gmon_start__
   3dc0 d __init_array_end
   3db8 d __init_array_start
   11e0 T __libc_csu_fini
   1170 T __libc_csu_init
   U __libc_start_main@@GLIBC_2.2.5
   4010 D _edata
   4018 B _end
   11e8 T _fini
   1000 t _init
   1080 T _start
   4010 b completed.8055
   4000 W data_start
   10b0 t deregister_tm_clones
   1160 t frame_dummy
   1060 T main
   U puts@@GLIBC_2.2.5
   10e0 t register_tm_clones
   nm01 6 TPASS: nm -f sysv -u /opt/ltp/testcases/data/nm01/f1 > nm.out passed 
as expected
   nm01 6 TPASS: Got undefined symbols with -u
   nm01 7 TPASS: nm -s /opt/ltp/testcases/data/nm01/lib.a > nm.out passed as 
expected
   nm01 7 TPASS: Got index with -s
   nm01 8 TINFO: AppArmor enabled, this may affect test results
   nm01 8 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
   nm01 8 TINFO: loaded AppArmor profiles: none

   Summary:
   passed 16
   failed 1
   skipped 0
   warnings 0
   tag=nm01_sh stime=1575599324 dur=0 exit=exited stat=1 core=no cu=3 cs=0

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

[Kernel-packages] [Bug 1847982] Re: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E

** Tags added: sru-20210315

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

Title:
  memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux-kvm source package in Disco:
  Won't Fix
Status in linux-oracle source package in Disco:
  Won't Fix

Bug description:
  Issue found on Azure Disco kernel 5.0.0-1023.24

  Failed on instance:
* Standard_GS2
* Standard_D16s_v3

  Passed on instance:
* Standard_F32s_v2
* Standard_L8s_v2
* Standard_L4s
* Standard_L8s_v2

  (Although it has passed on these instances, but they all have the same
  test output, just the pids are different)

  
  Test failed with:
    /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error

   tag=memcg_subgroup_charge stime=1570239843 dur=3 exit=exited stat=1 core=no 
cu=7 cs=11
   startup='Sat Oct 5 01:44:03 2019'
   memcg_subgroup_charge 1 TINFO: Starting test 1
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 1 TINFO: Warming up pid: 119041
   memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 119041
   memcg_subgroup_charge 1 TPASS: rss is 135168 as expected
   memcg_subgroup_charge 2 TPASS: rss is 0 as expected
   memcg_subgroup_charge 3 TINFO: Starting test 2
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 3 TINFO: Warming up pid: 119071
   memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 119071
   memcg_subgroup_charge 3 TFAIL: rss is 0, 135168 expected
   memcg_subgroup_charge 4 TPASS: rss is 0 as expected
   memcg_subgroup_charge 5 TINFO: Starting test 3
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 5 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 5 TINFO: Warming up pid: 119094
   memcg_subgroup_charge 5 TINFO: Process is still here after warm up: 119094
   memcg_subgroup_charge 5 TPASS: rss is 135168 as expected
   memcg_subgroup_charge 6 TPASS: rss is 0 as expected

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

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

[Kernel-packages] [Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed

** Tags added: sru-20210315

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

Title:
  crypto_user02 in crypto from ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This is a new test, test will fail with:

  <<>>
  tag=crypto_user02 stime=1563881396
  cmdline="crypto_user02"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  crypto_user02.c:59: INFO: Starting crypto_user larval deletion test.  May 
crash buggy kernels.
  crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY

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

  
  Nothing interesting in syslog:
  Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu.
  Jul 23 11:29:56 amaura kernel: [  619.646330] LTP: starting crypto_user02
  Jul 23 11:30:23 amaura kernel: [  646.554403] cfg80211: Loading compiled-in 
X.509 certificates for regulatory database

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-21-generic 5.0.0-21.22
  ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 23 11:19 seq
   crw-rw 1 root audio 116, 33 Jul 23 11:19 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 23 11:30:15 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-21-generic N/A
   linux-backports-modules-5.0.0-21-generic  N/A
   linux-firmware1.178.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'

** Tags added: sru-20210315

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

Title:
  tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With bug 1868707 fixed, the tpci test can finish now, and it's reporting 
another issue here:
     test_pci  489  TFAIL  :  tpci.c:73: PCI bus 01 slot 01 : Test-case '13'

  Please find attachment for dmesg log and the full test log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 13 10:08 seq
   crw-rw 1 root audio 116, 33 May 13 10:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Wed May 13 10:19:01 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed

** Tags added: sru-20210315

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

Title:
  memcg_usage_in_bytes from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in linux-aws source package in Cosmic:
  New

Bug description:
   startup='Wed May 22 05:59:09 2019'
   memcg_usage_in_bytes_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 
4194304
   memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689
   memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689
   memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 
expected
   memcg_usage_in_bytes_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled
   tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no 
cu=5 cs=3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed

** Tags added: sru-20210315

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

Title:
  cpuset_hotplug from controllers in ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux-aws source package in Focal:
  New
Status in linux-azure source package in Focal:
  New

Bug description:
  Issue found on node amaura:
  <<>>
  tag=cpuset_hotplug stime=1561372131
  cmdline="cpuset_hotplug_test.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
  cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
  cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded.
  cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, 
Expect: 0-7).
  cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded.
  cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded.
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=1 corefile=no
  cutime=19 cstime=81
  <<>>

  Test script:
  
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-22-generic 4.18.0-22.23
  ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 24 10:25 seq
   crw-rw 1 root audio 116, 33 Jun 24 10:25 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jun 24 10:30:59 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-22-generic N/A
   linux-backports-modules-4.18.0-22-generic  N/A
   linux-firmware 1.175.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1890641] Re: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169

2021-04-06 Thread Brian Murray

Could you please provide some details regarding the steps you took to
verify that this SRU was good?

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

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

Title:
  Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for
  module r8169

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Missing firmware for Realtek RTL8153 Based USB Ethernet Adapters,
  which is supported by linux-generic-hwe-18.04 kernel (currently v5.4).

  [Fix]

  Two upstream commit necessary:
  * commit b27d12383e7a ("rtl_nic: add firmware files for RTL8153")
  * commit 6f89735800fe ("rtl_nic: update firmware for RTL8153A")

  [Test Case]

  Without firmware, drive probe would fail with:

$ dmesg | grep firmware | grep rtl8153
r8152 2-4.1:1.0: firmware: failed to load rtl_nic/rtl8153a-2.fw (-2)
r8152 2-4.1:1.0: Direct firmware load for rtl_nic/rtl8153a-2.fw failed with 
error -2
r8152 2-4.1:1.0: unable to load firmware patch rtl_nic/rtl8153a-2.fw (-2)

  With firmware, it should succeed:

$ dmesg | grep rtl8152
r8152 2-1:1.0: load rtl8153a-3 v2 02/07/20 successfully
r8152 2-1:1.0 eth0: v1.11.11
r8152 2-1:1.0 enp0s20f0u1: renamed from eth0

  [Where problems could occur]

  While this introduces new firmware blobs and enabled devices supported
  by new kernels, it should have little effect on existing systems, but
  with new devices up and running, it may still affect power consumptions,
  ability to enter deep suspend, etc.

  [Other Info]

  RTL8153 firmware has been available on Eoan and newer, so only Bionic is
  nominated.

  == original bug report ==

  Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for
  module r8169

  after running sudo apt upgrade in ubuntu 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.38
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  6 22:38:31 2020
  InstallationDate: Installed on 2019-06-16 (417 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2020-03-08 22:54:00.439353
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done

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

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

[Kernel-packages] [Bug 1897764] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM

** Tags added: sru-20210315

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

Title:
  mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests
  failed on X-gcp-4.15 / F-5.4 zVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  Issue found on Focal 5.4.0-49.53 zVM kernel04

  Test failed with:
   # selftests: memory-hotplug: mem-on-off-test.sh
   # Test scope: 2% hotplug memory
   # online all hot-pluggable memory in offline state:
   # SKIPPED - no hot-pluggable memory in offline state
   # offline 2% hot-pluggable memory in online state
   # trying to offline 1 out of 16 memory block(s):
   # online->offline memory0
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 0: unexpected fail
   # online->offline memory1
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 1: unexpected fail
   # online->offline memory10
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 10: unexpected fail
   # online->offline memory11
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 11: unexpected fail
   # online->offline memory12
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 12: unexpected fail
   # online->offline memory13
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 13: unexpected fail
   # online->offline memory14
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 14: unexpected fail
   # online->offline memory15
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 15: unexpected fail
   # online->offline memory2
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 2: unexpected fail
   # online->offline memory3
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 3: unexpected fail
   # online->offline memory4
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 4: unexpected fail
   # online->offline memory5
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 5: unexpected fail
   # online->offline memory6
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 6: unexpected fail
   # online->offline memory7
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 7: unexpected fail
   # online->offline memory8
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 8: unexpected fail
   # online->offline memory9
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 9: unexpected fail
   # FAILED - unable to offline some memory blocks, device busy?
   # online all hot-pluggable memory in offline state:
   # SKIPPED - no hot-pluggable memory in offline state
   # Test with memory notifier error injection
   not ok 1 selftests: memory-hotplug: mem-on-off-test.sh # exit=1

  This issue can be found on 5.4.0-46.50, 5.4.0-45.49 zVM as well.
  Passed with 5.4.0-44.48
  Passed with 5.4.0-43.47
  Failed with 5.4.0-42.46

  Looks like it's not very stable.

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

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

[Kernel-packages] [Bug 1922800] Re: Nvidia proprietary DKMS drivers cannot build in linux-kvm 5.8 and subsequent versions

2021-04-06 Thread Guilherme G. Piccoli

Hints added to linux-kvm, so it should pass the ADT tests.

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

Title:
  Nvidia proprietary DKMS drivers cannot build in linux-kvm 5.8 and
  subsequent versions

Status in linux-kvm package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers source package in Groovy:
  New

Bug description:
  After an ADT/DKMS modification (see
  https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1915051) binary
  DKMS packages without -dkms in the name started to get tested on ADT
  run. This exposed a problem in the Nvidia proprietary DKMS modules for
  linux-kvm build:

  if we don't have CONFIG_X86_PAT set, the Nvidia drivers (all versions) set 
NV_ENABLE_BUILTIN_PAT_SUPPORT to 1 and attempt to build the file 
nvidia/nv-pat.c - two functions there make use of __flush_tlb() exported symbol.
  But, after kernel v5.8, this symbol is not exported anymore [0][1], not even 
flush_tlb_local() is available.

  For the time being, we ADT-hinted linux-kvm package, but the driver
  requires modifications, in order to fix that.

  [0] http://git.kernel.org/linus/2faf153bb734
  [1] http://git.kernel.org/linus/bfe3d8f6313d

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

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

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

This change was made by a bot.

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

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

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad not working on lenovo ideapad 5.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-48-generic 5.8.0-48.54
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pier   1120 F pulseaudio
   /dev/snd/controlC0:  pier   1120 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Apr  6 23:42:06 2021
  InstallationDate: Installed on 2021-04-06 (0 days ago)
  InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 82LM
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=2b00a467-aa8f-4985-9e05-2d408a17ff2a ro quiet splash 
processor.max_cstate=5 rcu_nocbs=0-11 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2021-04-06 (0 days ago)
  dmi.bios.date: 02/03/2021
  dmi.bios.release: 1.16
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5CN16WW(V1.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14ALC05
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5CN16WW(V1.04):bd02/03/2021:br1.16:efr1.16:svnLENOVO:pn82LM:pvrIdeaPad514ALC05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad514ALC05:
  dmi.product.family: IdeaPad 5 14ALC05
  dmi.product.name: 82LM
  dmi.product.sku: LENOVO_MT_82LM_BU_idea_FM_IdeaPad 5 14ALC05
  dmi.product.version: IdeaPad 5 14ALC05
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1922809] [NEW] Touchpad not working

2021-04-06 Thread Pier Francesco Contino

Public bug reported:

Touchpad not working on lenovo ideapad 5.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-48-generic 5.8.0-48.54
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  pier   1120 F pulseaudio
 /dev/snd/controlC0:  pier   1120 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Apr  6 23:42:06 2021
InstallationDate: Installed on 2021-04-06 (0 days ago)
InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 82LM
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=2b00a467-aa8f-4985-9e05-2d408a17ff2a ro quiet splash 
processor.max_cstate=5 rcu_nocbs=0-11 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-48-generic N/A
 linux-backports-modules-5.8.0-48-generic  N/A
 linux-firmware1.190.3
SourcePackage: linux
UpgradeStatus: Upgraded to groovy on 2021-04-06 (0 days ago)
dmi.bios.date: 02/03/2021
dmi.bios.release: 1.16
dmi.bios.vendor: LENOVO
dmi.bios.version: G5CN16WW(V1.04)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 5 14ALC05
dmi.ec.firmware.release: 1.16
dmi.modalias: 
dmi:bvnLENOVO:bvrG5CN16WW(V1.04):bd02/03/2021:br1.16:efr1.16:svnLENOVO:pn82LM:pvrIdeaPad514ALC05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad514ALC05:
dmi.product.family: IdeaPad 5 14ALC05
dmi.product.name: 82LM
dmi.product.sku: LENOVO_MT_82LM_BU_idea_FM_IdeaPad 5 14ALC05
dmi.product.version: IdeaPad 5 14ALC05
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug groovy

** Attachment added: "cat /proc/bus/input/devices > ~/devices"
   https://bugs.launchpad.net/bugs/1922809/+attachment/5484959/+files/devices

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

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  New

Bug description:
  Touchpad not working on lenovo ideapad 5.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-48-generic 5.8.0-48.54
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pier   1120 F pulseaudio
   /dev/snd/controlC0:  pier   1120 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Apr  6 23:42:06 2021
  InstallationDate: Installed on 2021-04-06 (0 days ago)
  InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 82LM
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=2b00a467-aa8f-4985-9e05-2d408a17ff2a ro quiet splash 
processor.max_cstate=5 rcu_nocbs=0-11 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2021-04-06 (0 days ago)
  dmi.bios.date: 02/03/2021
  dmi.bios.release: 1.16
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5CN16WW(V1.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14ALC05
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5CN16WW(V1.04):bd02/03/2021:br1.16:efr1.16:svnLENOVO:pn82LM:pvrIdeaPad514ALC05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad514ALC05:
  dmi.product.family: IdeaPad 5 14ALC05
  dmi.product.name: 82LM
  dmi.product.sku: LENOVO_MT_82LM_BU_idea_FM_IdeaPad 5 14ALC05
  dmi.product.version: IdeaPad 5 14ALC05
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1882439] Re: Power down and restart after shut down doesn't work.

apport information

** Tags added: apport-collected ulyssa

** Description changed:

  It only works with hard shutdown.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.16
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  dordom  953 F pulseaudio
+  /dev/snd/controlC0:  dordom  953 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 20.1
+ InstallationDate: Installed on 2021-01-30 (66 days ago)
+ InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
+ MachineType: LENOVO 81N6
+ Package: linux (not installed)
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
+ ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.8.0-48-generic N/A
+  linux-backports-modules-5.8.0-48-generic  N/A
+  linux-firmware1.187.10
+ Tags:  ulyssa
+ Uname: Linux 5.8.0-48-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/08/2020
+ dmi.bios.release: 1.27
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: AGCN27WW(V1.10)
+ dmi.board.asset.tag: NO Asset Tag
+ dmi.board.name: LNVNB161216
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40700 WIN
+ dmi.chassis.asset.tag: NO Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Lenovo IdeaPad C340-14API
+ dmi.ec.firmware.release: 1.27
+ dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
+ dmi.product.family: IdeaPad C340-14API
+ dmi.product.name: 81N6
+ dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
+ dmi.product.version: Lenovo IdeaPad C340-14API
+ dmi.sys.vendor: LENOVO

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1882439/+attachment/5484926/+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/1882439

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1922800] [NEW] Nvidia proprietary DKMS drivers cannot build in linux-kvm 5.8 and subsequent versions

2021-04-06 Thread Guilherme G. Piccoli

Public bug reported:

After an ADT/DKMS modification (see
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1915051) binary DKMS
packages without -dkms in the name started to get tested on ADT run.
This exposed a problem in the Nvidia proprietary DKMS modules for linux-
kvm build:

if we don't have CONFIG_X86_PAT set, the Nvidia drivers (all versions) set 
NV_ENABLE_BUILTIN_PAT_SUPPORT to 1 and attempt to build the file 
nvidia/nv-pat.c - two functions there make use of __flush_tlb() exported symbol.
But, after kernel v5.8, this symbol is not exported anymore [0][1], not even 
flush_tlb_local() is available.

For the time being, we ADT-hinted linux-kvm package, but the driver
requires modifications, in order to fix that.

[0] http://git.kernel.org/linus/2faf153bb734
[1] http://git.kernel.org/linus/bfe3d8f6313d

** Affects: linux-kvm (Ubuntu)
 Importance: Undecided
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: In Progress

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

** Affects: linux-kvm (Ubuntu Groovy)
 Importance: Undecided
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: In Progress

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

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

** Also affects: nvidia-graphics-drivers (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-kvm (Ubuntu)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

** Changed in: linux-kvm (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: linux-kvm (Ubuntu Groovy)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: linux-kvm (Ubuntu Groovy)
   Status: New => In Progress

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

Title:
  Nvidia proprietary DKMS drivers cannot build in linux-kvm 5.8 and
  subsequent versions

Status in linux-kvm package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers source package in Groovy:
  New

Bug description:
  After an ADT/DKMS modification (see
  https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1915051) binary
  DKMS packages without -dkms in the name started to get tested on ADT
  run. This exposed a problem in the Nvidia proprietary DKMS modules for
  linux-kvm build:

  if we don't have CONFIG_X86_PAT set, the Nvidia drivers (all versions) set 
NV_ENABLE_BUILTIN_PAT_SUPPORT to 1 and attempt to build the file 
nvidia/nv-pat.c - two functions there make use of __flush_tlb() exported symbol.
  But, after kernel v5.8, this symbol is not exported anymore [0][1], not even 
flush_tlb_local() is available.

  For the time being, we ADT-hinted linux-kvm package, but the driver
  requires modifications, in order to fix that.

  [0] http://git.kernel.org/linus/2faf153bb734
  [1] http://git.kernel.org/linus/bfe3d8f6313d

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dordom  953 F pulseaudio
   /dev/snd/controlC0:  dordom  953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (66 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  MachineType: LENOVO 81N6
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b6af4cf2-3243-4b15-81ef-1b166a90e68b ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  ulyssa
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2020
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AGCN27WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad C340-14API
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN27WW(V1.10):bd07/08/2020:br1.27:efr1.27:svnLENOVO:pn81N6:pvrLenovoIdeaPadC340-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadC340-14API:
  dmi.product.family: IdeaPad C340-14API
  dmi.product.name: 81N6
  dmi.product.sku: LENOVO_MT_81N6_BU_idea_FM_IdeaPad C340-14API
  dmi.product.version: Lenovo IdeaPad C340-14API
  dmi.sys.vendor: LENOVO

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

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

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

2021-04-06 Thread magellan

I don't leave the numpad always on. And while I'm typing it is always
off. But when I need it, I dont switch it off after typing a few numbers
and that's the problem. Ok I agree with you, it should be on only when
we have a lot of numbers to type or when we use the calculator.

About keys stroke, We must keep it for the natural keyboard but it
should not used with the numpad. I don't want to impact all the system
and keyboard, just suppress the repetition with the numpad if it is
possible.

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

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

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

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

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

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

[Kernel-packages] [Bug 1908677] Update Released

2021-04-06 Thread Brian Murray

The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Dell Latitude 9510 capture volume is too low

Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * The internal mic default volume is too low
     A upstream commit correct the init configuration

  [Test Case]

   * Using gnome-sound-recoder to record audio without tweak capture volume
     The volume is very low
   * Try to update the init.conf mentioned by
     
https://github.com/alsa-project/alsa-ucm-conf/commit/263bd26b1216c933db3d216197a78678d0f8610e
     $ alsactl init
     $ amixer cget name='rt715 ADC 07 Capture Volume'
     numid=14,iface=MIXER,name='rt715 ADC 07 Capture Volume'
    ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0
    : values=58,58
    | dBscale-min=-17.25dB,step=0.75dB,mute=0

   * Using gnome-sound-recorder to record again
     The volume is significantly improved

  [Where problems could occur]

   * The change only apply to the hardware with rt715 codec.

   * [racb] Is there any other hardware that isn't being tested that
  uses this codec?

   * The change adjust the volume only, but not change other control,
     the worst case is the change doesn't take effect.

  [Other Info]

   * The change has been verified on Latitude 9510.

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

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

[Kernel-packages] [Bug 1882439] Missing required logs.

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 1882439

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.

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

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

[Kernel-packages] [Bug 1873334] Missing required logs.

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 1873334

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

Title:
  Secondary HDD hard drive spin down abruptly when shutting down or
  restarting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have recently replaced the main HDD of my ASUS a53s laptop with an
  SSD. I have placed the HDD hard drive in the SATA port where the DVD
  drive was located. I have not had any problems and the speed of my
  system has increased a lot. However, I have noticed that every time I
  turn off the system, a click of the needle of the HDD hard disk
  sounds, as if it were turned off suddenly (this did not happen when it
  was placed in the main SATA port). Could you do some configuration in
  Ubuntu to avoid this? Thank you very much.

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

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

[Kernel-packages] [Bug 1907416] Missing required logs.

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 1907416

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

Title:
  skype microphone  problem after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  skype microphone problem after suspend. After suspend I need to
  restart skype, because microphone of skype not working

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

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

[Kernel-packages] [Bug 1903841] Missing required logs.

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 1903841

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

Title:
  i915 kerner driver can't initialize two connected LVDS outputs

Status in linux package in Ubuntu:
  Incomplete
Status in Debian:
  Incomplete

Bug description:
  The bug appears from Ubuntu 18.04 and persists in Ubuntu 20.04 and
  20.10.

  The hardware:
  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 11)

  The bug appears only if both LVDS-Outputs are connected to TFT panels
  at the same time.

  3) Expected (works at Ubuntu 16.04):
  The graphic card is properly initialized and the intel_backlight links appear:

  ll /sys/class/backlight/
  lrwxrwxrwx  1 root root 0 Feb 11  2016 intel_backlight -> 
../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-1/intel_backlight/
  lrwxrwxrwx  1 root root 0 Feb 11  2016 intel_backlight 
../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-2/intel_backlight/

  Both TFT panels connected via LVDS are on and are showing the desktop.

  4) What happens instead:
  The the initialisation of the graphic card by the i915 kernel driver fails:

  dmesg | grep dup
  [2.951765] sysfs: cannot create duplicate filename 
'/class/backlight/intel_backlight'
  [2.951792]  sysfs_warn_dup.cold+0x17/0x35

  The /sys/class/backlight/ directory is empty.

  Modesetting fails:
  xrandr shows only one eDP-1 output and the disconnected outputs HDMI-1 and 
VGA-1 are gone.

  The TFT-Panels are off.

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

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

[Kernel-packages] [Bug 1909002] Re: Kernel 5.4.0-58

2021-04-06 Thread Jim Zarpaty

I tried many different ways to resolve this issue manually adding and
removing modules or editing driver files as suggested in different
forums and it didn't work (I only have a basic knowledge of Linux)
anyway I'm pleased to say that it is working again from Kernel 5.4.0-67.

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

Title:
  Kernel 5.4.0-58

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installing Kernel 5.4.0-58 in Mint, I lost the wireless USB
  LOGITECH mouse and keyboard, had to go back to 5.4.0-54.

  Description:  Linux Mint 19.3 Tricia
  Release:  19.3

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

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

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

2021-04-06 Thread Badaoui Mohamed

Hi David,

To summarize, you suggest 2 features;

1/ add an option to disable  the up right corner switch,
2/ disable press and hold feature of keystrokes,

However I have the impression that you leave your numpad always on, so that s 
why when you type on your main keyboard sometimes you hit some numpad keys 
accidentally.
But even on Windows, such numpad are often off because of its particular 
location, its could not be used while you type on the main keyboard.

Considering the features above, I agree that press and hold keys stroke
is useless. I don't see usecase when we would like to type several times
a same number for example (multiple 9 at a time) BUT it is interesting
to keep it for the backspace and the enter to make multiple supression
and enters at a time.

Don't know what the community thinks about this.

Mohamed.

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

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

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

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

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

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

[Kernel-packages] [Bug 1908677] Re: Dell Latitude 9510 capture volume is too low

2021-04-06 Thread Launchpad Bug Tracker

This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu5.2

---
alsa-ucm-conf (1.2.2-1ubuntu5.2) groovy; urgency=medium

  * d/p/0001-rt715-init-setup-ADC07-to-a-proper-volume.patch
Correct rt715 init volume setting. (LP: #1908677)

 -- Kai-Chuan Hsieh   Fri, 18 Dec 2020
15:10:56 +0800

** Changed in: alsa-ucm-conf (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

Title:
  Dell Latitude 9510 capture volume is too low

Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * The internal mic default volume is too low
     A upstream commit correct the init configuration

  [Test Case]

   * Using gnome-sound-recoder to record audio without tweak capture volume
     The volume is very low
   * Try to update the init.conf mentioned by
     
https://github.com/alsa-project/alsa-ucm-conf/commit/263bd26b1216c933db3d216197a78678d0f8610e
     $ alsactl init
     $ amixer cget name='rt715 ADC 07 Capture Volume'
     numid=14,iface=MIXER,name='rt715 ADC 07 Capture Volume'
    ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0
    : values=58,58
    | dBscale-min=-17.25dB,step=0.75dB,mute=0

   * Using gnome-sound-recorder to record again
     The volume is significantly improved

  [Where problems could occur]

   * The change only apply to the hardware with rt715 codec.

   * [racb] Is there any other hardware that isn't being tested that
  uses this codec?

   * The change adjust the volume only, but not change other control,
     the worst case is the change doesn't take effect.

  [Other Info]

   * The change has been verified on Latitude 9510.

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

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

[Kernel-packages] [Bug 1882439] Re: Power down and restart after shut down doesn't work.

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

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

Title:
  Power down and restart after shut down doesn't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It only works with hard shutdown.

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

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

[Kernel-packages] [Bug 1873334] Re: Secondary HDD hard drive spin down abruptly when shutting down or restarting

Is this still an issue?
You've given us no indication as to which version or flavour of Ubuntu you are 
using.
Which version of the linux kernel are you using?
Please provide any further information that is asked from you, thank you.


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

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

Title:
  Secondary HDD hard drive spin down abruptly when shutting down or
  restarting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have recently replaced the main HDD of my ASUS a53s laptop with an
  SSD. I have placed the HDD hard drive in the SATA port where the DVD
  drive was located. I have not had any problems and the speed of my
  system has increased a lot. However, I have noticed that every time I
  turn off the system, a click of the needle of the HDD hard disk
  sounds, as if it were turned off suddenly (this did not happen when it
  was placed in the main SATA port). Could you do some configuration in
  Ubuntu to avoid this? Thank you very much.

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

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

[Kernel-packages] [Bug 1903841] Re: i915 kerner driver can't initialize two connected LVDS outputs

If you've reported the bug directly to Debian please provide details of
the Debian bug #

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

** Changed in: debian
   Status: New => Incomplete

** Tags added: bionic focal groovy

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

Title:
  i915 kerner driver can't initialize two connected LVDS outputs

Status in linux package in Ubuntu:
  Incomplete
Status in Debian:
  Incomplete

Bug description:
  The bug appears from Ubuntu 18.04 and persists in Ubuntu 20.04 and
  20.10.

  The hardware:
  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 11)

  The bug appears only if both LVDS-Outputs are connected to TFT panels
  at the same time.

  3) Expected (works at Ubuntu 16.04):
  The graphic card is properly initialized and the intel_backlight links appear:

  ll /sys/class/backlight/
  lrwxrwxrwx  1 root root 0 Feb 11  2016 intel_backlight -> 
../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-1/intel_backlight/
  lrwxrwxrwx  1 root root 0 Feb 11  2016 intel_backlight 
../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-2/intel_backlight/

  Both TFT panels connected via LVDS are on and are showing the desktop.

  4) What happens instead:
  The the initialisation of the graphic card by the i915 kernel driver fails:

  dmesg | grep dup
  [2.951765] sysfs: cannot create duplicate filename 
'/class/backlight/intel_backlight'
  [2.951792]  sysfs_warn_dup.cold+0x17/0x35

  The /sys/class/backlight/ directory is empty.

  Modesetting fails:
  xrandr shows only one eDP-1 output and the disconnected outputs HDMI-1 and 
VGA-1 are gone.

  The TFT-Panels are off.

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

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

[Kernel-packages] [Bug 1908677] Re: Dell Latitude 9510 capture volume is too low

2021-04-06 Thread Launchpad Bug Tracker

This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.6

---
alsa-ucm-conf (1.2.2-1ubuntu0.6) focal; urgency=medium

  * d/p/0001-rt715-init-setup-ADC07-to-a-proper-volume.patch
Correct rt715 init volume setting. (LP: #1908677)

 -- Kai-Chuan Hsieh   Fri, 18 Dec 2020
15:26:20 +0800

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Dell Latitude 9510 capture volume is too low

Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * The internal mic default volume is too low
     A upstream commit correct the init configuration

  [Test Case]

   * Using gnome-sound-recoder to record audio without tweak capture volume
     The volume is very low
   * Try to update the init.conf mentioned by
     
https://github.com/alsa-project/alsa-ucm-conf/commit/263bd26b1216c933db3d216197a78678d0f8610e
     $ alsactl init
     $ amixer cget name='rt715 ADC 07 Capture Volume'
     numid=14,iface=MIXER,name='rt715 ADC 07 Capture Volume'
    ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0
    : values=58,58
    | dBscale-min=-17.25dB,step=0.75dB,mute=0

   * Using gnome-sound-recorder to record again
     The volume is significantly improved

  [Where problems could occur]

   * The change only apply to the hardware with rt715 codec.

   * [racb] Is there any other hardware that isn't being tested that
  uses this codec?

   * The change adjust the volume only, but not change other control,
     the worst case is the change doesn't take effect.

  [Other Info]

   * The change has been verified on Latitude 9510.

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

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

[Kernel-packages] [Bug 1907416] Re: skype microphone problem after suspend

Is this still an issue?
Have you reported the problem directly to Skype?
You've not told us which version of Ubuntu or the Linux kernel you are using.
Does this problem affect other applications are resuming from suspend?
Moving to the "linux" package as you are indicating a problem with "suspend".
Please provide any additional information that is asked of you.


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

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

Title:
  skype microphone  problem after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  skype microphone problem after suspend. After suspend I need to
  restart skype, because microphone of skype not working

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

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

[Kernel-packages] [Bug 1917210] Re: Dell XPS 13 2in1 wakes from sleep when moved on 20.04

2021-04-06 Thread Danny van Dyk

I found an interesting line in the dmesg output:

intel-hid INTC1051:00: unknown event 0xcd

The 0xcd event indicates a switch from or to tablet mode, confirming my
diagnosis that the accelerometer wakes the laptop form suspend. Incidentally,
goolging for this very event
showed me the following patch:

https://www.spinics.net/lists/platform-driver-x86/msg25277.html

I would ask the Ubuntu Kernel team to include this as soon as possible
in the OEM kernel.

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

Title:
Dell XPS 13 2in1 wakes from sleep when moved on 20.04

Status in linux package in Ubuntu:
Confirmed

Bug description:
Dell XPS 13 9310 2in1, running Ubuntu OEM kernel (20.04) on 20.04 LTS.

Laptop suspends and wakes up when lid is closed and opened, respectively.
Laptop erroneously wakes up also in following conditions:

1. lid is closed and laptop is moved/rotated.
2. lid is open, suspended manually (via power button), and laptop is
moved/rotated.

Until I found out about case 2, I assumed that the hall sensor triggered on
slight opening
of the lid. However, case 2 shows that this is unlikely a hard ware
defect/sensitivity.
I suspect that the accelaration sensor triggers waking up from sleep.

I can confirm that the problem persist after stopping the iio-sensor-prox
service via systemctl.
I did not find which kernel module is reponsible for tracking this sensor.
Suggestions?
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dvandyk1207 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-12-26 (65 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. XPS 13 9310 2-in-1
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1048-oem
root=UUID=9104c339-1746-4791-b1ff-0d439dfd75e0 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.6.0-1048.52-oem 5.6.19
RelatedPackageVersions:
linux-restricted-modules-5.6.0-1048-oem N/A
linux-backports-modules-5.6.0-1048-oem N/A
linux-firmware 1.187.9
Tags: wayland-session focal
Uname: Linux 5.6.0-1048-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/05/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.1
dmi.board.name: 0062CR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.1:bd10/05/2020:svnDellInc.:pnXPS1393102-in-1:pvr:rvnDellInc.:rn0062CR:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9310 2-in-1
dmi.product.sku: 09FF
dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device

2021-04-06 Thread Sebastien Bacher

Uploaded to 20.10 also, there was another SRU done in novembre though,
please try to base your changes on the current version, the debdiff
didn't apply to that version since it was done on top of the release
pocket version instead

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

Title:
  [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-
  Audio.pcm.iec958_device

Status in OEM Priority Project:
  In Progress
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  In Progress
Status in alsa-lib source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Where problems will occur]
  "Cmedia Audio" is the sound card name of this usb audio dongle, and this 
string is got from usb string descriptor, that is to say the "Cmedia Audio" is 
hard-coded in the firmware of that usb dongle.
  Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't 
set string descriptor, then the audio driver sets a generic name "USB Audio 
Device" for them, if a dongle has string descriptor, it may have different 
string like "C-Media USB Headphone Set", and all dongles I met before don't 
have SPDIF interface.
  So If this SRU could introduce regression, it will happen on a Cmedia usb 
audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor 
and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF 
playback device from the gnome-sound-setting. But this regression chance is 
very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in 
the string descriptor and it is very rare a usb audio dongle has SPDIF 
interface. So far we haven't met such a cmedia usb audio dongle.

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

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

[Kernel-packages] [Bug 1921643] Missing required logs.

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 1921643

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

Title:
  Thunderbolt docking station drops USB

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My Lenovo Thunderbolt Dock Gen2 randomly drops the USB controller, resulting 
in no USB at all.
  It sometimes happens after a few seconds of being plugged in to the notebook, 
but sometimes it works for hours.
  The display connected to the dock stays active and working.

  I tried to blacklist the driver (r8152) for the usb3-ethernet
  controller, as suggested in a few forums, but it does not solve the
  issue.

  dmesg is full of the following messages:
  [ 1001.028336] xhci_hcd :08:00.0: WARN Event TRB for slot 11 ep 1 with no 
TDs queued?
  [ 1001.029304] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 1 comp_code 1
  [ 1001.029324] xhci_hcd :08:00.0: Looking for event-dma 00087785b460 
trb-start 00087785b540 trb-end 00087785b540 seg-start 00087785b000 
seg-end 00087785bff0

  I'm running ubuntu 20.10, but it also happened under 20.04. Everything is up 
to date as of writing this bugreport.
  The dock is running the latest firmware, but the issue was present with 
earlier version of the firmware too.
  I also tried both thunderbolt ports on the notebook (MSI Prestige 15), the 
issue happens on both.
  The dock works flawlessly under windows 10.

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

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

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

2021-04-06 Thread Luna Jernberg

Reinstalled my desktop today, with todays Beta and having the same issue
:(

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

Title:
  Snaps appear broken on 21.04 Beta with ZFS

Status in snapd package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

2021-04-06 Thread Christopher

> (as for Wayland issues, let's please not mix it in here, please open a
separate bug report if needed, possibly adding ubuntu-desktop to it).

@stolowski No worries. I'll open a new one for that.

@mvo Let me know when a new release is cut and I can pop it on the box
and test.

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

Title:
  Snaps appear broken on 21.04 Beta with ZFS

Status in snapd package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

The apport-collect run for this was actually perfect: the external
screen didn't wake for LUKS and didn't wake for the greeter afterwards,
so I had to get the laptop out of the stand and open the lid to be able
to finish booting. I hope the logs have captured all relevant
information.

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
Confirmed
Status in linux-meta-oem-5.6 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

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

apport information

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

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1922334/+attachment/5484889/+files/WifiSyslog.txt

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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)
  [

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340]

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340] xhci_hcd

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340] xhci_hcd

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340] xhci_hcd

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340]

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340]

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340]

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340]

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340] xhci_hcd

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340] xhci_hcd

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340] xhci_hcd

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340] xhci_hcd

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340] xhci_hcd

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

apport information

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

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

Title:
  ACPI errors and USB reset loop when hot-plugging a Titan Ridge laptop
  into a dock (9500, TB16)

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-oem-5.6 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, hot-plugging the dock causes ACPI 
errors in dmesg and some kind of reset loop with USB peripherals connected via 
the dock.

  
  details:
  USB peripherals keep reconnecting according to dmesg, but in practice they 
barely ever finish registering with the system before disappearing again. Maybe 
1 out of 40 USB keyboard presses registers while this is happening. At this 
point my choices are to either reboot with the dock connected or work without 
the dock and consequently without any peripherals on my desk. Booting with an 
open lid and the dock connected works fine until I re-plug the dock.

  Notably, it hot-plugs fine every time when using XPS 9560 or Precision
  5520 in the same setup which I have been using for ages and which had
  similar problems until around kernel 4.13.

  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.

  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 rebinding the XHCI controller after reconnecting the
  dock. I have attempted disabling USB autosuspend and ASPM via a GRUB
  kernel parameter. 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.

  System config:

  XPS 9500, i7, 32GB RAM
  BIOS 1.6.1, TB3 firmware NVM60
  Ubuntu 20.04.02 LTS, kernels 5.6-oem, 5.8-generic, 5.10-oem (same behaviour)
  TB16 dock firmware 1.0.4 (MST 3.12.02)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  gboiko 1990 F pulseaudio
   /dev/snd/controlC2:  gboiko 1990 F pulseaudio
   /dev/snd/controlC1:  gboiko 1990 F pulseaudio
   /dev/snd/controlC0:  gboiko 1990 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-03-31 (6 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. XPS 15 9500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-meta-oem-5.6
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1052-oem 
root=/dev/mapper/vgubuntu-root ro net.ifnames=0 biosdevname=0 ipv6.disable=1 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1052.56-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1052-oem N/A
   linux-backports-modules-5.6.0-1052-oem  N/A
   linux-firmware  1.187.10
  Tags:  focal
  Uname: Linux 5.6.0-1052-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0RHXRG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd12/24/2020:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0RHXRG:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9500
  dmi.product.sku: 097D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1922336/+subscriptions

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

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340] xhci_hcd

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

apport information

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.6 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:
  Confirmed
Status in linux-meta-oem-5.6 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 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340]

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