[Kernel-packages] [Bug 1912316] Re: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048)

[Kelsey Skunberg]

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

Title:
  log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud
  node grumman (failed with flag 2048)

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

Bug description:
  Issue found on node grumman, this is not a regression.

  The kernel_tainted check reports a non-zero flag 2048, this means
  "workaround for bug in platform firmware applied"

  log_check reports WARNINGs found in the dmesg:

  10.   01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 7.852005] WARNING: CPU: 
0 PID: 179 at /build/linux-0dlxvs/linux-4.4.0/drivers/dma/ioat/dca.c:342 
ioat_dca_init+0x17c/0x1a0 [ioatdma]()
  11.   01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 5.387292] WARNING: CPU: 
0 PID: 181 at /build/linux-7Nk88i/linux-4.4.0/drivers/dma/ioat/dca.c:342 
ioat_dca_init+0x17c/0x1a0 [ioatdma]()
  12.   01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 6.039705] WARNING: CPU: 
0 PID: 4 at /build/linux-7Nk88i/linux-4.4.0/drivers/dma/ioat/dca.c:342 
ioat_dca_init+0x17c/0x1a0 [ioatdma]()

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

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

[Kernel-packages] [Bug 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed

[Kelsey Skunberg]

** Tags added: 5.4 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/1829978

Title:
  cpuacct_100_100 from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
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

Bug description:
   startup='Wed May 22 06:50:45 2019'
   cpuacct 1 TINFO: timeout per run is 0h 5m 0s
   cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct
   cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes
   /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: 
/opt/ltp/testcases/bin/cpuacct.sh: Cannot fork
   tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 
cs=53

  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 06:59:27 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/1829978/+subscriptions

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

[Kernel-packages] [Bug 1908264] Re: Disable Atari partition support for cloud kernels

[Khaled El Mously]

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

** No longer affects: linux-gkeop (Ubuntu Xenial)

** No longer affects: linux-gkeop (Ubuntu Bionic)

** No longer affects: linux-gkeop (Ubuntu Groovy)

** No longer affects: linux-gkeop (Ubuntu Hirsute)

** No longer affects: linux-oracle (Ubuntu Xenial)

** No longer affects: linux-gke (Ubuntu Xenial)

** No longer affects: linux-gcp (Ubuntu Xenial)

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

Title:
  Disable Atari partition support for cloud kernels

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-4.15 package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux-gkeop package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-aws source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-4.15 source package in Xenial:
  Invalid
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  Fix Released
Status in linux-gcp source package in Bionic:
  New
Status in linux-gke source package in Bionic:
  New
Status in linux-oracle source package in Bionic:
  New
Status in linux-aws source package in Focal:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-azure-4.15 source package in Focal:
  Invalid
Status in linux-gcp source package in Focal:
  New
Status in linux-gke source package in Focal:
  New
Status in linux-gkeop source package in Focal:
  New
Status in linux-oracle source package in Focal:
  New
Status in linux-aws source package in Groovy:
  Fix Committed
Status in linux-azure source package in Groovy:
  Fix Released
Status in linux-azure-4.15 source package in Groovy:
  Invalid
Status in linux-gcp source package in Groovy:
  New
Status in linux-gke source package in Groovy:
  New
Status in linux-oracle source package in Groovy:
  New
Status in linux-aws source package in Hirsute:
  In Progress
Status in linux-azure source package in Hirsute:
  Fix Released
Status in linux-azure-4.15 source package in Hirsute:
  Invalid
Status in linux-gcp source package in Hirsute:
  New
Status in linux-gke source package in Hirsute:
  New
Status in linux-oracle source package in Hirsute:
  New

Bug description:
  [Impact]
  Atari partition tables have very broad specifications, and can spontaneously 
show up on uncleared disks with "garbage" data. There have been reports of 
misinterpreted AHDI partition tables before (see [0] and [1]), usually as an 
unintended side-effect of using non-zeroed disks. Users of this specific 
partition scheme are unlikely to be on AWS instances, so we should disable them.

  [0] 
https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/
  [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html

  [Test Case]
  Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r)

  [Fix]
  Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu

  [Regression Potential]
  There could be unexpected dependencies on Atari partitions that are impacted 
by this change. Considering Atari hardware hasn't been produced in a long time, 
and is unlikely to be used in AWS instances, the regression potential should be 
very low.

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

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

[Kernel-packages] [Bug 1879328] Re: ubuntu_kvm_unit_test failed to build on Focal PowerPC

[Kelsey Skunberg]

** Tags added: 5.4 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/1879328

Title:
  ubuntu_kvm_unit_test failed to build on Focal PowerPC

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

Bug description:
  Compilation failed with:

  ld: ld: powerpc/selftest.elfpowerpc/spapr_hcall.elf: error: PHDR
  segment not covered by LOAD segment: error: PHDR segment not covered
  by LOAD segment

  ld: powerpc/rtas.elf: error: PHDR segment not covered by LOAD segment
  ld: powerpc/emulator.elf: error: PHDR segment not covered by LOAD segment
  ld: powerpc/sprs.elf: error: PHDR segment not covered by LOAD segment
  ld: powerpc/tm.elf: error: PHDR segment not covered by LOAD segment

  
  Full build log:
  $ sudo make  -j156 standalone
  gcc  -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec 
-I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt
 -I lib -Wa,-mregnames -g -MMD -MF powerpc/.selftest.d -Wall -Wwrite-strings 
-Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers 
-Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror  
-fomit-frame-pointer-Wno-frame-address   -fno-pic  -no-pie 
-Wmissing-parameter-type -Wold-style-declaration -Woverride-init 
-mlittle-endian -c -o powerpc/selftest.aux.o 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c
 \
-DPROGNAME=\"powerpc/selftest.elf\"
  gcc  -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec 
-I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt
 -I lib -Wa,-mregnames -g -MMD -MF powerpc/.spapr_hcall.d -Wall -Wwrite-strings 
-Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers 
-Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror  
-fomit-frame-pointer-Wno-frame-address   -fno-pic  -no-pie 
-Wmissing-parameter-type -Wold-style-declaration -Woverride-init 
-mlittle-endian -c -o powerpc/spapr_hcall.aux.o 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c
 \
-DPROGNAME=\"powerpc/spapr_hcall.elf\"
  gcc  -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec 
-I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt
 -I lib -Wa,-mregnames -g -MMD -MF powerpc/.rtas.d -Wall -Wwrite-strings 
-Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers 
-Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror  
-fomit-frame-pointer-Wno-frame-address   -fno-pic  -no-pie 
-Wmissing-parameter-type -Wold-style-declaration -Woverride-init 
-mlittle-endian -c -o powerpc/rtas.aux.o 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c
 \
-DPROGNAME=\"powerpc/rtas.elf\"
  gcc  -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec 
-I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt
 -I lib -Wa,-mregnames -g -MMD -MF powerpc/.emulator.d -Wall -Wwrite-strings 
-Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers 
-Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror  
-fomit-frame-pointer-Wno-frame-address   -fno-pic  -no-pie 
-Wmissing-parameter-type -Wold-style-declaration -Woverride-init 
-mlittle-endian -c -o powerpc/emulator.aux.o 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c
 \
-DPROGNAME=\"powerpc/emulator.elf\"
  gcc  -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec 
-I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt
 -I lib -Wa,-mregnames -g -MMD -MF powerpc/.tm.d -Wall -Wwrite-strings 
-Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers 
-Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror  
-fomit-frame-pointer-Wno-frame-address   -fno-pic  -no-pie 
-Wmissing-parameter-type -Wold-style-declaration -Woverride-init 
-mlittle-endian -c -o powerpc/tm.aux.o 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c
 \
-DPROGNAME=\"powerpc/tm.elf\"
  gcc  -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec 
-I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-I 

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

[Kelsey Skunberg]

** Tags added: 5.4

-- 
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 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x

[Kelsey Skunberg]

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

Title:
  ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x

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

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz

  The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x:

  15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh
  15:45:23 DEBUG| [stdout] # PASS: policy routing
  15:45:23 DEBUG| [stdout] # PASS: route get
  15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired
  15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete
  15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy
  15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint
  15:45:29 DEBUG| [stdout] # PASS: gretap
  15:45:29 DEBUG| [stdout] # PASS: ip6gretap
  15:45:29 DEBUG| [stdout] # PASS: erspan
  15:45:29 DEBUG| [stdout] # PASS: ip6erspan
  15:45:30 DEBUG| [stdout] # PASS: bridge setup
  15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel
  15:45:31 DEBUG| [stdout] # PASS: set ifalias 
b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0
  15:45:31 DEBUG| [stdout] # PASS: vrf
  15:45:31 DEBUG| [stdout] # PASS: vxlan
  15:45:31 DEBUG| [stdout] # FAIL: can't add fou port , skipping test
  15:45:31 DEBUG| [stdout] # PASS: macsec
  15:45:32 DEBUG| [stdout] # PASS: ipsec
  15:45:33 DEBUG| [stdout] # 3,7c3,7
  15:45:33 DEBUG| [stdout] # < sa[0]spi=0x0009 proto=0x32 
salt=0x64636261 crypt=1
  15:45:33 DEBUG| [stdout] # < sa[0]key=0x31323334 35363738 39303132 
33343536
  15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x   
c0a87b03
  15:45:33 DEBUG| [stdout] # < sa[1]spi=0x0009 proto=0x32 
salt=0x64636261 crypt=1
  15:45:33 DEBUG| [stdout] # < sa[1]key=0x31323334 35363738 39303132 
33343536
  15:45:33 DEBUG| [stdout] # ---
  15:45:33 DEBUG| [stdout] # > sa[0]spi=0x0009 proto=0x32 
salt=0x61626364 crypt=1
  15:45:33 DEBUG| [stdout] # > sa[0]key=0x34333231 38373635 32313039 
36353433
  15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x   
037ba8c0
  15:45:33 DEBUG| [stdout] # > sa[1]spi=0x0009 proto=0x32 
salt=0x61626364 crypt=1
  15:45:33 DEBUG| [stdout] # > sa[1]key=0x34333231 38373635 32313039 
36353433
  15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data
  15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload
  15:45:33 DEBUG| [stdout] # PASS: bridge fdb get
  15:45:33 DEBUG| [stdout] # PASS: neigh get
  15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1

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

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

[Kernel-packages] [Bug 1913273] Re: System crash randomly

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  System crash randomly

Status in linux package in Ubuntu:
  Expired

Bug description:
  Since the linux-image-5.4.0-62 kernel, my system crashes randomly
  several times a day. I have the same behavior (crash) with the
  5.4.0-64. I have reinstalled the 5.4.0-60 which seems to work
  properly. I have few informations about my crashes. The only starting
  point I found is in my /var/log/kern.log, where the following lines
  appear (I have no certitudes this is related to my problem, but I
  didn't found anything else):

  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.549952] [ cut here 
]
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.549960] kernel BUG at 
mm/slub.c:306!
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.549987] invalid opcode:  
[#1] SMP NOPTI
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.549994] CPU: 0 PID: 5238 Comm: 
ThreadPoolForeg Tainted: G   OE 5.4.0-64-generic #72-Ubuntu
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.549996] Hardware name: Dell Inc. 
Latitude 5400/0PD9KD, BIOS 1.4.2 07/04/2019
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550013] RIP: 
0010:__slab_free+0x189/0x330
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550017] Code: 00 48 89 c7 fa 66 
0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 65 4d 3b 6c 24 20 74 11 49 0f ba 34 24 
00 57 9d 0f 1f 44 00 00 eb 9f <0f> 0b 49 3b 5c 24 28 75 e8 48 8b 44 24 28 49 89 
4c 24 28 49 89 44
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550019] RSP: 
0018:a141c3b53c20 EFLAGS: 00010246
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550022] RAX: 8f007ba1cae0 
RBX: 802a0028 RCX: 8f007ba1cae0
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550024] RDX: 8f007ba1cae0 
RSI: d41b8fee8700 RDI: 8f00ea407480
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550025] RBP: a141c3b53cb8 
R08: 0001 R09: c1511547
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550053] R10: 8f007ba1cae0 
R11: 0001 R12: d41b8fee8700
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550055] R13: 8f007ba1cae0 
R14: 8f00ea407480 R15: a141c3b53e68
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550058] FS:  
7f3d4cf50700() GS:8f00ec20() knlGS:
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550060] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550062] CR2: 083cc0009100 
CR3: 0002efebe004 CR4: 003606f0
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550064] DR0:  
DR1:  DR2: 
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550066] DR3:  
DR6: fffe0ff0 DR7: 0400
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550068] Call Trace:
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550094]  ? 
hnfsflt_ll_free.part.0+0x17/0x30 [hnfsflt]
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550097]  kfree+0x231/0x250
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550102]  
hnfsflt_ll_free.part.0+0x17/0x30 [hnfsflt]
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550105]  
hnfsflt_ll_insert+0x31/0xc0 [hnfsflt]
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550108]  
hnfsflt_logcall+0x282/0x9e0 [hnfsflt]
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550128]  
rfs_postcall_flts+0x63/0x85 [redirfs]
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550135]  rfs_setattr+0x115/0x1b0 
[redirfs]
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550144]  
notify_change+0x357/0x4e0
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550156]  do_truncate+0x78/0xd0
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550161]  
do_sys_ftruncate+0x14a/0x1c0
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550166]  
__x64_sys_ftruncate+0x1b/0x20
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550181]  do_syscall_64+0x57/0x190
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550215]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550222] RIP: 0033:0x7f3d5725ee5b
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550225] Code: 77 05 c3 0f 1f 40 
00 48 8b 15 31 10 0d 00 f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 f3 
0f 1e fa b8 4d 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 
01 10 0d 00 f7 d8
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550228] RSP: 
002b:7f3d4cf4efc8 EFLAGS: 0246 ORIG_RAX: 004d
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550230] RAX: ffda 
RBX: 7f3d4cf4eff0 RCX: 7f3d5725ee5b
  Jan 25 09:19:42 IUTNC-DOSCH-1 kernel: [  121.550232] RDX: 55ac80ccd280 
RSI: 0053980d RDI: 00d1
  

[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le

[Kelsey Skunberg]

** Tags added: 5.4 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/1867570

Title:
  reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on
  ppc64le

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

Bug description:
  This issue was extracted from the comment in bug 1812638, since that
  bug will be specific for i386

  This reuseport_bpf_numa in net will fail on PowerPC with:

  The output on B-5.3 P8 is:
   # selftests: net: reuseport_bpf_numa
   #  IPv4 UDP 
   # send node 0, receive socket 0
   # send node 1, receive socket 7
   # ./reuseport_bpf_numa: node id/receive socket mismatch
   not ok 3 selftests: net: reuseport_bpf_numa # exit=1

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

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

[Kernel-packages] [Bug 1881643] Re: pmtu.sh net selftest fail with PMTU dst likely leaked (can't delete veth device in a timely manner, PMTU dst likely leaked)

[Kelsey Skunberg]

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

Title:
  pmtu.sh net selftest fail with PMTU dst likely leaked (can't delete
  veth device in a timely manner, PMTU dst likely leaked)

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

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/ppc64el/l/linux/20200528_044656_7f57a@/log.gz

  [...]
  03:48:34 DEBUG| [stdout] # TEST: ipv6: cleanup of cached exceptions - nexthop 
objects  [FAIL]
  03:48:34 DEBUG| [stdout] #   can't delete veth device in a timely manner, 
PMTU dst likely leaked
  [...]
  03:49:17 DEBUG| [stdout] not ok 16 selftests: net: pmtu.sh # exit=1

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

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

[Kernel-packages] [Bug 1916573] Re: displayer can not wake up from sleeping.

[nullshaw]

Apr  8 11:43:17 shaozj-HPDesk kernel: [  876.939517] [drm:lspcon_wait_mode 
[i915]] *ERROR* LSPCON mode hasn't settled
Apr  8 11:43:17 shaozj-HPDesk kernel: [  877.355939] [drm:drm_lspcon_set_mode 
[drm_kms_helper]] *ERROR* LSPCON mode change timed out
Apr  8 11:43:17 shaozj-HPDesk kernel: [  877.355981] 
[drm:lspcon_change_mode.constprop.0 [i915]] *ERROR* LSPCON mode change failed
Apr  8 11:43:17 shaozj-HPDesk kernel: [  877.356011] [drm:lspcon_resume [i915]] 
*ERROR* LSPCON resume failed
Apr  8 11:43:17 shaozj-HPDesk kernel: [  877.362180] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful
Apr  8 11:43:17 shaozj-HPDesk kernel: [  877.371923] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful
Apr  8 11:43:19 shaozj-HPDesk kernel: [  878.794051] [drm:lspcon_wait_mode 
[i915]] *ERROR* LSPCON mode hasn't settled
Apr  8 11:43:19 shaozj-HPDesk kernel: [  879.195933] [drm:drm_lspcon_set_mode 
[drm_kms_helper]] *ERROR* LSPCON mode change timed out
Apr  8 11:43:19 shaozj-HPDesk kernel: [  879.195976] 
[drm:lspcon_change_mode.constprop.0 [i915]] *ERROR* LSPCON mode change failed
Apr  8 11:43:19 shaozj-HPDesk kernel: [  879.196006] [drm:lspcon_resume [i915]] 
*ERROR* LSPCON resume failed
Apr  8 11:43:19 shaozj-HPDesk kernel: [  879.202164] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful
Apr  8 11:43:19 shaozj-HPDesk kernel: [  879.221780] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful
Apr  8 11:43:20 shaozj-HPDesk kernel: [  879.672507] [drm:lspcon_wait_mode 
[i915]] *ERROR* LSPCON mode hasn't settled
Apr  8 11:43:20 shaozj-HPDesk kernel: [  880.079906] [drm:drm_lspcon_set_mode 
[drm_kms_helper]] *ERROR* LSPCON mode change timed out
Apr  8 11:43:20 shaozj-HPDesk kernel: [  880.079947] 
[drm:lspcon_change_mode.constprop.0 [i915]] *ERROR* LSPCON mode change failed
Apr  8 11:43:20 shaozj-HPDesk kernel: [  880.079977] [drm:lspcon_resume [i915]] 
*ERROR* LSPCON resume failed
Apr  8 11:43:20 shaozj-HPDesk kernel: [  880.086135] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful
Apr  8 11:43:20 shaozj-HPDesk kernel: [  880.105102] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful
Apr  8 11:43:21 shaozj-HPDesk kernel: [  881.550543] [drm:lspcon_wait_mode 
[i915]] *ERROR* LSPCON mode hasn't settled
Apr  8 11:43:22 shaozj-HPDesk kernel: [  881.959837] [drm:drm_lspcon_set_mode 
[drm_kms_helper]] *ERROR* LSPCON mode change timed out
Apr  8 11:43:22 shaozj-HPDesk kernel: [  881.959878] 
[drm:lspcon_change_mode.constprop.0 [i915]] *ERROR* LSPCON mode change failed
Apr  8 11:43:22 shaozj-HPDesk kernel: [  881.959909] [drm:lspcon_resume [i915]] 
*ERROR* LSPCON resume failed
Apr  8 11:43:22 shaozj-HPDesk kernel: [  881.966068] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful
Apr  8 11:43:22 shaozj-HPDesk kernel: [  881.988386] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful

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

Title:
  displayer can not wake up from sleeping.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  os system: ubuntu 20.04.2 LTS

  when I press the keyboard, I saw new log from ssh terminal.

  /var/log/kern.log

  Feb 23 17:31:56 shaozj-HPDesk kernel: [23628.303887] [drm:lspcon_wait_mode 
[i915]] *ERROR* LSPCON mode hasn't settled
  Feb 23 17:31:56 shaozj-HPDesk kernel: [23628.307888] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful
  Feb 23 17:32:48 shaozj-HPDesk kernel: [23679.346636] [drm:lspcon_wait_mode 
[i915]] *ERROR* LSPCON mode hasn't settled
  Feb 23 17:32:48 shaozj-HPDesk kernel: [23679.350790] i915 :00:02.0: [drm] 
*ERROR* Link Training Unsuccessful

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

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

[Kernel-packages] [Bug 1922406] Re: Intel AX210 Wi-Fi card does not work since updating to 1.196

[Alberto Abrao]

I can confirm it is working fine after the update:

- Restored original name for the file previously renamed.
- Installed linux-firmware update.
- Rebooted.
- Wi-Fi test: OK.

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

Title:
  Intel AX210 Wi-Fi card does not work since updating to 1.196

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  Running 21.04, updated daily.

  Since updating the linux-firmware package yesterday, the Wireless card
  does not work with current kernel (5.11.0-13).

  The error message is as follows:

  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

  It **does** work with 5.11.0-11 (previous version)

  Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020
  CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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

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

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

[Daniel van Vugt]

** Summary changed:

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

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

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

Status in bluez package in Ubuntu:
  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 1922406] Re: Intel AX210 Wi-Fi card does not work since updating to 1.196

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.197

---
linux-firmware (1.197) hirsute; urgency=medium

  * Intel AX210 Wi-Fi card does not work since updating to 1.196
(LP: #1922406)
- SAUCE: Revert "iwlwifi: add new FWs from core59-66 release"

 -- Seth Forshee   Wed, 07 Apr 2021 08:50:11
-0500

** Changed in: linux-firmware (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Intel AX210 Wi-Fi card does not work since updating to 1.196

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  Running 21.04, updated daily.

  Since updating the linux-firmware package yesterday, the Wireless card
  does not work with current kernel (5.11.0-13).

  The error message is as follows:

  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

  It **does** work with 5.11.0-11 (previous version)

  Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020
  CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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

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

[Kernel-packages] [Bug 1922406] Re: Intel AX210 Wi-Fi card does not work since updating to 1.196

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => In Progress

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

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

Title:
  Intel AX210 Wi-Fi card does not work since updating to 1.196

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  Running 21.04, updated daily.

  Since updating the linux-firmware package yesterday, the Wireless card
  does not work with current kernel (5.11.0-13).

  The error message is as follows:

  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

  It **does** work with 5.11.0-11 (previous version)

  Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020
  CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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

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

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

[Bug Watch Updater]

** Changed in: makedumpfile (Debian)
   Status: Unknown => Fix Released

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

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

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

Bug description:
  [Impact]

  On arm64 and kernels 5.4+ makedumpfile fails.

  Upstream patches solve this bug :

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

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

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

  [Test Case]

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

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

  [Regression Potential]

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

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

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

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

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

  [Other]

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

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

  commit da0d25ffa585c9a1adb94562c815daa393b1ee5e
  [PATCH] arm64: Add support for ARMv8.2-LPA (52-bit PA support)

To manage notifications about this bug 

[Kernel-packages] [Bug 1919154] Re: Enable CONFIG_NO_HZ_FULL on supported architectures

[Marcelo Cerri]

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

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

Title:
  Enable CONFIG_NO_HZ_FULL on supported architectures

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

Bug description:
  [Impact]

  The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid
  sending scheduling-clock interrupts to CPUs with a single runnable task,
  and such CPUs are said to be "adaptive-ticks CPUs".  This is important
  for applications with aggressive real-time response constraints because
  it allows them to improve their worst-case response times by the maximum
  duration of a scheduling-clock interrupt.  It is also important for
  computationally intensive short-iteration workloads:  If any CPU is
  delayed during a given iteration, all the other CPUs will be forced to
  wait idle while the delayed CPU finishes.  Thus, the delay is multiplied
  by one less than the number of CPUs.  In these situations, there is
  again strong motivation to avoid sending scheduling-clock interrupts.

  [Test Plan]

  In order to verify the change will not cause performance issues in
  context switch we should compare the results for:

  ./stress-ng --seq 0 --metrics-brief -t 15

  Running on a dedicated machine and with the following services
  disabled: smartd.service, iscsid.service, apport.service,
  cron.service, anacron.timer, apt-daily.timer, apt-daily-upgrade.timer,
  fstrim.timer, logrotate.timer, motd-news.timer, man-db.timer.

  The results didn't show any performance regression:

  https://kernel.ubuntu.com/~mhcerri/lp1919154/

  [Where problems could occur]

  Performance degradation might happen for workloads with intensive
  context switching.

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

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

[Guilherme G. Piccoli]

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

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

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

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

Status in linux-kvm package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Groovy:
  Fix Released
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 1919154] Re: Enable CONFIG_NO_HZ_FULL on supported architectures

[Marcelo Cerri]

** Description changed:

  [Impact]
  
  The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid
  sending scheduling-clock interrupts to CPUs with a single runnable task,
  and such CPUs are said to be "adaptive-ticks CPUs".  This is important
  for applications with aggressive real-time response constraints because
  it allows them to improve their worst-case response times by the maximum
  duration of a scheduling-clock interrupt.  It is also important for
  computationally intensive short-iteration workloads:  If any CPU is
  delayed during a given iteration, all the other CPUs will be forced to
  wait idle while the delayed CPU finishes.  Thus, the delay is multiplied
  by one less than the number of CPUs.  In these situations, there is
  again strong motivation to avoid sending scheduling-clock interrupts.
  
  [Test Plan]
  
  In order to verify the change will not cause performance issues in
  context switch we should compare the results for:
  
  ./stress-ng --seq 0 --metrics-brief -t 15
  
  Running on a dedicated machine and with the following services disabled:
  smartd.service, iscsid.service, apport.service, cron.service,
  anacron.timer, apt-daily.timer, apt-daily-upgrade.timer, fstrim.timer,
  logrotate.timer, motd-news.timer, man-db.timer.
  
+ The results didn't show any performance regression:
+ 
+ https://kernel.ubuntu.com/~mhcerri/lp1919154/
+ 
  [Where problems could occur]
  
  Performance degradation might happen for workloads with intensive
  context switching.

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

Title:
  Enable CONFIG_NO_HZ_FULL on supported architectures

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

Bug description:
  [Impact]

  The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid
  sending scheduling-clock interrupts to CPUs with a single runnable task,
  and such CPUs are said to be "adaptive-ticks CPUs".  This is important
  for applications with aggressive real-time response constraints because
  it allows them to improve their worst-case response times by the maximum
  duration of a scheduling-clock interrupt.  It is also important for
  computationally intensive short-iteration workloads:  If any CPU is
  delayed during a given iteration, all the other CPUs will be forced to
  wait idle while the delayed CPU finishes.  Thus, the delay is multiplied
  by one less than the number of CPUs.  In these situations, there is
  again strong motivation to avoid sending scheduling-clock interrupts.

  [Test Plan]

  In order to verify the change will not cause performance issues in
  context switch we should compare the results for:

  ./stress-ng --seq 0 --metrics-brief -t 15

  Running on a dedicated machine and with the following services
  disabled: smartd.service, iscsid.service, apport.service,
  cron.service, anacron.timer, apt-daily.timer, apt-daily-upgrade.timer,
  fstrim.timer, logrotate.timer, motd-news.timer, man-db.timer.

  The results didn't show any performance regression:

  https://kernel.ubuntu.com/~mhcerri/lp1919154/

  [Where problems could occur]

  Performance degradation might happen for workloads with intensive
  context switching.

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

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

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

[Luis Felipe Quiñones Nieto]

I can confirm UX433F without extra symbols working properly turning On/Off
option from the numpad button is also working without issues.

Thanks, Mohamed!

El mié, 7 abr 2021 a las 16:00, Leesa (<1810...@bugs.launchpad.net>)
escribió:

> F8 was the first thing I commented out, I vote for removal or maybe
> installation option for those who really need it?
>
> I hope someday we will find a way to turn on and off real numpad
> keyboard device.
>
> Great job, Mohamed!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>

-- 
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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[Leesa]

F8 was the first thing I commented out, I vote for removal or maybe
installation option for those who really need it?

I hope someday we will find a way to turn on and off real numpad
keyboard device.

Great job, 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 1909381] Re: ubuntu 20.04 frozen randomly

[Shay Perlstein]

I get the same issue on DELL Precision 7550 and I am sure I got it once
also on a Precision 5550

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

Title:
  ubuntu 20.04 frozen randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 20.04 (dual boot with windows 10) on Dell vostro
  7500, the whole system crashes randomly, the symptom is the whole
  screen frozen, the time on the screen is stuck, mouse cannot move,
  keyboard input is invalid. I think it is a kernel crash because sysrq
  does not work, which works in normal time, and /var/log/syslog
  contains no lines after the crash.

  I tried reinstalling the os and switching my kernel version from
  5.4.0-58-generic to 5.4.0-42-generic, but the problem persists. The
  frequency of crashing is one time per week before reinstalling and one
  time per day after reinstalling.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 described
  the same problems as me but it is about 18.10 and is closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  7165 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 27 10:57:10 2020
  InstallationDate: Installed on 2020-12-19 (7 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 7500
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=691b73da-2f14-4067-99eb-f7ade1c6ce10 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 034VHF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/25/2020:svnDellInc.:pnVostro7500:pvr:rvnDellInc.:rn034VHF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 7500
  dmi.product.sku: 09F0
  dmi.sys.vendor: Dell Inc.

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

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

[Badaoui Mohamed]

This python driver has been tested and works fine for these asus versions at 
the moment:
- X412DA (without extra symbols)
- UX433 (without extra symbols)
- UX431F (without extra symbols)
- UX333FA (without extra symbols)
- UX434FA (with % and = symbols)
- UX325EA (with % and = symbols)
- UX363EA (with % and = symbols)
- UX393 (with % and = symbols)
- M433IA (with % and = symbols)
- TM420 (with % and = symbols)

With that list, we could auto-detect the keyboard layout.

Another suggestion is too disable F8, because it is potentially conflictual
(see https://github.com/mohamed-badaoui/ux433-touchpad-numpad/issues/7)
Once long tap feature on numpad switch is implemented, F8 could be removed ? 
What do you think ?

Mohamed.


** Bug watch added: github.com/mohamed-badaoui/ux433-touchpad-numpad/issues #7
   https://github.com/mohamed-badaoui/ux433-touchpad-numpad/issues/7

-- 
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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[Badaoui Mohamed]

Hi Leeda,

Indeed, the detection of the touchpad must correspond to ASUE and not to ELAN 
(for a touchpad without additional symbols).
This has been fixed.

Regarding the numeric keypad switch, I also think that a long press
(>500 ms) could be interesting and quite easy to implement. As soon as I
have a little bit of time, I will upgrade it.

Personally, it's been almost 1 week since I tested it and it works very
well for the UX433 model.

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 1921403] Re: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

[Ioanna Alifieraki]

** Changed in: makedumpfile (Ubuntu Hirsute)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

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

Title:
  makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Hirsute:
  New
Status in makedumpfile package in Debian:
  New

Bug description:
  makedumpfile does not create the dmesg. in /var/crash.
  This happens only on 5.10+ kernel because 5.10 kernel introduces a new
  lockless ringbuffer.

  This issue has been addressed upstream with commits :
  [1] c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  [2] 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values)

  [1] 
https://github.com/makedumpfile/makedumpfile/commit/c617ec63339222f3a44d73e36677a9acc8954ccd
  [2] 
https://github.com/makedumpfile/makedumpfile/commit/44b073b7ec467aee0d7de381d455b8ace1199184

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

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

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

[Ioanna Alifieraki]

** Bug watch added: Debian Bug tracker #986594
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986594

** Also affects: makedumpfile (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986594
   Importance: Unknown
   Status: Unknown

** Changed in: makedumpfile (Ubuntu Groovy)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: makedumpfile (Ubuntu Focal)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

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

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

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Focal:
  Confirmed
Status in makedumpfile source package in Groovy:
  Confirmed
Status in makedumpfile source package in Hirsute:
  Confirmed
Status in makedumpfile package in Debian:
  Unknown

Bug description:
  [Impact]

  On arm64 and kernels 5.4+ makedumpfile fails.

  Upstream patches solve this bug :

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

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

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

  [Test Case]

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

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

  [Regression Potential]

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

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

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

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

  This patch makes adjustemnt to properly calculate vabits_actual, 
max_physmem_bits, page_offset
  Any regression 

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

[Leesa]

Numpad works on Asus UX325EA after changing touchpad detection from ELAN to 
ASUE (Maybe this should be installer option?)
Be careful when testing - each service restart creates new keyboard (not so 
important in real life use)
Numpad activation by simple touch is not so comfortable, it will be better to 
use long tap (1 sec or more) to avoid accidental touch (especially using 
old-style side scrolling)

-- 
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 1854982] Re: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

[BertN45]

I'm using Ubuntu 21.04 Beta and FreeBSD 13.0-RC5 now on my desktop and
backup server. I did check it and it works without any issue, even after
I changed the setting I used to force compatibility. I changed the
'dnodesize' back to 'auto' from 'legacy'. Legay that I used to force
compatibility.

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

Title:
  Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  After I tried to back-up my datapools from Ubuntu 19.10 to FreeBSD
  12.0 as I have done since June each week, I found out it did not work
  anymore. The regression occurred after I reinstalled Ubuntu on my new
  nvme drive. I also had to reorganize my own datapools/datasets,
  because they either moved to the nvme drive or they had to be located
  on 2 HDDs instead of 3. I had one datapool that still works, the
  datapool containing my archives and it is the datapool, that has NOT
  been reorganized. I tried for a whole long day to get the backup
  working again, but I failed. I compared the properties from datapool
  and dataset, but did not see any problem there. Only a lot of new
  features and properties not present before and not present in FreeBSD.
  I used FreeBSD, because I use for backup an old 32-bits Pentium.

  I have two complaints:
  - the Ubuntu upgrade did cost me the compatibility with FreeBSD. Open-ZFS? :(
  - the system transfers the dataset and at the end of a long transfer it 
decides to quit and the error messages are completely useless and self 
contradicting. 

  On the first try it say the dataset does exist and on the second try it says 
it does NOT exist. One of the two is completely wrong. Some consistency and 
some clearer error messages would be helpful for the user.
  See the following set of strange set error messages on two tries:

  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive zroot/hp-data/dummy
  cannot receive new filesystem stream: destination 'zroot/hp-data/dummy' exists
  must specify -F to overwrite it
  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive -F zroot/hp-data/dummy
  cannot receive new filesystem stream: dataset does not exist

  A 2nd subset of my backup is stored on the laptop and that still
  works. I also compared the properties with those of my laptop, that
  still has its original datapools of begin of the year. I aligned the
  properties of FreeBSD with those of my laptop, but it did not help.

  I attach the properties of the datapool and dataset from both FreeBSD
  and Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  3 13:35:08 2019
  InstallationDate: Installed on 2019-11-30 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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

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

[William Wilson]

Attached is a patch for Hirsute. If this is accepted I will SRU to focal
and groovy.

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => William Wilson (jawn-smith)

** Patch added: "Hirsute Patch"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+attachment/5485323/+files/lp1922792.debdiff

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

Re: [Kernel-packages] [Bug 1854982] Re: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

[BertN45]

I'm using Ubuntu 21.04 Beta and FreeBSD 13.0-RC5 now on my desktop and
backup server. I did check it and it works without any isue, even after
I changed the setting I used to force compatibility.

I already added this text to the bug report.

On Wed, 2021-04-07 at 13:24 +, Colin Ian King wrote:
> ZFS 2.0.x is now the default for Ubuntu Hirsute 21.04. If anyone
> would
> like to check that this is now compatible with BSD then that would be
> useful so we can close this issue.
> 
> ** Changed in: zfs-linux (Ubuntu)
>Importance: Undecided => Medium
>

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

Title:
  Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  After I tried to back-up my datapools from Ubuntu 19.10 to FreeBSD
  12.0 as I have done since June each week, I found out it did not work
  anymore. The regression occurred after I reinstalled Ubuntu on my new
  nvme drive. I also had to reorganize my own datapools/datasets,
  because they either moved to the nvme drive or they had to be located
  on 2 HDDs instead of 3. I had one datapool that still works, the
  datapool containing my archives and it is the datapool, that has NOT
  been reorganized. I tried for a whole long day to get the backup
  working again, but I failed. I compared the properties from datapool
  and dataset, but did not see any problem there. Only a lot of new
  features and properties not present before and not present in FreeBSD.
  I used FreeBSD, because I use for backup an old 32-bits Pentium.

  I have two complaints:
  - the Ubuntu upgrade did cost me the compatibility with FreeBSD. Open-ZFS? :(
  - the system transfers the dataset and at the end of a long transfer it 
decides to quit and the error messages are completely useless and self 
contradicting. 

  On the first try it say the dataset does exist and on the second try it says 
it does NOT exist. One of the two is completely wrong. Some consistency and 
some clearer error messages would be helpful for the user.
  See the following set of strange set error messages on two tries:

  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive zroot/hp-data/dummy
  cannot receive new filesystem stream: destination 'zroot/hp-data/dummy' exists
  must specify -F to overwrite it
  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive -F zroot/hp-data/dummy
  cannot receive new filesystem stream: dataset does not exist

  A 2nd subset of my backup is stored on the laptop and that still
  works. I also compared the properties with those of my laptop, that
  still has its original datapools of begin of the year. I aligned the
  properties of FreeBSD with those of my laptop, but it did not help.

  I attach the properties of the datapool and dataset from both FreeBSD
  and Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  3 13:35:08 2019
  InstallationDate: Installed on 2019-11-30 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Screen artifacts on recent amd gpu with kernel > 5.11.0-11

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is my first time filing a bug report, so apologies in advance for
  any mistakes and please feel free to point me in the right direction.
  I'm posting this for the kernel package because the problem is
  reliably eliminated by downgrading to 5.11.0-11 and reliably returns
  by upgrading to any greater version.

  I've been testing Hirsute as my daily driver for a couple of weeks on
  my PC with one of the recent AMD GPU's (6700XT). Everything was
  running flawlessly until the kernel upgrade from 5.11.0-11 to
  5.11.0-13. After the upgrade I had a lot of artifacts (flashing
  squares of either the background or random colors) on the screen.
  Example picture attached.

  * I suspect it's only in parts that are being hardware-accelerated. Turning 
off hardware acceleration in chrome, eliminated them in the content part of the 
browser, but the windows title bar continues to be affected.
  * The gnome panels and application menu also have random square artifacts 
appearing and disappearing. 
  * The issue exists both in X11 and Wayland sessions. 
  * I see nothing out of the ordinary in dmesg or journalctl -r.
  * Downgrading to kernel 5.11.0-11 eliminates the issue. 
  * I tried installing the latest mainline kernel (5.12-rc6), the issue 
returned, so I downgraded to 5.11.0-11 again (which fixed it). 
  * To see if other packages I installed may be causing the issue, I did a 
clean install of the latest daily iso (20210407) and can confirm the issue is 
also in there.

  I'm happy to provide more information or testing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-13-generic 5.11.0-13.14
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rob1654 F pulseaudio
   /dev/snd/controlC1:  rob1654 F pulseaudio
   /dev/snd/controlC0:  rob1654 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  7 20:48:15 2021
  InstallationDate: Installed on 2021-04-07 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210407)
  MachineType: Micro-Star International Co., Ltd. MS-7C84
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=66ca562a-996d-408a-a49b-6225bfb86cb6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-13-generic N/A
   linux-backports-modules-5.11.0-13-generic  N/A
   linux-firmware 1.196
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.61
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAG X570 TOMAHAWK WIFI (MS-7C84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.61:bd03/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570TOMAHAWKWIFI(MS-7C84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1922955] [NEW] Screen artifacts on recent amd gpu with kernel > 5.11.0-11

[Rob Vandeweyer]

Public bug reported:

This is my first time filing a bug report, so apologies in advance for
any mistakes and please feel free to point me in the right direction.
I'm posting this for the kernel package because the problem is reliably
eliminated by downgrading to 5.11.0-11 and reliably returns by upgrading
to any greater version.

I've been testing Hirsute as my daily driver for a couple of weeks on my
PC with one of the recent AMD GPU's (6700XT). Everything was running
flawlessly until the kernel upgrade from 5.11.0-11 to 5.11.0-13. After
the upgrade I had a lot of artifacts (flashing squares of either the
background or random colors) on the screen. Example picture attached.

* I suspect it's only in parts that are being hardware-accelerated. Turning off 
hardware acceleration in chrome, eliminated them in the content part of the 
browser, but the windows title bar continues to be affected.
* The gnome panels and application menu also have random square artifacts 
appearing and disappearing. 
* The issue exists both in X11 and Wayland sessions. 
* I see nothing out of the ordinary in dmesg or journalctl -r.
* Downgrading to kernel 5.11.0-11 eliminates the issue. 
* I tried installing the latest mainline kernel (5.12-rc6), the issue returned, 
so I downgraded to 5.11.0-11 again (which fixed it). 
* To see if other packages I installed may be causing the issue, I did a clean 
install of the latest daily iso (20210407) and can confirm the issue is also in 
there.

I'm happy to provide more information or testing.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-13-generic 5.11.0-13.14
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  rob1654 F pulseaudio
 /dev/snd/controlC1:  rob1654 F pulseaudio
 /dev/snd/controlC0:  rob1654 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  7 20:48:15 2021
InstallationDate: Installed on 2021-04-07 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210407)
MachineType: Micro-Star International Co., Ltd. MS-7C84
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=66ca562a-996d-408a-a49b-6225bfb86cb6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-13-generic N/A
 linux-backports-modules-5.11.0-13-generic  N/A
 linux-firmware 1.196
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/01/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.61
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MAG X570 TOMAHAWK WIFI (MS-7C84)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.61:bd03/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570TOMAHAWKWIFI(MS-7C84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C84
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug hirsute wayland-session

** Attachment added: "Picture of squares in menu"
   
https://bugs.launchpad.net/bugs/1922955/+attachment/5485293/+files/squares.jpg

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

Title:
  Screen artifacts on recent amd gpu with kernel > 5.11.0-11

Status in linux package in Ubuntu:
  New

Bug description:
  This is my first time filing a bug report, so apologies in advance for
  any mistakes and please feel free to point me in the right direction.
  I'm posting this for the kernel package because the problem is
  reliably eliminated by downgrading to 5.11.0-11 and reliably returns
  by upgrading to any greater version.

  I've been testing Hirsute as my daily driver for a couple of weeks on
  my PC with one of the recent AMD GPU's (6700XT). Everything was
  running flawlessly until the kernel upgrade from 5.11.0-11 to
  5.11.0-13. After the upgrade I had a lot of artifacts (flashing
  squares of either the background or random colors) on the screen.
  Example picture attached.

  * I suspect it's only in parts that are being hardware-accelerated. Turning 
off hardware acceleration in chrome, eliminated them in the content part of the 
browser, but the wind

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  hfs+ filesystems fail reading / writing large files

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed a problem reading hfs+ partitions on a USB flash drive after
  I installed Ubuntu 20.04 on two laptop machines. I have a Mini Mac
  that I share files via an USB flash drive formatted with hfs+ from the
  laptops with Ubuntu installed. I had no issues with Ubuntu Mate 18.10.

  I noticed that very large files, typicality larger than 100 MB, would
  have read errors or sometimes have a zero file size. One particular
  file about 500MB fails nearly every time. Other files, down to about
  100MB fail sometimes.

  I bought a new USB flash drive, but have the same failures on that.
  I have an identical flash drive formatted with ext4 which has no issues. I'm 
currently booting to Ubuntu Mate 18.10 to write the hfs+ USB flash drive.

  
  1007 ceres ~ cat /proc/version_signature
  Ubuntu 5.4.0-42.46-generic 5.4.44

  1000 ceres ~ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  1005 admin@ceres ~ sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error
  pcilib: sysfs_read_vpd: read failed: Input/output error
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uschcld1581 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-17 (91 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0408:a030 Quanta Computer, Inc. HD WebCam
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 046d:c06c Logitech, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-576
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=75021464-0e3f-4ad2-a466-cf655a6c4dd7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip fax floppy plugdev tape video www-data
  _MarkForUpload: True
  dmi.bios.date: 09/06/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.47
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: KBL
  dmi.board.version: V1.47
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:svnAcer:pnAspireE5-576:pvrV1.47:rvnKBL:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire E 15
  dmi.product.name: Aspire E5-576
  dmi.product.sku: 
  dmi.product.version: V1.47
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1891768] Re: hfs+ filesystems fail reading / writing large files

[Richard J Uschold]

OOPS! I discovered that this is NOT REALLY FIXED!
I changed it from "Fixed Released" to "New" I'm sure this is not appropriate, 
but no other available options made any sense whatsoever.

I will resubmit this in a few days. I have more information to supply.


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

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

Title:
  hfs+ filesystems fail reading / writing large files

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed a problem reading hfs+ partitions on a USB flash drive after
  I installed Ubuntu 20.04 on two laptop machines. I have a Mini Mac
  that I share files via an USB flash drive formatted with hfs+ from the
  laptops with Ubuntu installed. I had no issues with Ubuntu Mate 18.10.

  I noticed that very large files, typicality larger than 100 MB, would
  have read errors or sometimes have a zero file size. One particular
  file about 500MB fails nearly every time. Other files, down to about
  100MB fail sometimes.

  I bought a new USB flash drive, but have the same failures on that.
  I have an identical flash drive formatted with ext4 which has no issues. I'm 
currently booting to Ubuntu Mate 18.10 to write the hfs+ USB flash drive.

  
  1007 ceres ~ cat /proc/version_signature
  Ubuntu 5.4.0-42.46-generic 5.4.44

  1000 ceres ~ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  1005 admin@ceres ~ sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error
  pcilib: sysfs_read_vpd: read failed: Input/output error
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uschcld1581 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-17 (91 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0408:a030 Quanta Computer, Inc. HD WebCam
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 046d:c06c Logitech, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-576
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=75021464-0e3f-4ad2-a466-cf655a6c4dd7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip fax floppy plugdev tape video www-data
  _MarkForUpload: True
  dmi.bios.date: 09/06/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.47
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: KBL
  dmi.board.version: V1.47
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:svnAcer:pnAspireE5-576:pvrV1.47:rvnKBL:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire E 15
  dmi.product.name: Aspire E5-576
  dmi.product.sku: 
  dmi.product.version: V1.47
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Re: Thunderbolt docking station drops USB

[Viktor]

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

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

Title:
  Thunderbolt docking station drops USB

Status in linux package in Ubuntu:
  Confirmed

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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] acpidump.txt

[Viktor]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485290/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] WifiSyslog.txt

[Viktor]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485289/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] RfKill.txt

[Viktor]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1921643/+attachment/5485287/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

[Viktor]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1921643/+attachment/5485288/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] PulseList.txt

[Viktor]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485286/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] ProcModules.txt

[Viktor]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485285/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

[Viktor]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485284/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] ProcEnviron.txt

[Viktor]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485283/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] ProcCpuinfoMinimal.txt

[Viktor]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485282/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] ProcCpuinfo.txt

[Viktor]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485281/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] PciMultimedia.txt

[Viktor]

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485280/+files/PciMultimedia.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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] PaInfo.txt

[Viktor]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1921643/+attachment/5485279/+files/PaInfo.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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

[Viktor]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485278/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] Lsusb-t.txt

[Viktor]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485277/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

[Viktor]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1921643/+attachment/5485276/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] Lspci-vt.txt

[Viktor]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485275/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] Lspci.txt

[Viktor]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1921643/+attachment/5485274/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] IwConfig.txt

[Viktor]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485273/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] CurrentDmesg.txt

[Viktor]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485272/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] Card0.Codecs.codec.0.txt

[Viktor]

apport information

** Attachment added: "Card0.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485270/+files/Card0.Codecs.codec.0.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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] Card0.Codecs.codec.2.txt

[Viktor]

apport information

** Attachment added: "Card0.Codecs.codec.2.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485271/+files/Card0.Codecs.codec.2.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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1921643] Re: Thunderbolt docking station drops USB

[Viktor]

apport information

** Tags added: apport-collected

** Description changed:

  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.
+ --- 
+ ProblemType: Bug
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.20.11-0ubuntu50.5
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  viktor 1021 F pulseaudio
+  /dev/snd/controlC0:  viktor 1021 F pulseaudio
+ Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
+ Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
+ Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
+ Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2020-06-05 (306 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
+ Tags:  groovy
+ Uname: Linux 5.8.0-48-generic x86_64
+ UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/18/2019
+ dmi.bios.release: 1.8
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: E16S3IMS.108
+ dmi.board.asset.tag: Default string
+ dmi.board.name: MS-16S3
+ dmi.board.vendor: Micro-Star International Co., Ltd.
+ dmi.board.version: REV:1.0
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Micro-Star International Co., Ltd.
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
+ dmi.product.family: Prestige
+ dmi.product.name: Prestige 15 A10SC
+ dmi.product.sku: 16S3.1
+ dmi.product.version: REV:1.0
+ dmi.sys.vendor: Micro-Star International Co., Ltd.

** Attachment added: "AlsaDevices.txt"
   
https://bugs.launchpad.net/bugs/1921643/+attachment/5485268/+files/AlsaDevices.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/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 

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

[Viktor]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1921643/+attachment/5485269/+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/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.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-48-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  viktor 1021 F pulseaudio
   /dev/snd/controlC0:  viktor 1021 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-06-05 (306 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54-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.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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 1922594] Re: zfs-linux/0.6.5.6-0ubuntu29 ADT test failure with linux-snapdragon/4.4.0-1154.164

[Kelsey Skunberg]

Ah, that makes sense. Thank you for the explanation Colin. I'll get this
hinted for ADT

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

Title:
  zfs-linux/0.6.5.6-0ubuntu29 ADT test failure with linux-
  snapdragon/4.4.0-1154.164

Status in linux-snapdragon package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  Invalid

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

  Testing failed on:
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/z/zfs-linux/20210405_161503_e43f5@/log.gz



  
  First Installation: checking all kernels...
  Building only for 4.4.0-1154-snapdragon
  Building initial module for 4.4.0-1154-snapdragon
  Error! Bad return status for module build on kernel: 4.4.0-1154-snapdragon 
(aarch64)
  Consult /var/lib/dkms/zfs/0.6.5.6/build/make.log for more information.
  (Reading database ... 89329 files and directories currently installed.)
  Removing autopkgtest-satdep (0) ...
  autopkgtest [16:14:09]: test kernel-smoke-test: [---
  modprobe: FATAL: Module zfs not found in directory 
/lib/modules/4.4.0-1154-snapdragon
  kernel smoke test, create and destroy pool, 2x2 mirror: The ZFS modules are 
not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  FAILED: zpool create failed, exit code=1
  kernel smoke test, create and destroy pool, 4x1 mirror: The ZFS modules are 
not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  FAILED: zpool create failed, exit code=1
  kernel smoke test, create and destroy pool, nested raidz3: FAILED: zpool 
create failed, exit code=1
  The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  kernel smoke test, create and destroy pool, raidz1: The ZFS modules are not 
loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  FAILED: zpool create failed, exit code=1
  kernel smoke test, create and destroy pool, raidz2: FAILED: zpool create 
failed, exit code=1
  The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  kernel smoke test, create and destroy pool, raidz3: FAILED: zpool create 
failed, exit code=1
  The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  kernel smoke test, create and destroy pool, striped: The ZFS modules are not 
loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  FAILED: zpool create failed, exit code=1
  kernel smoke test, create and destroy ZFS Intent Log: The ZFS modules are not 
loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  FAILED: zpool create failed, exit code=1
  kernel smoke test, create and destroy ZFS filesystems: The ZFS modules are 
not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  FAILED: zpool create failed, exit code=1
  kernel smoke test, ZFS snapshot: FAILED: zpool create failed, exit code=1
  The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  kernel smoke test, ZFS clone: The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  FAILED: zpool create failed, exit code=1
  kernel smoke test, ZFS send and receive: FAILED: zpool create failed, exit 
code=1
  The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  kernel smoke test, corrupt data and clean with a scrub: The ZFS modules are 
not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  FAILED: zpool create failed, exit code=1
  autopkgtest [16:14:46]: test kernel-smoke-test: ---]
  autopkgtest [16:14:46]: test kernel-smoke-test:  - - - - - - - - - - results 
- - - - - - - - - -
  kernel-smoke-testFAIL non-zero exit status 1
  autopkgtest [16:14:46]: test kernel-smoke-test:  - - - - - - - - - - stderr - 
- - - - - - - - -
  modprobe: FATAL: Module zfs not found in directory 
/lib/modules/4.4.0-1154-snapdragon
  The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them.
  The ZFS modules are not loaded.
  Try running 

[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10

[Werner Sembach]

Oh I'm sorry I missed that.

I only checked the git for focal hwe-kernel because I thought: hwe-
kernel = kernel of the next release.

I was apperently misstaken on that ^^.

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

Title:
  SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Groovy:
  In Progress

Bug description:
  The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin
  setup and enable microphones to work correctly when using via the
  audio jacks.

  Patches that are fixing these problems have already been accepted to
  current Linux stable releases:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb

  Commit-hash:

  48698c973e6b4dde94d87cd1ded56d9436e9c97d

  73e7161eab5dee98114987239ec9c87fe8034ddb

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

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

[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend

[Christopher Barrington-Leigh]

Can't tell if it's the same problem, but a recent (<1 month) update on a
Lenovo T450s running 20.10 has led me to these symptoms: closing the lid
or calling suspend leaves the machine dark and unusuable until I hold
down the power button for 10 seconds to reboot.

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

Title:
  Ubuntu does not resume (wake up) from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever Ubuntu gets into suspend state, I cannot wake it up. 
  -Keystrokes start the fans but screen does not turn on and Ubuntu still seems 
to be suspended because in my teamviewer account the computer is still offline.
  -Power button clicks do not help
  -I always have to turn off computer by holding power button and then turn it 
on again.

  The only kernel that works is the following: "linux-image-5.0.0-1070
  -oem-osp1". But with this old kernel I run into different problems.

  I have the latest BIOS version from Dell (released 2020-11-27) and the
  latest updates in Ubuntu 20.04.

  I will post logs during suspend and important logs (found in Logs gui
  tool)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 13:59:14 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18
  InstallationDate: Installed on 2019-12-04 (383 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3593
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep 
tsc=reliable quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 04N9HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3593
  dmi.product.sku: 0979
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1922583] Re: xfce4-sensors-plugin: FTBFS: NVCtrlLib.h:42:1: error: unknown type name ‘Bool’; did you mean ‘bool’?

[Logan Rosen]

Thanks, Thomas!

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

Title:
  xfce4-sensors-plugin: FTBFS: NVCtrlLib.h:42:1: error: unknown type
  name ‘Bool’; did you mean ‘bool’?

Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in xfce4-sensors-plugin package in Ubuntu:
  Invalid
Status in nvidia-settings package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/978192:

  Source: xfce4-sensors-plugin
  Version: 1.3.0-3
  Severity: serious
  Justification: FTBFS on amd64
  Tags: bullseye sid ftbfs
  Usertags: ftbfs-20201226 ftbfs-bullseye

  Hi,

  During a rebuild of all packages in sid, your package failed to build
  on amd64.

  Relevant part (hopefully):
  > /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
-DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" -pthread 
-I/usr/include/xfce4/libxfce4ui-2 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/xfce4 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/xfce4/libxfce4panel-2.0 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/xfce4 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include 
-I/usr/include/NVCtrl -pthread -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o libxfce4sensors_la-nvidia.lo `test -f 'nvidia.c' 
|| echo './'`nvidia.c
  > libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" 
-pthread -I/usr/include/xfce4/libxfce4ui-2 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/xfce4 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/xfce4/libxfce4panel-2.0 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/xfce4 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include 
-I/usr/include/NVCtrl -pthread -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c nvidia.c  -fPIC -DPIC -o 
.libs/libxfce4sensors_la-nvidia.o
  > In file included from nvidia.c:39:
  > /usr/include/NVCtrl/NVCtrlLib.h:42:1: error: unknown type name ‘Bool’; did 
you mean ‘bool’?
  >42 | Bool XNVCTRLQueryExtension (
  >   | 

[Kernel-packages] [Bug 1922242] Re: openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

I can confirm that openafs-modules-dkms/1.6.15-1ubuntu1.1 can be built
and installed on both older and newer xenial/linux kernels:

$ dkms status
openafs, 1.6.15, 4.4.0-206-generic, x86_64: installed
openafs, 1.6.15, 4.4.0-208-generic, x86_64: installed


autopkgtests were also successful:

* xenial/linux 4.4.0-208.240
  - amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210407_161651_8b22b@/log.gz
  - armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210407_163444_963c5@/log.gz
  - i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/o/openafs/20210407_161429_59fe1@/log.gz
  - s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210407_161222_963c5@/log.gz

* xenial/linux 4.4.0-206.238:
  - amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210407_142619_8fbc1@/log.gz
  - armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210407_142941_8fbc1@/log.gz
  - i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/o/openafs/20210407_142002_8fbc1@/log.gz
  - s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210407_142101_8fbc1@/log.gz

Note: arm64 and ppc64el has never passed.

Thanks,
Kleber

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

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

Title:
  openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in openafs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in openafs source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  autopkgtest caught a build failure with openafs-modules-dkms with the 
xenial/linux kernel currently in -proposed (4.4.0-207.239).

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz

  Build error:

    CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
   code = inode_change_ok(inode, );
  ^
  cc1: some warnings being treated as errors

  This was caused by commit "fs: Give dentry to inode_change_ok()
  instead of inode" applied to xenial/linux as part of the fixes for
  CVE-2015-1350, which renamed inode_change_ok() to setattr_prepare().

  [Fix]
  The proposed fix is to cherry-pick commit 
8aeb711eeaa5ddac5a74c354091e2d4f7ac0cd63 "Linux 4.9: inode_change_ok() becomes 
setattr_prepare()" from openafs repository (git://git.openafs.org/openafs.git).

  [Test]
  Install openafs-modules-dkms on a xenial system running an older kernel 
without the interface change (<4.4.0-207) and with a newer kernel with the 
interface change (>=4.4.0-207). The openafs module should be built and loaded 
with all kernels.

  [Where problems could occur]
  The fix is based on the detection made during build time of the function 
available on the kernel headers. If the detection doesn't work correctly the 
build would fail.

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

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

[Kernel-packages] [Bug 1922779] Re: vc4 and v3d module not loaded

[Juerg Haefliger]

The problem is due to LP: #1918110. A fix for that was released today so
you should update and rerun flash-kernel (if it doesn't run
automatically).

I don't understand your comment #4.

** Changed in: linux-raspi (Ubuntu Groovy)
   Status: Confirmed => Fix Released

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

Title:
  vc4 and v3d module not loaded

Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi source package in Groovy:
  Fix Released

Bug description:
  I am testing ubuntu 21.04 beta on raspberry pi 4
  and after installation and also after restart
  vc4 v3d kernel module isn't loaded
  So 3d acceleration don't work

  uname -a
  Linux misko-desktop 5.11.0-1004-raspi #4-Ubuntu SMP PREEMPT Mon Mar 22 
15:51:28 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

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

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

[Kernel-packages] [Bug 1922583] Re: xfce4-sensors-plugin: FTBFS: NVCtrlLib.h:42:1: error: unknown type name ‘Bool’; did you mean ‘bool’?

[Thomas Ward]

The issue was never really in xfce4-sensors-plugin, it was in nvidia-
settings.  Since the FTBFS is fixed with the newer nvidia-settings, I'm
going to mark this as 'invalid' for xfce4-sensors-plugin as the FTBFS
wasn't part of the package itself but a supporting package that was
required.

** Changed in: xfce4-sensors-plugin (Ubuntu)
   Status: New => Invalid

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

Title:
  xfce4-sensors-plugin: FTBFS: NVCtrlLib.h:42:1: error: unknown type
  name ‘Bool’; did you mean ‘bool’?

Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in xfce4-sensors-plugin package in Ubuntu:
  Invalid
Status in nvidia-settings package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/978192:

  Source: xfce4-sensors-plugin
  Version: 1.3.0-3
  Severity: serious
  Justification: FTBFS on amd64
  Tags: bullseye sid ftbfs
  Usertags: ftbfs-20201226 ftbfs-bullseye

  Hi,

  During a rebuild of all packages in sid, your package failed to build
  on amd64.

  Relevant part (hopefully):
  > /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
-DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" -pthread 
-I/usr/include/xfce4/libxfce4ui-2 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/xfce4 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/xfce4/libxfce4panel-2.0 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/xfce4 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include 
-I/usr/include/NVCtrl -pthread -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o libxfce4sensors_la-nvidia.lo `test -f 'nvidia.c' 
|| echo './'`nvidia.c
  > libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" 
-pthread -I/usr/include/xfce4/libxfce4ui-2 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/xfce4 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/xfce4/libxfce4panel-2.0 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/xfce4 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include 
-I/usr/include/NVCtrl -pthread -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/glib-2.0 

[Kernel-packages] [Bug 1868243] Re: ld_abs+vlan_push/pop from test_bpf in ubuntu_bpf_jit will fail on X s390x

[Kleber Sacilotto de Souza]

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

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

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

Title:
  ld_abs+vlan_push/pop from test_bpf in ubuntu_bpf_jit will fail on X
  s390x

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

Bug description:
  Issue separated from bug 1768452
  The ubuntu_bpf_jit will report the following failure on Xenial s390x:
    * test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524

  This test has been moved to the test_verifier test in bpf of kselftests:
  
https://github.com/torvalds/linux/commit/93731ef086cee90af594e62874bb98ae6d6eee91

  "Remove all eBPF tests involving LD_ABS/LD_IND from test_bpf.ko. Reason
  is that the eBPF tests from test_bpf module do not go via BPF verifier
  and therefore any instruction rewrites from verifier cannot take place.

  Therefore, move them into test_verifier which runs out of user space,
  so that verfier can rewrite LD_ABS/LD_IND internally in upcoming patches.
  It will have the same effect since runtime tests are also performed from
  there. This also allows to finally unexport bpf_skb_vlan_{push,pop}_proto
  and keep it internal to core kernel."

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

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

[Kernel-packages] [Bug 1921137] Re: mount.ocfs2 causes kernel BUG at lib/string.c:1149!

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~rbalint/britney/+git/hints-ubuntu/+merge/400720

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

Title:
  mount.ocfs2 causes kernel BUG at lib/string.c:1149!

Status in corosync package in Ubuntu:
  New
Status in libaio package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in ocfs2-tools package in Ubuntu:
  New

Bug description:
  the ocfs2-tools autopkgtests for hirsute recently started failing, and
  a local test run shows this kernel bug occurring during the test:

  [  100.791586] o2dlm: Leaving domain 1D5A19C6EC8F430AB4E29230BC54D70E
  [  108.864491] detected buffer overflow in strlen
  [  108.869193] [ cut here ]
  [  108.869196] kernel BUG at lib/string.c:1149!
  [  108.869962] invalid opcode:  [#1] SMP PTI
  [  108.870715] CPU: 15 PID: 1725 Comm: mount.ocfs2 Not tainted 
5.11.0-11-generic #12-Ubuntu
  [  108.872156] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1.1 04/01/2014
  [  108.873701] RIP: 0010:fortify_panic+0x13/0x15
  [  108.874452] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 
41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 
c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8
  [  108.879043] RSP: 0018:a9cf811afc90 EFLAGS: 00010246
  [  108.880396] RAX: 0022 RBX: 926a4cd06000 RCX: 

  [  108.882165] RDX:  RSI: 926b77bd8ac0 RDI: 
926b77bd8ac0
  [  108.883474] RBP: a9cf811afc90 R08:  R09: 
a9cf811afa88
  [  108.884758] R10: a9cf811afa80 R11: 92f53508 R12: 
0004
  [  108.885961] R13: 926a49917800 R14: 926a54bdc800 R15: 
926a4cd06291
  [  108.887163] FS:  7f8440b60600() GS:926b77bc() 
knlGS:
  [  108.888626] CS:  0010 DS:  ES:  CR0: 80050033
  [  108.889607] CR2: 55eec2b97dc8 CR3: 000106c64000 CR4: 
06e0
  [  108.890823] Call Trace:
  [  108.891279]  ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2]
  [  108.892603]  ? ocfs2_sb_probe+0x133/0x3a0 [ocfs2]
  [  108.893484]  ? pointer+0x185/0x4d0
  [  108.894079]  ocfs2_fill_super+0x15d/0x7a0 [ocfs2]
  [  108.894965]  mount_bdev+0x18d/0x1c0
  [  108.895570]  ? ocfs2_remount+0x450/0x450 [ocfs2]
  [  108.896518]  ocfs2_mount+0x15/0x20 [ocfs2]
  [  108.897293]  legacy_get_tree+0x2b/0x50
  [  108.897939]  vfs_get_tree+0x2a/0xc0
  [  108.898542]  do_new_mount+0x14b/0x1a0
  [  108.899175]  path_mount+0x1d4/0x4e0
  [  108.899789]  __x64_sys_mount+0x108/0x140
  [  108.900465]  do_syscall_64+0x38/0x90
  [  108.901129]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  108.902376] RIP: 0033:0x7f8441109bce
  [  108.903169] Code: 48 8b 0d 9d 72 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 
0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 6a 72 0c 00 f7 d8 64 89 01 48
  [  108.906322] RSP: 002b:7fff92a4e2f8 EFLAGS: 0246 ORIG_RAX: 
00a5
  [  108.907610] RAX: ffda RBX:  RCX: 
7f8441109bce
  [  108.909000] RDX: 55eec0e140ae RSI: 55eec2b899e0 RDI: 
55eec2b8f060
  [  108.910727] RBP: 7fff92a4e4a0 R08: 55eec2b8f000 R09: 
7fff92a4bd00
  [  108.912443] R10:  R11: 0246 R12: 
7fff92a4e390
  [  108.914190] R13: 7fff92a4e310 R14: 55eec2b8ac00 R15: 

  [  108.916009] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs 
ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue 9p fscache 
nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev 
bochs_drm drm_vram_helper drm_ttm_helper ttm kvm_intel drm_kms_helper 
parport_pc 9pnet_virtio cec input_leds joydev 9pnet parport rc_core fb_sys_fops 
serio_raw kvm syscopyarea sysfillrect sysimgblt mac_hid qemu_fw_cfg 
sch_fq_codel msr drm virtio_rng ip_tables x_tables autofs4 btrfs 
blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover 
virtio_blk i2c_piix4 pata_acpi floppy
  [  108.925313] ---[ end trace 72e4f69b08b1a89a ]---
  [  108.927136] RIP: 0010:fortify_panic+0x13/0x15
  [  108.928706] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 
41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 
c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8
  [  108.932308] RSP: 0018:a9cf811afc90 EFLAGS: 00010246
  [  108.933231] RAX: 0022 RBX: 926a4cd06000 RCX: 

  [  108.934468] RDX:  RSI: 926b77bd8ac0 RDI: 
926b77bd8ac0
  [  108.935659] RBP: a9cf811afc90 R08:  R09: 
a9cf811afa88
  [  108.936933] R10: a9cf811afa80 R11: 92f53508 R12: 
0004
  [  108.938141] R13: 

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

[Tim Gardner]

** Description changed:

+ [SRU Justification]
+ 
  We've discovered an issue on Ubuntu 20.04 when used with Kubernetes CNIs
  that perform offloading using Geneve that causes the kernel to panic on
  Azure instances with accelerated networking with the following errors:
  
  [ 307.561223] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x200, ci 
0x3d4, sqn 0x2c5, opcode 0xd, syndrome 0x2, vendor syndrome 0x68
  [ 307.573864] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2c5
  [ 307.764902] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x200, ci 
0x3d7, sqn 0x2c5, opcode 0xd, syndrome 0x2, vendor syndrome 0x68
  [ 307.777332] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2c5
  [ 322.814393] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x218, ci 
0x1a7, sqn 0x2bd, opcode 0xd, syndrome 0x2, vendor syndrome 0x68
  [ 322.826685] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2bd
  
  NVIDIA fixed this issue in
  
https://github.com/torvalds/linux/commit/5ccc0ecda9e8a67add654d93d7e0ac4346c0fa22
  , so we're looking to have this backported to at least the linux-azure
  package.
+ 
+ [Test Plan]
+ Spin up a Kubernetes CNI that uses Geneve offloading
+ 
+ [Where problems could occur]
+ Its possible some traffic won't get geneve acceleration. This patch has been 
backported to v5.10.y and v5.11.y

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

Title:
  Backport mlx5e fix for tunnel offload

Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-azure source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux-azure source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Incomplete
Status in linux-azure source package in Groovy:
  Confirmed
Status in linux source package in Hirsute:
  Incomplete
Status in linux-azure source package in Hirsute:
  Confirmed

Bug description:
  [SRU Justification]

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1907854] Re: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status

[Colin Ian King]

Ah, so you had /dev/sdg1 3906982908 2350825580
1556157328  61% /mnt/Media02

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

Title:
  package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade:
  installed zfsutils-linux package post-installation script subprocess
  returned error exit status 1

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  After update zfsutils-linux, the update process tries to mount zfs
  file in /mnt but since in /mnt there are another disk mount fails
  with:

  Setting up zfsutils-linux (0.8.3-1ubuntu12.5) ...
  zfs-import-scan.service is a disabled or a static unit, not starting it.
  zfs-import-scan.service is a disabled or a static unit, not starting it.
  Job for zfs-mount.service failed because the control process exited with 
error code.
  See "systemctl status zfs-mount.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript zfs-mount, action "start" failed.

  ● zfs-mount.service - Mount ZFS filesystems
   Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-12-11 21:05:24 CET; 
8ms ago
 Docs: man:zfs(8)
  Process: 177294 ExecStart=/sbin/zfs mount -a (code=exited, 
status=1/FAILURE)
 Main PID: 177294 (code=exited, status=1/FAILURE)

  dic 11 21:05:24 serv systemd[1]: Starting Mount ZFS filesystems...
  dic 11 21:05:24 serv zfs[177294]: cannot mount '/mnt': directory is not empty
  dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
  dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.
  dic 11 21:05:24 serv systemd[1]: Failed to start Mount ZFS filesystems.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12.5
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.13
  AptOrdering:
   python3-aptdaemon.gtk3widgets:amd64: Install
   aptdaemon:amd64: Install
   python3-aptdaemon:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Dec 11 20:56:40 2020
  ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-03-24 (261 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-19 (206 days ago)

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

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

[Kernel-packages] [Bug 1919252] Re: zfs-dkms on Focal still allows building on Linux kernel version 5.10+

[Colin Ian King]

** Summary changed:

- zfs-dkms on Focal still allow building on Linux kernel version 5.10+
+ zfs-dkms on Focal still allows building on Linux kernel version 5.10+

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

Title:
  zfs-dkms on Focal still allows building on Linux kernel version 5.10+

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  == SRU update, zfs-dkms, Focal ==

  [Impact]

  Due to a mistake in the BUILD_EXCLUSIVE_KERNEL regex in dkms.conf,
  dkms will still consider zfs-dkms to be buildable on kernel version
  5.10+. This can happen if one installs a mainline kernel from the
  mainline PPA for one reason or another.

  Fixing this will stop users from installing incompatible newer
  versions of the kernel and hence stop dkms build failures on known
  incompatible kernel versions.  The fix is also trivial.

  [The Fix]

  Correctly escape . in regex so that the final sed'd string gets
  modified to produce the correct regex pattern, as follows:

  sed -ie '/^PACKAGE_VERSION/a 
BUILD_EXCLUSIVE_KERNEL="^(4\\.[0-9]+|5\\.[01234])\\."' \
  '$(CURDIR)/scripts/zfs-dkms.dkms'

  
  [Test Plan]

  Without the fix, install kernels > than versions 5.4. ZFS dkms will
  attempt to be built against these and fail with broken builds.
  Installing earlier kernels such as 4.20, 5.0, 5.4 should succeed.

  With the fix, installing kernels > 5.4 will skip the ZFS dkms build
  phase and report a meaningful error:

  Error!  The /var/lib/dkms/zfs/0.8.3/5.5.19-050519-generic/x86_64/dkms.conf 
for module zfs includes a BUILD_EXCLUSIVE directive which
  does not match this kernel/arch.  This indicates that it should not be built

  Test kernels for the test from https://kernel.ubuntu.com/~kernel-
  ppa/mainline/?C=N;O=D can be used to test this out.

  [Where problems could occur]

  The change is to a regex pattern match. If this is incorrect then
  kernels such a 5.4 will not be allowed to build the dkms zfs driver.
  This will clearly show up as a ZFS dkms build denied failure with an
  error such as:

  Error!  The /var/lib/dkms/zfs/0.8.3/5.5.19-050519-generic/x86_64/dkms.conf 
for module zfs includes a BUILD_EXCLUSIVE directive which
  does not match this kernel/arch.  This indicates that it should not be built

  This fix is relatively low-risk, it fixes am issue with an earlier fix
  to the regex which wasn't quite working for kernels > 5.4 and yet
  didn't cause any major issues blocking legitimate users from using
  known working 5.4 kernels with zfs dkms.

  ---

  Due to a mistake in the BUILD_EXCLUSIVE_KERNEL regex in dkms.conf,
  dkms will still consider zfs-dkms to be buildable on kernel version
  5.10+. This can happen if one installs a mainline kernel from the
  mainline PPA for one reason or another [1].

  The following patch to dkms.conf should fix the issue:

  --- ./dkms.conf.orig  2021-03-16 04:15:55.077568974 +0700
  +++ /usr/src/zfs-0.8.3/dkms.conf  2021-03-16 04:17:16.598219797 +0700
  @@ -1,6 +1,6 @@
   PACKAGE_NAME="zfs"
   PACKAGE_VERSION="0.8.3"
  -BUILD_EXCLUSIVE_KERNEL="^(4.[0-9]+|5.[01234])."
  +BUILD_EXCLUSIVE_KERNEL='^(4.[0-9]+|5.[01234])\.'
   PACKAGE_CONFIG="/etc/sysconfig/zfs"
   PRE_BUILD="configure
     --prefix=/usr

  Although it's not convenient for me at the moment to create a debdiff.

  Related: LP: #1902701

  [1] For me it's to get a complete fix for LP: #1887190, as Focal's HWE
  kernel doesn't seem to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: zfs-dkms 0.8.3-1ubuntu12.6
  Uname: Linux 5.11.6-051106-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Mar 16 04:26:08 2021
  InstallationDate: Installed on 2021-03-15 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=th_TH.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1907854] Re: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status

[Colin Ian King]

ZFS will refrain from mounting over a currently mounted mount point, so
that is expected.

It would be useful to see what zfs expects the mounted file systems are
and what you had mounted, e.g.

1. See what zfs expectes as the mounted zfs file systems:

sudo zfs list

2. See what was mounted:

cat /proc/mounts



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

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

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade:
  installed zfsutils-linux package post-installation script subprocess
  returned error exit status 1

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  After update zfsutils-linux, the update process tries to mount zfs
  file in /mnt but since in /mnt there are another disk mount fails
  with:

  Setting up zfsutils-linux (0.8.3-1ubuntu12.5) ...
  zfs-import-scan.service is a disabled or a static unit, not starting it.
  zfs-import-scan.service is a disabled or a static unit, not starting it.
  Job for zfs-mount.service failed because the control process exited with 
error code.
  See "systemctl status zfs-mount.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript zfs-mount, action "start" failed.

  ● zfs-mount.service - Mount ZFS filesystems
   Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-12-11 21:05:24 CET; 
8ms ago
 Docs: man:zfs(8)
  Process: 177294 ExecStart=/sbin/zfs mount -a (code=exited, 
status=1/FAILURE)
 Main PID: 177294 (code=exited, status=1/FAILURE)

  dic 11 21:05:24 serv systemd[1]: Starting Mount ZFS filesystems...
  dic 11 21:05:24 serv zfs[177294]: cannot mount '/mnt': directory is not empty
  dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
  dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.
  dic 11 21:05:24 serv systemd[1]: Failed to start Mount ZFS filesystems.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12.5
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.13
  AptOrdering:
   python3-aptdaemon.gtk3widgets:amd64: Install
   aptdaemon:amd64: Install
   python3-aptdaemon:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Dec 11 20:56:40 2020
  ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-03-24 (261 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-19 (206 days ago)

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

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

[Kernel-packages] [Bug 1907854] Re: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status

[Colin Ian King]

3. Also can you provide the output from:

sudo zfs get all | grep mountpoint

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

Title:
  package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade:
  installed zfsutils-linux package post-installation script subprocess
  returned error exit status 1

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  After update zfsutils-linux, the update process tries to mount zfs
  file in /mnt but since in /mnt there are another disk mount fails
  with:

  Setting up zfsutils-linux (0.8.3-1ubuntu12.5) ...
  zfs-import-scan.service is a disabled or a static unit, not starting it.
  zfs-import-scan.service is a disabled or a static unit, not starting it.
  Job for zfs-mount.service failed because the control process exited with 
error code.
  See "systemctl status zfs-mount.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript zfs-mount, action "start" failed.

  ● zfs-mount.service - Mount ZFS filesystems
   Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-12-11 21:05:24 CET; 
8ms ago
 Docs: man:zfs(8)
  Process: 177294 ExecStart=/sbin/zfs mount -a (code=exited, 
status=1/FAILURE)
 Main PID: 177294 (code=exited, status=1/FAILURE)

  dic 11 21:05:24 serv systemd[1]: Starting Mount ZFS filesystems...
  dic 11 21:05:24 serv zfs[177294]: cannot mount '/mnt': directory is not empty
  dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
  dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.
  dic 11 21:05:24 serv systemd[1]: Failed to start Mount ZFS filesystems.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12.5
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.13
  AptOrdering:
   python3-aptdaemon.gtk3widgets:amd64: Install
   aptdaemon:amd64: Install
   python3-aptdaemon:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Dec 11 20:56:40 2020
  ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-03-24 (261 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-19 (206 days ago)

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

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

[Kernel-packages] [Bug 1922651] Re: r8152 tx status -71

[Martin Vysny]

The "usbcore.quirks=17ef:a387:k" kernel parameter workaround seems to be
working excellent so far!

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

Title:
  r8152 tx status -71

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've bought ThinkPad T14s with a USB-based docking station. Everything
  is working marvelously, but from time to time the ethernet port on the
  docking station won't connect. I've discovered the following messages
  in my dmesg:

  [  400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71

  Rebooting the machine doesn't seem to work, turning the ethernet
  connection off and on doesn't seem to work. I have a dualboot
  Linux+Windows (one wants to play games from time to time :-p ) and it
  could be that rebooting from Win to Lin causes this issue, but this
  needs to be confirmed yet. I will try to power off the computer and/or
  the docking station, to see whether that would help.

  I've found numerous bug reports, but they are rather old or may not
  apply to this situation, therefore I figured it's best to open a new
  bug report.

  Thank you so much for your hard work!

  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
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  6 10:00:29 2021
  InstallationDate: Installed on 2021-03-24 (12 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20UH001QMX
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic 
root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash 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: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2020
  dmi.bios.release: 1.30
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET61W(1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UH001QMX
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.30
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14s Gen 1
  dmi.product.name: 20UH001QMX
  dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
  dmi.product.version: ThinkPad T14s Gen 1
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10

[Seth Forshee]

These commits are already included in hirsute, closing the development
task.

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

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

Title:
  SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Groovy:
  In Progress

Bug description:
  The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin
  setup and enable microphones to work correctly when using via the
  audio jacks.

  Patches that are fixing these problems have already been accepted to
  current Linux stable releases:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb

  Commit-hash:

  48698c973e6b4dde94d87cd1ded56d9436e9c97d

  73e7161eab5dee98114987239ec9c87fe8034ddb

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

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

[Kernel-packages] [Bug 1906850] Re: aws: xen-netfront: prevent potential error on hibernate

[Andrea Righi]

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

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

Title:
  aws: xen-netfront: prevent potential error on hibernate

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-aws source package in Focal:
  Fix Released
Status in linux-aws source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  On hibernation xen-netfront is setting the device state on the xenbus
  to "Closing" and then it's waiting for the backend state to
  acknowledge that state (with a timeout). However, if the device is
  already in the state "Closed" this opteration will always hit the
  timeout, preventing the system to hibernate correctly.

  [Test case]

  It is a quite rare condition that can be reproduced
  hibernating/resuming a Xen instance multiple times. When the problem
  happens we should in the log a Xen error message like the following:

Freezing timed out; the device may become inconsistent state

  [Fix]

  If the device is already in the state "Closed", simply tear it down
  without notifying the Xen backend.

  [Regression potential]

  The fix would just prevent aborting hibernation if the netfront device
  is already in a "Closed" state. The resume callback is forcing the
  device into the "Initializing" state anyway, basically forcing a reset
  of the device, so nothing else in the state machine can be potentially
  broken.

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

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

[Kernel-packages] [Bug 1913410] Re: aws: update Xen hibernation patch set

[Andrea Righi]

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

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

Title:
  aws: update Xen hibernation patch set

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-aws source package in Focal:
  Fix Committed
Status in linux-aws source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  Amazon maintains a custom patch to enable hibernation in Xen guests
  that is not upstream yet. This patch set has been updated in AWS AL2
  and we should sync up the patch set in our AWS kernels.

  [Test case]

  Tests have been performed (simply doing multiple hibernate/resume
  cycles) with the new patch set applied and they have shown significant
  improvement in terms of reliability.

  [Fix]

  Backport/apply the new Xen hibernation patch set from AWS AL2.

  [Regression potential]

  The patch set is affecting only Xen (in particular the guest code) and
  only hibernation, so the risk of regressions is restricted to this
  particular scenario (Xen + hibernation).

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

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

[prabhakar pujeri]

test-build verified with intel E810 card working as expected

1. able to see the network interface up 
2. tested ping and wget test

-- 
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 1890641] Re: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.173.20

---
linux-firmware (1.173.20) bionic; urgency=medium

  * Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module
r8169 (LP: #1890641)
- rtl_nic: add firmware files for RTL8153
- rtl_nic: update firmware for RTL8153A

 -- Seth Forshee   Tue, 02 Mar 2021 14:28:08
-0600

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

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 1890641] Update Released

[Brian Murray]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-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 Released

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 1853275] Re: [21.04 FEAT] Log DASD EDIF capability - kernel

[Frank Heimes]

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] Log DASD EDIF capability - kernel

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

Bug description:
  A Linux on Z user can find out if a DASD volume is being accessed
  using authenticated or encrypted links, both in the running system,
  but also based on kernel logs.

  Target: kernel >= kernel 5.5

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

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

[Kernel-packages] [Bug 1887923] Re: [21.04 FEAT] zKVM: Implement full set of zPCI function properties (kernel)

[Frank Heimes]

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] zKVM: Implement full set of zPCI function properties
  (kernel)

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

Bug description:
  Currently not all PCI function properties are passed through to the
  guest. Instead, some default assumptions are being made, which can
  make it difficult or impossible to properly handle the PCI function in
  the guest. The correct approach is to pass the host PCI device's
  properties down to the guest, except for properties that are
  overridden by the user.

  
  Feature request for the kernel part.
  Target - kernel >=5.9, therefore backport

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

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

[Kernel-packages] [Bug 1902862] Re: [21.04 FEAT] EP11 related enhancements for pkey module and zkey tool - kernel part

[Frank Heimes]

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] EP11 related enhancements for pkey module and zkey tool -
  kernel part

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

Bug description:
  Description:
  EP11 related enhancements for pkey module (kernel) 

  This feature is made available with kernel 5.10.

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

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

[Kernel-packages] [Bug 1902866] Re: [21.04 FEAT] zcrypt DD: add state for offline due to error - kernel

[Frank Heimes]

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] zcrypt DD: add state for offline due to error - kernel

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

Bug description:
  Improved error handling requires introduction of new state in zcrypt
  kernel module. (kernel+s390-tools)

  This feature kernel part is available with kernel 5.10

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

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

[Kernel-packages] [Bug 1902046] Re: [21.04 FEAT] Server Time Protocol (STP) leap second handling - kernel

[Frank Heimes]

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] Server Time Protocol (STP) leap second handling - kernel

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

Bug description:
  For time synchronisation Linux currently supports Server Time Protocol (STP).
  STP was explicitly not used as time source for Linux system time, due to 
several reasons:
  - STP is not virtualized (neither z/VM, nor KVM have STP virtualization 
support)
  - missing leap second support for STP in Linux

  This feature implements leap second functionality for STP.

  Business Case:
  HW support, z/OS interoperability

  
  This is the kernel part of the requested feature.
  Will be made available with kernel 5.10.

  Integrated via kernel update.

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

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

[Kernel-packages] [Bug 1853313] Re: [21.04 FEAT] KVM enablement for enhanced hardware diagnose data of guest kernel - kernel part

[Frank Heimes]

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] KVM enablement for enhanced hardware diagnose data of
  guest kernel - kernel part

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

Bug description:
  KVM enablement for enhanced hardware diagnose data of guest kernel

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

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

[Kernel-packages] [Bug 1887921] Re: [21.04 FEAT] NVMe IPL Load Normal support - kernel

[Frank Heimes]

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] NVMe IPL Load Normal support - kernel

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

Bug description:
  Re-IPL for NVMe is currently done by using diag 308 with the "Load Clear" 
subcode, which means that all memory will be cleared. 
  This can increase re-IPL duration considerably on very large machines.

  For list-directed IPL like NVMe or FCP IPL, a "Load Normal" subcode
  was introduced with z14. The "Load Normal" diag 308 subcode allows to
  re-IPL without clearing memory.

  This feature adds kernel and s390-tools support for a new "clear"
  sysfs attribute in /sys/firmware/reipl/nvme, which can be set to
  either "0" or "1" to disable or enable re-IPL with memory clearing.
  The default value is "0", which disables memory clearing.

  Feature request for kernel contribution.
  Target kernel >= 5.9. Therefore a backport need to be provided

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

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

[Kernel-packages] [Bug 1908414] Re: [21.04 FEAT] s390/Kconfig: default PCI_NR_FUNCTIONS to 512

[Frank Heimes]

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

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] s390/Kconfig: default PCI_NR_FUNCTIONS to 512

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

Bug description:
  Summary: s390/Kconfig: default PCI_NR_FUNCTIONS to 512

  Description: On machines with a large number of PCI devices, including
   Virtual Functions and NVMe devices it is quite common that an
   LPAR can see over 100 PCI functions in Standby or even wants
   to use as many.
   For affected distributions this poses a problem as any PCI
   function probed after the limit has been reached is simply
   inaccessible and invisible for older kernels this is even silent.
   This is solved by increasing the PCI_NR_FUNCTIONS Kconfig option
   to 512 matching the recommended setting in the upstream 
defconfig.
   In testing and through code study it was determined that this has
   only neglibile memory use overhead of a handful of 4k pages when
   devices are only visible in Standby.

  Upstream-ID: 10e59217479d733ff50b6e8c6316ecffe8b857cb

  kernel 5.11

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

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

[Kernel-packages] [Bug 1901674] Re: [21.04 FEAT] zcrypt DD: Provide indications that ap bus initialization and DD bindings are complete

[Frank Heimes]

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] zcrypt DD: Provide indications that ap bus initialization
  and DD bindings are complete

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

Bug description:
  Feature Description

  Provide indications to early exploiters of crypto adapters (e.g. dm-
  crypt root devices using the PAES cipher) that the AP bus is
  initialized and all crypto devices are usable.

  Upstream target: kernel 5.10 
  git-commit will be provided , once available.

  3. Business Case
  Enhance security on IBM Z platform

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

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

[Kernel-packages] [Bug 1918110] Re: overlay_map.dtb is in wrong location

[Launchpad Bug Tracker]

This bug was fixed in the package flash-kernel - 3.104ubuntu3

---
flash-kernel (3.104ubuntu3) hirsute; urgency=medium

  * Copy overlay_map.dtb into overlays/ sub-directory instead of the
root of the boot partition (LP: #1918110)
  * Add minor board revisions to db/all.db

 -- Dave Jones   Tue, 06 Apr 2021 11:31:11
+0100

** Changed in: flash-kernel (Ubuntu Hirsute)
   Status: In Progress => Fix Released

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

Title:
  overlay_map.dtb is in wrong location

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Invalid
Status in flash-kernel source package in Focal:
  New
Status in linux-raspi source package in Focal:
  Invalid
Status in flash-kernel source package in Groovy:
  New
Status in linux-raspi source package in Groovy:
  Invalid
Status in flash-kernel source package in Hirsute:
  Fix Released
Status in linux-raspi source package in Hirsute:
  Invalid

Bug description:
  overlay_map.dtb is supposed to be located in /boot/firmware/overlays
  and *not* in /boot/firmware.

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

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

[Kernel-packages] [Bug 1914214] Re: [21.04 FEAT] zkey: LUKS2 Enhancements (s390-tools)

[Frank Heimes]

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

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] zkey: LUKS2 Enhancements (s390-tools)

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

Bug description:
  Extend zkey to also store passphrases for keys used with LUKS2 volumes:
  Add a new option to zkey.

  Will be made available with s390-tools 2.16.0

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

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

[Kernel-packages] [Bug 1887940] Re: [21.04 FEAT] NVMe stand-alone dump support

[Frank Heimes]

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] NVMe stand-alone dump support

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

Bug description:
  Once the system can IPL from an NVMe device it makes sense to support 
stand-alone dump to the NVMe device as well.
  The support is likely to be similar to the SCSI stand-alone dumper, the first 
few mega-bytes need to be saved into the HSA and a specialized dump kernel for 

  Feature will contribute to kernel >= 5.9

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

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

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

[Timo Aaltonen]

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  Fix mic on P620 after S3 resume

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

Bug description:
  [Impact]
  Mic on Lenovo P620 can not record any sound after S3.

  [Fix]
  Query the connector status on system resume.

  [Test]
  With the patch applied, the mic in question works after S3 resume.
  Also tested on some other USB audio and they also work fine.
   
  [Where problems could occur]
  If there's a USB audio device that doesn't like its connectors being
  queried, then this may regress on those devices.
  However I suspect this is the default behavior on other OSes, so it's
  unlikely to happen.

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

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

[Kernel-packages] [Bug 1905023] Re: [21.04 FEAT] SMC-R Link Group (LG) Support - kernel

[Frank Heimes]

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT]  SMC-R Link Group (LG) Support - kernel

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

Bug description:
  Provide support for SMC-R Link Failover / Link Group (LG) Support in
  smc-tools with some additional code required in SMC-R itself.

  This feature request is for the kernel part.
  Target : kernel >=5.11

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

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

[Kernel-packages] [Bug 1853291] Re: [21.04 FEAT] SMC-D v2 Support

[Frank Heimes]

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] SMC-D v2 Support

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

Bug description:
  SMC is currently limited to traffic within a single IP subnet only. SMC v2 
will lift this restriction, which also (confusingly) applies to ISM 
devices/SMC-D.
  This is a strict requirement e.g. for Docker containers.
  Current planning is to have a new ISM device type, titled "ISM v2" for now, 
so users can make a conscious decision whether (conceptually) different IP 
subnets can be interconnected or not, which might be a security concern.

  Business value:
  Prerequisite for proper Docker support

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

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

[Kernel-packages] [Bug 1853286] Re: [21.04 FEAT] Converged HiperSockets/Ethernet Interface - kernel

[Frank Heimes]

** Information type changed from Private to Public

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

Title:
  [21.04 FEAT] Converged HiperSockets/Ethernet Interface - kernel

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

Bug description:
  Support HiperSockets Converged Interface functionality, providing a
  converged interface that forms a single LAN based on HiperSockets (HS)
  and OSA/RoCE. Traffic for target hosts reachable via HS will use HS,
  all other traffic will be switched to OSA/RoCE.

  Simplified network configuration via single network interface; ability
  to communicate with z/OS hosts using HiperSockets Layer 2.

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

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

[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time

[stevecam]

** Also affects: debian
   Importance: Undecided
   Status: New

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

Title:
  nvme drive fails after some time

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Groovy:
  Fix Released
Status in Debian:
  New

Bug description:
  Sorry for the vague title. I thought this was a hardware issue until
  someone else online mentioned their nvme drive goes "read only" after
  some time. I tend not to reboot my system much, so have a large
  journal. Either way this happens once in a while. The / drive is fine,
  but /home is on nvme which just disappears. I reboot and everything is
  fine. But leave it long enough and it'll fail again.

  Here's the most recent snippet about the nvme drive before I restarted
  the system.

  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting 

   
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset 
controller
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset 
controller
  Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure 
status: -19
  Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more 
than 120 seconds.
  Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0   731  2 0x4000
  Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123967, lost async page write
  Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): 
__ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading 
directory lblock 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123917, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123909, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 0, lost sync page write
  Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing 
superblock

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  9 11:56:28 2021
  InstallationDate: Installed on 2020-08-15 (146 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel Corporation NUC8i7HVK
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic 
root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7
  RebootRequiredPkgs:
   linux-image-5.8.0-36-generic
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-34-generic N/A
   

[Kernel-packages] [Bug 1922406] Re: Intel AX210 Wi-Fi card does not work since updating to 1.196

[Seth Forshee]

Looks like 5.11 isn't able to use the new firmware versions added
alongside this file anyway, so I'll get a new version uploaded which
removes all the version 62 API files along with iwlwifi-
ty-a0-gf-a0.pnvm.

** Changed in: linux-firmware (Ubuntu)
   Importance: Undecided => High

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

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Intel AX210 Wi-Fi card does not work since updating to 1.196

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  Running 21.04, updated daily.

  Since updating the linux-firmware package yesterday, the Wireless card
  does not work with current kernel (5.11.0-13).

  The error message is as follows:

  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

  It **does** work with 5.11.0-11 (previous version)

  Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020
  CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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

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

[Kernel-packages] [Bug 1922406] Re: Intel AX210 Wi-Fi card does not work since updating to 1.196

[Seth Forshee]

** Bug watch added: Linux Kernel Bug Tracker #212371
   https://bugzilla.kernel.org/show_bug.cgi?id=212371

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=212371
   Importance: Unknown
   Status: Unknown

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

Title:
  Intel AX210 Wi-Fi card does not work since updating to 1.196

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Running 21.04, updated daily.

  Since updating the linux-firmware package yesterday, the Wireless card
  does not work with current kernel (5.11.0-13).

  The error message is as follows:

  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

  It **does** work with 5.11.0-11 (previous version)

  Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020
  CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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

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

[Kernel-packages] [Bug 1854982] Re: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

[Colin Ian King]

ZFS 2.0.x is now the default for Ubuntu Hirsute 21.04. If anyone would
like to check that this is now compatible with BSD then that would be
useful so we can close this issue.

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

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

Title:
  Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  After I tried to back-up my datapools from Ubuntu 19.10 to FreeBSD
  12.0 as I have done since June each week, I found out it did not work
  anymore. The regression occurred after I reinstalled Ubuntu on my new
  nvme drive. I also had to reorganize my own datapools/datasets,
  because they either moved to the nvme drive or they had to be located
  on 2 HDDs instead of 3. I had one datapool that still works, the
  datapool containing my archives and it is the datapool, that has NOT
  been reorganized. I tried for a whole long day to get the backup
  working again, but I failed. I compared the properties from datapool
  and dataset, but did not see any problem there. Only a lot of new
  features and properties not present before and not present in FreeBSD.
  I used FreeBSD, because I use for backup an old 32-bits Pentium.

  I have two complaints:
  - the Ubuntu upgrade did cost me the compatibility with FreeBSD. Open-ZFS? :(
  - the system transfers the dataset and at the end of a long transfer it 
decides to quit and the error messages are completely useless and self 
contradicting. 

  On the first try it say the dataset does exist and on the second try it says 
it does NOT exist. One of the two is completely wrong. Some consistency and 
some clearer error messages would be helpful for the user.
  See the following set of strange set error messages on two tries:

  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive zroot/hp-data/dummy
  cannot receive new filesystem stream: destination 'zroot/hp-data/dummy' exists
  must specify -F to overwrite it
  root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | 
ssh 192.168.1.100 zfs receive -F zroot/hp-data/dummy
  cannot receive new filesystem stream: dataset does not exist

  A 2nd subset of my backup is stored on the laptop and that still
  works. I also compared the properties with those of my laptop, that
  still has its original datapools of begin of the year. I aligned the
  properties of FreeBSD with those of my laptop, but it did not help.

  I attach the properties of the datapool and dataset from both FreeBSD
  and Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  3 13:35:08 2019
  InstallationDate: Installed on 2019-11-30 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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

[Kernel-packages] [Bug 1922242] Re: openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

[Robie Basak]

Hello Kleber, or anyone else affected,

Accepted openafs into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openafs/1.6.15-1ubuntu1.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: openafs (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in openafs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in openafs source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  autopkgtest caught a build failure with openafs-modules-dkms with the 
xenial/linux kernel currently in -proposed (4.4.0-207.239).

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz

  Build error:

    CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
   code = inode_change_ok(inode, );
  ^
  cc1: some warnings being treated as errors

  This was caused by commit "fs: Give dentry to inode_change_ok()
  instead of inode" applied to xenial/linux as part of the fixes for
  CVE-2015-1350, which renamed inode_change_ok() to setattr_prepare().

  [Fix]
  The proposed fix is to cherry-pick commit 
8aeb711eeaa5ddac5a74c354091e2d4f7ac0cd63 "Linux 4.9: inode_change_ok() becomes 
setattr_prepare()" from openafs repository (git://git.openafs.org/openafs.git).

  [Test]
  Install openafs-modules-dkms on a xenial system running an older kernel 
without the interface change (<4.4.0-207) and with a newer kernel with the 
interface change (>=4.4.0-207). The openafs module should be built and loaded 
with all kernels.

  [Where problems could occur]
  The fix is based on the detection made during build time of the function 
available on the kernel headers. If the detection doesn't work correctly the 
build would fail.

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1922406

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

Title:
  Intel AX210 Wi-Fi card does not work since updating to 1.196

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Running 21.04, updated daily.

  Since updating the linux-firmware package yesterday, the Wireless card
  does not work with current kernel (5.11.0-13).

  The error message is as follows:

  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

  It **does** work with 5.11.0-11 (previous version)

  Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020
  CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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

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