date:20210618

** Tags added: gt

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

Title:
  cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New

Bug description:
  [Impact]
  Test case cfs_bandwidth01 in LTP sched test suite is a reproducer of a CFS 
unthrottle_cfs_rq() issue (fe61468b2cbc2b sched/fair: Fix enqueue_task_fair 
warning).

  This test triggers a warning on our 4.15 kernel:
   LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5)
   [ cut here ]
   rq->tmp_alone_branch != >leaf_cfs_rq_list
   WARNING: CPU: 0 PID: 0 at 
/build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 
unthrottle_cfs_rq+0x16f/0x200
   Modules linked in: input_leds joydev serio_raw mac_hid qemu_fw_cfg kvm_intel 
kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl 
lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm psmouse virtio_blk pata_acpi floppy 
virtio_net i2c_piix4
   CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic #148-Ubuntu
   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 
04/01/2014
   RIP: 0010:unthrottle_cfs_rq+0x16f/0x200
   RSP: 0018:989ebfc03e80 EFLAGS: 00010082
   RAX:  RBX: 989eb4c6ac00 RCX: 
   RDX: 0005 RSI: acb63c4d RDI: 0046
   RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: acb63c20
   R10:  R11: 0001 R12: 989eb57fe400
   R13: 989ebfc21900 R14: 0001 R15: 0001
   FS: () GS:989ebfc0() knlGS:
   CS: 0010 DS:  ES:  CR0: 80050033
   CR2: 55593258d618 CR3: 7a044000 CR4: 06f0
   DR0:  DR1:  DR2: 
   DR3:  DR6: fffe0ff0 DR7: 0400
   Call Trace:
   
   distribute_cfs_runtime+0xc3/0x110
   sched_cfs_period_timer+0xff/0x220
   ? sched_cfs_slack_timer+0xd0/0xd0
   __hrtimer_run_queues+0xdf/0x230
   hrtimer_interrupt+0xa0/0x1d0
   smp_apic_timer_interrupt+0x6f/0x140
   apic_timer_interrupt+0x90/0xa0
   
   RIP: 0010:native_safe_halt+0x12/0x20
   RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: ff11
   RAX: abbc9280 RBX:  RCX: 
   RDX:  RSI:  RDI: 
   RBP: ac603e28 R08: 00af39850067 R09: 989e73749d00
   R10:  R11: 7fff R12: 
   R13:  R14:  R15: 
   ? __sched_text_end+0x1/0x1
   default_idle+0x20/0x100
   arch_cpu_idle+0x15/0x20
   default_idle_call+0x23/0x30
   do_idle+0x172/0x1f0
   cpu_startup_entry+0x73/0x80
   rest_init+0xae/0xb0
   start_kernel+0x4dc/0x500
   x86_64_start_reservations+0x24/0x26
   x86_64_start_kernel+0x74/0x77
   secondary_startup_64+0xa5/0xb0
   Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 00 75 5f 31 
db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 48 85 db 74 
43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00
   ---[ end trace b6b9a70bc2945c0c ]---

  [Fix]
    * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning
    * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more
    * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list
    * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path
    * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair()

  Backport needed for Bionic since we're missing some new variables introduced 
in the following commits and their corresponding fixes:
    * 9f68395333ad7f sched/pelt: Add a new runnable average signal
    * 6212437f0f6043 sched/fair: Fix runnable_avg for throttled cfs
    * 43e9f7f231e40e sched/fair: Start tracking SCHED_IDLE tasks count in cfs_rq

  I have also searched in the upstream tree to see if there is any other
  commit claim to a fix of these but didn't see any.

  [Test]
  Test kernel can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1931325-cfs_bandwidth01/

  With these patches applied, the test can pass without any issue.

  I have also run the whole sched test suite in LTP to make sure it
  didn't cause any other problem.

  [Regression Potential]
  * Completely Fair Scheduler (CFS) is a vital part in the kernel,

  [Other Info]
  Test case description:
   * Creates

[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

2021-06-18 Thread Bas Schilperoord

When is this going to be fixed? It's really annoying we have to use old
drivers in order to get it to work. 460.56 works, but all the others
don't

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

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Triaged

Bug description:
  I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute

  Jun 03 16:26:57 willow kernel: Oops:  [#1] SMP PTI
  Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P 
  OE 5.11.0-18-generic #19-Ubuntu
  Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System 
Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI: 
  Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 
R09: 8e318220acb8
  Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 
R12: 0400
  Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 
R15: 0800
  Jun 03 16:26:57 willow kernel: FS:  7f5807f38a40() 
GS:8e3466dc() knlGS:
  Jun 03 16:26:57 willow kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 
CR4: 003706e0
  Jun 03 16:26:57 willow kernel: DR0:  DR1:  
DR2: 
  Jun 03 16:26:57 willow kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jun 03 16:26:57 willow kernel: Call Trace:
  Jun 03 16:26:57 willow kernel:  ? _nv015556rm+0x7fd/0x1020 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv027155rm+0x22c/0x4f0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017787rm+0x303/0x5e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017789rm+0xe1/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv022829rm+0xed/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv023065rm+0x30/0x60 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv000704rm+0x16da/0x22b0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? rm_init_adapter+0xc5/0xe0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nv_open_device+0x122/0x8e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nvidia_open+0x2b7/0x560 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nvidia_frontend_open+0x58/0xa0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? chrdev_open+0xf7/0x220
  Jun 03 16:26:57 willow kernel:  ? cdev_device_add+0x90/0x90
  Jun 03 16:26:57 willow kernel:  ? do_dentry_open+0x156/0x370
  Jun 03 16:26:57 willow kernel:  ? vfs_open+0x2d/0x30
  Jun 03 16:26:57 willow kernel:  ? do_open+0x1c3/0x340
  Jun 03 16:26:57 willow kernel:  ? path_openat+0x10a/0x1d0
  Jun 03 16:26:57 willow kernel:  ? do_filp_open+0x8c/0x130
  Jun 03 16:26:57 willow kernel:  ? __check_object_size+0x1c/0x20
  Jun 03 16:26:57 willow kernel:  ? do_sys_openat2+0x9b/0x150
  Jun 03 16:26:57 willow kernel:  ? __x64_sys_openat+0x56/0x90
  Jun 03 16:26:57 willow kernel:  ? do_syscall_64+0x38/0x90
  Jun 03 16:26:57 willow kernel:  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) 
zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) >
  Jun 03 16:26:57 willow kernel:  sunrpc ip_tables x_tables autofs4 btrfs 
blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c>
  Jun 03 16:26:57 willow kernel: CR2: 0170
  Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]---
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI:

[Kernel-packages] [Bug 1827866] Re: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure / X-aws

Observed in B/KVM, cycle sru-20210531.

** Tags added: kvm linux-kvm sru-20210531

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

Title:
  vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure /
  X-aws

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New
Status in linux-oracle source package in Xenial:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-kvm source package in Bionic:
  New
Status in linux-oracle source package in Bionic:
  New

Bug description:
  vmx_apicv_test from ubuntu_kvm_unit_tests failed on X-KVM:
  FAIL vmx_apicv_test (timeout; duration=10)

   the test was terminated with return code 124:

  # TESTNAME=vmx_apicv_test TIMEOUT=10 ACCEL= ./x86/run x86/vmx.flat -smp 1 
-cpu host,+vmx -append "apic_reg_virt_test virt_x2apic_mode_test"
  timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu 
host,+vmx -append apic_reg_virt_test virt_x2apic_mode_test # -initrd 
/tmp/tmp.K6b7rjmgp8
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 477000
  cr4 = 20

  Test suite: apic_reg_virt_test
  --- Virtualize APIC accesses test ---
  PASS: xapic - reading 0x000: got APIC access exit @ page offset 0x000, want 
0x000
  PASS: xapic - writing 0x12345678 to 0x000: got APIC access exit @ page offset 
0x000, want 0x000
  PASS: xapic - reading 0x010: got APIC access exit @ page offset 0x010, want 
0x010
  PASS: xapic - writing 0x12345678 to 0x010: got APIC access exit @ page offset 
0x010, want 0x010
  PASS: xapic - reading 0x020: got APIC access exit @ page offset 0x020, want 
0x020
  PASS: xapic - writing 0x12345678 to 0x020: got APIC access exit @ page offset 
0x020, want 0x020
  PASS: xapic - reading 0x030: got APIC access exit @ page offset 0x030, want 
0x030
  
  
  PASS: xapic - writing 0x12345678 to 0x380: non-virtualized write; val is 
0x12345678, want 0x12345678
  PASS: xapic - reading 0x390: read 0x12345678, expected 0x12345678.
  PASS: xapic - writing 0x12345678 to 0x390: non-virtualized 
writqemu-system-x86_64: terminating on signal 15 from pid 1327

  # echo $?
  124

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1044-kvm 4.4.0-1044.50
  ProcVersionSignature: Ubuntu 4.4.0-1044.50-kvm 4.4.177
  Uname: Linux 4.4.0-1044-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon May  6 10:47:17 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1831449] Re: memory in ubuntu_kvm_unit_tests fails (clflushopt / cwlb ABSENT)

Observed in B/KVM, cycle sru-20210531.

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

Title:
  memory in ubuntu_kvm_unit_tests fails (clflushopt / cwlb ABSENT)

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New

Bug description:
  Need to run this on oracle manually to get the full output:
   TESTNAME=memory TIMEOUT=90s ACCEL= ./x86/run x86/memory.flat -smp 1 -cpu host
   FAIL memory (8 tests, 2 unexpected failures)

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

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

[Kernel-packages] [Bug 1932966] [NEW] kvm_unit_tests: emulator test fails on 4.15 kernel, timeout

Public bug reported:

Found this on B/KVM, current cycle (sru-20210531):

18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11 DEBUG| [stderr] RAX=000a RBX=e000 
RCX=03fd RDX=03f8
18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991 
RBP=0051b440 RSP=0051b420
18:27:11 DEBUG| [stderr] R8 =000a R9 =03f8 
R10=000d R11=
18:27:11 DEBUG| [stderr] R12=e000 R13= 
R14=d000 R15=
18:27:11 DEBUG| [stderr] RIP=00400a0c RFL=00010006 [-P-] CPL=0 II=0 
A20=1 SMM=0 HLT=0
18:27:11 DEBUG| [stderr] ES =0010   00c09300 DPL=0 DS   
[-WA]
18:27:11 DEBUG| [stderr] CS =0008   00a09b00 DPL=0 CS64 
[-RA]
18:27:11 DEBUG| [stderr] SS =0010   00c09300 DPL=0 DS   
[-WA]
18:27:11 DEBUG| [stderr] DS =0010   00c09300 DPL=0 DS   
[-WA]
18:27:11 DEBUG| [stderr] FS =0010   00c09300 DPL=0 DS   
[-WA]
18:27:11 DEBUG| [stderr] GS =0010 0051a4d0  00c09300 DPL=0 DS   
[-WA]
18:27:11 DEBUG| [stderr] LDT=   8200 DPL=0 LDT
18:27:11 DEBUG| [stderr] TR =0080 0041207a  8b00 DPL=0 
TSS64-busy
18:27:11 DEBUG| [stderr] GDT= 0041100a 106f
18:27:11 DEBUG| [stderr] IDT= 0041 0fff
18:27:11 DEBUG| [stderr] CR0=80010011 CR2= CR3=01007000 
CR4=0220
18:27:11 DEBUG| [stderr] DR0= DR1= 
DR2= DR3= 
18:27:11 DEBUG| [stderr] DR6=0ff0 DR7=0400
18:27:11 DEBUG| [stderr] EFER=0500
18:27:11 DEBUG| [stderr] Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 
0f 6f 45 e0 <0f> 11 03 48 89 de 48 8d 7d e0 e8 f8 f9 ff ff 0f b6 f8 be a1 8f 41 
00 b8 00 00 00 00 e8 05
18:28:40 DEBUG| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 
13634 (timeout)
18:28:40 DEBUG| [stdout] FAIL emulator (timeout; duration=90s)
[...]
TestError: Test failed for emulator
18:28:40 ERROR| child process failed
18:28:40 DEBUG| Traceback (most recent call last):
18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/parallel.py", line 25, in 
fork_start
18:28:40 DEBUG| l()
18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/job.py", line 505, in 

18:28:40 DEBUG| l = lambda: test.runtest(self, url, tag, args, dargs)
18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/test.py", line 125, in 
runtest
18:28:40 DEBUG| job.sysinfo.log_after_each_iteration)
18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/shared/test.py", line 913, 
in runtest
18:28:40 DEBUG| mytest._exec(args, dargs)
18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/shared/test.py", line 411, 
in _exec
18:28:40 DEBUG| _call_test_function(self.execute, *p_args, **p_dargs)
18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/shared/test.py", line 823, 
in _call_test_function
18:28:40 DEBUG| return func(*args, **dargs)
18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/shared/test.py", line 291, 
in execute
18:28:40 DEBUG| postprocess_profiled_run, args, dargs)
18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/shared/test.py", line 212, 
in _call_run_once
18:28:40 DEBUG| self.run_once(*args, **dargs)
18:28:40 DEBUG|   File 
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
 line 82, in run_once
18:28:40 DEBUG| raise error.TestError("Test failed for 
{}".format(test_name))
18:28:40 DEBUG| TestError: Test failed for emulator
18:28:41 INFO | ERROR   ubuntu_kvm_unit_tests.emulator  
ubuntu_kvm_unit_tests.emulator  timestamp=1624040921localtime=Jun 18 
18:28:41   Test failed for emulator
18:28:41 INFO | END ERROR   ubuntu_kvm_unit_tests.emulator  
ubuntu_kvm_unit_tests.emulator  timestamp=1624040921localtime=Jun 18 
18:28:41

** Affects: ubuntu-kernel-tests
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed

** Affects: linux-kvm (Ubuntu)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed

** Affects: linux-kvm (Ubuntu Bionic)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed


** Tags: 4.15 bionic kvm linux-kvm sru-20210531 ubuntu-kvm-unit-tests

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

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

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

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

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

** Changed in:

[Kernel-packages] [Bug 1932965] [NEW] selftests/net/rtnetlink - Failure in RISC-V (uuidgen command not found)

Public bug reported:

Found this on G/RISC-V, cycle sru-20210531:

02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found
02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found
02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found
02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found
02:41:52 DEBUG| [stdout] # FAIL: set interface alias test-dummy0 to 
02:41:52 DEBUG| [stdout] # PASS: vrf
02:41:54 DEBUG| [stdout] # PASS: vxlan
02:41:55 DEBUG| [stdout] # PASS: fou
02:41:55 DEBUG| [stdout] # PASS: macsec
02:41:58 DEBUG| [stdout] # PASS: ipsec
02:42:01 DEBUG| [stdout] # PASS: ipsec_offload
02:42:02 DEBUG| [stdout] # PASS: bridge fdb get
02:42:03 DEBUG| [stdout] # PASS: neigh get
02:42:03 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1

Seems uuidgen is from package "uuid-runtime", not sure if this was not
installed in the environment where test ran.

** Affects: ubuntu-kernel-tests
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed

** Affects: linux (Ubuntu Groovy)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed


** Tags: 5.8 groovy riscv riscv64 sru-20210531

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

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

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

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

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

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

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

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

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

Title:
  selftests/net/rtnetlink - Failure in RISC-V (uuidgen command not
  found)

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

Bug description:
  Found this on G/RISC-V, cycle sru-20210531:

  02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not 
found
  02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not 
found
  02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not 
found
  02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not 
found
  02:41:52 DEBUG| [stdout] # FAIL: set interface alias test-dummy0 to 
  02:41:52 DEBUG| [stdout] # PASS: vrf
  02:41:54 DEBUG| [stdout] # PASS: vxlan
  02:41:55 DEBUG| [stdout] # PASS: fou
  02:41:55 DEBUG| [stdout] # PASS: macsec
  02:41:58 DEBUG| [stdout] # PASS: ipsec
  02:42:01 DEBUG| [stdout] # PASS: ipsec_offload
  02:42:02 DEBUG| [stdout] # PASS: bridge fdb get
  02:42:03 DEBUG| [stdout] # PASS: neigh get
  02:42:03 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1

  Seems uuidgen is from package "uuid-runtime", not sure if this was not
  installed in the environment where test ran.

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

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

[Kernel-packages] [Bug 1932957] [NEW] Focal update: v5.4.125 upstream stable release

2021-06-18 Thread Kamal Mostafa

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.4.125 upstream stable release
   from git://git.kernel.org/

btrfs: tree-checker: do not error out if extent ref hash doesn't match
net: usb: cdc_ncm: don't spew notifications
ALSA: usb: update old-style static const declaration
nl80211: validate key indexes for cfg80211_registered_device
hwmon: (dell-smm-hwmon) Fix index values
netfilter: conntrack: unregister ipv4 sockopts on error unwind
efi: Allow EFI_MEMORY_XP and EFI_MEMORY_RO both to be cleared
efi: cper: fix snprintf() use in cper_dimm_err_location()
vfio/pci: Fix error return code in vfio_ecap_init()
vfio/pci: zap_vma_ptes() needs MMU
samples: vfio-mdev: fix error handing in mdpy_fb_probe()
vfio/platform: fix module_put call in error flow
ipvs: ignore IP_VS_SVC_F_HASHED flag when adding service
HID: pidff: fix error return code in hid_pidff_init()
HID: i2c-hid: fix format string mismatch
net/sched: act_ct: Fix ct template allocation for zone 0
ACPICA: Clean up context mutex during object deletion
netfilter: nft_ct: skip expectations for confirmed conntrack
netfilter: nfnetlink_cthelper: hit EBUSY on updates if size mismatches
ieee802154: fix error return code in ieee802154_add_iface()
ieee802154: fix error return code in ieee802154_llsec_getparams()
ixgbevf: add correct exception tracing for XDP
ipv6: Fix KASAN: slab-out-of-bounds Read in fib6_nh_flush_exceptions
ice: write register with correct offset
ice: Fix VFR issues for AVF drivers that expect ATQLEN cleared
ice: Allow all LLDP packets from PF to Tx
i2c: qcom-geni: Add shutdown callback for i2c
i40e: optimize for XDP_REDIRECT in xsk path
i40e: add correct exception tracing for XDP
arm64: dts: ls1028a: fix memory node
arm64: dts: zii-ultra: fix 12V_MAIN voltage
ARM: dts: imx7d-meerkat96: Fix the 'tuning-step' property
ARM: dts: imx7d-pico: Fix the 'tuning-step' property
ARM: dts: imx: emcon-avari: Fix nxp,pca8574 #gpio-cells
bus: ti-sysc: Fix flakey idling of uarts and stop using swsup_sidle_act
tipc: add extack messages for bearer/media failure
tipc: fix unique bearer names sanity check
Bluetooth: fix the erroneous flush_work() order
Bluetooth: use correct lock to prevent UAF of hdev object
net: caif: added cfserl_release function
net: caif: add proper error handling
net: caif: fix memory leak in caif_device_notify
net: caif: fix memory leak in cfusbl_device_notify
HID: i2c-hid: Skip ELAN power-on command after reset
HID: magicmouse: fix NULL-deref on disconnect
HID: multitouch: require Finger field to mark Win8 reports as MT
ALSA: timer: Fix master timer notification
ALSA: hda: Fix for mute key LED for HP Pavilion 15-CK0xx
ARM: dts: imx6dl-yapp4: Fix RGMII connection to QCA8334 switch
ARM: dts: imx6q-dhcom: Add PU,VDD1P1,VDD2P5 regulators
ext4: fix bug on in ext4_es_cache_extent as ext4_split_extent_at failed
usb: dwc2: Fix build in periphal-only mode
pid: take a reference when initializing `cad_pid`
ocfs2: fix data corruption by fallocate
nfc: fix NULL ptr dereference in llcp_sock_getname() after failed connect
drm/amdgpu: Don't query CE and UE errors
drm/amdgpu: make sure we unpin the UVD BO
x86/apic: Mark _all_ legacy interrupts when IO/APIC is missing
btrfs: mark ordered extent and inode with error if we fail to finish
btrfs: fix error handling in btrfs_del_csums
btrfs: return errors from btrfs_del_csums in cleanup_ref_head
btrfs: fixup error handling in fixup_inode_link_counts
mm, hugetlb: fix simple resv_huge_pages underflow on UFFDIO_COPY
bnxt_en: Remove the setting of dev_port.
mm: add thp_order
XArray: add xa_get_order
XArray: add xas_split
mm/filemap: fix storing to a THP shadow entry
btrfs: fix unmountable seed device after fstrim
KVM: SVM: Truncate GPR value for DR and CR accesses in !64-bit mode
KVM: arm64: Fix debug register indexing
lib/lz4: explicitly support in-place decompression
xen-pciback: redo VF placement in the virtual topology
i2c: qcom-geni: Suspend and resume the bus during SYSTEM_SLEEP_PM ops
neighbour: allow NUD_NOARP entries to be forced GCed
Linux 5.4.125
UBUNTU: upstream stable to v5.4.125

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

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

[Kernel-packages] [Bug 1932582] Re: Implement support for Intel SGX

2021-06-18 Thread Tim Gardner

** Description changed:

  Backport Linux kernel 5.11 SGX native support to new Azure Ubuntu 20.04
  releases.
+ 
+ SF:00308240

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

Title:
  Implement support for Intel SGX

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  New
Status in linux-azure source package in Focal:
  In Progress

Bug description:
  Backport Linux kernel 5.11 SGX native support to new Azure Ubuntu 20.04
  releases.

  SF:00308240

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

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

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

Observed on G/RISC-V , cycle sru-20210531 .

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

Title:
  ubuntu_ftrace_smoke_test timeout on G-riscv

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

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

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

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

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

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

[Kernel-packages] [Bug 1905728] Re: log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on G-riscv

Observed on G/RISC-V , cycle sru-20210531 .

** Tags added: sru-20210531

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

Title:
  log_check / tainted_check failed in ubuntu_boot because of warnings
  (Found insecure W+X mapping at address) found on G-riscv

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

Bug description:
  Issue found on 5.8.0-10-generic riscv

  Message reported on boot.

  [   13.483103] [ cut here ]
  [   13.483711] riscv/mm: Found insecure W+X mapping at address 
(ptrval)/0xffdff800
  [   13.484542] WARNING: CPU: 5 PID: 1 at arch/riscv/mm/ptdump.c:200 
note_page+0x24c/0x252
  [   13.485175] Modules linked in:
  [   13.485606] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic 
#12-Ubuntu
  [   13.486091] epc: ffe000208f18 ra : ffe000208f18 sp : 
ffe1f5bfbb30
  [   13.486471]  gp : ffe001728ee0 tp : ffe1f5bf5080 t0 : 
ffe00173ed88
  [   13.486850]  t1 : ffe00173ed20 t2 : 0001fecbe000 s0 : 
ffe1f5bfbb80
  [   13.487250]  s1 : ffe1f5bfbe10 a0 : 0053 a1 : 
0020
  [   13.487633]  a2 : ffe1f5bfb870 a3 :  a4 : 
ffe0016200f8
  [   13.488040]  a5 : ffe0016200f8 a6 : 00b5 a7 : 
ffe0006f2806
  [   13.488421]  s2 : ffdff8001000 s3 :  s4 : 
0004
  [   13.488800]  s5 :  s6 :  s7 : 
ffe1f5bfbd20
  [   13.489322]  s8 : ffdff8001000 s9 : ffe00172a148 s10: 
ffdff8002000
  [   13.489738]  s11: ffe000c16e20 t3 : 0003cec0 t4 : 
0003cec0
  [   13.490119]  t5 :  t6 : ffe001739462
  [   13.490406] status: 0120 badaddr:  cause: 
0003
  [   13.490849] ---[ end trace 607c551edff1ef12 ]---

  Please find attachment for the boot dmesg log.

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

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

[Kernel-packages] [Bug 1932585] [NEW] Please block application of hirsute linux/bits.h: fix compilation error with GENMASK for this cycle

2021-06-18 Thread Terry Rudd

Public bug reported:

The following upstream changes in 5.13-rc3 [1] broke Mellanox OFED 
compatibility:
https://patches.linaro.org/patch/451093/

Mellanox has confirmed that OFED5.3 installation fails with this patch
and they are working to check older versions. They have asked us to keep
them informed on when this patch set will come into which kernel series,
which we've agreed to do.  The intent of this bug is to block
application of the patch set until we get confirmation of Mellanox's
awareness.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Terry Rudd (terrykrudd)
 Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Terry Rudd (terrykrudd)

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

Title:
  Please block application of hirsute  linux/bits.h: fix compilation
  error with GENMASK for this cycle

Status in linux package in Ubuntu:
  New

Bug description:
  The following upstream changes in 5.13-rc3 [1] broke Mellanox OFED 
compatibility:
  https://patches.linaro.org/patch/451093/

  Mellanox has confirmed that OFED5.3 installation fails with this patch
  and they are working to check older versions. They have asked us to
  keep them informed on when this patch set will come into which kernel
  series, which we've agreed to do.  The intent of this bug is to block
  application of the patch set until we get confirmation of Mellanox's
  awareness.

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

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

[Kernel-packages] [Bug 1932586] [NEW] Processes launched during the NIC load is high may hang up.

2021-06-18 Thread Hatuki Maruyama

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
❯ lsb_release -rd
Description:Ubuntu 21.04
Release:21.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
❯ LANG=C apt-cache policy linux-raspi
linux-raspi:
  Installed: 5.11.0.1009.7
  Candidate: 5.11.0.1009.7
  Version table:
 *** 5.11.0.1009.7 500
500 http://ports.ubuntu.com/ubuntu-ports hirsute-updates/main arm64 
Packages
500 http://ports.ubuntu.com/ubuntu-ports hirsute-security/main arm64 
Packages
100 /var/lib/dpkg/status
 5.11.0.1007.5 500
500 http://ports.ubuntu.com/ubuntu-ports hirsute/main arm64 Packages

3) What you expected to happen
Processes launched during the NIC load is high will exit normally.

4) What happened instead
I'm using hirsute on Raspberry Pi 4 model B(4GB RAM).
Some processes launched during the NIC load is high might not exit.

What "NIC load is high" means:
- I have configured crontab to run Ookla's speedtest-cli which generates heavy 
network traffic every 15 minites.
- During speedtest-cli, Softirq becomes higher.
- SoC(BCM2711) built-in NIC(driver is bcmgenet)

What "may not exit" means:
- Some processes launched during speedtest-cli is running will not exit. It 
remains with consuming CPU 100% and not accept any signals including SIGKILL.
- Those processes can't be attached by gdb or strace. Trying to do so, gdb and 
strace will freeze.

I could't terminate the processes in any way. But the system could be
rebooted by "sudo reboot" command.

I configured RFS/RPS to distribute Softirq among CPU cores. It was quite
effective, but did not prevent the problem completely.

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


** Tags: arm64 hirsute

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

Title:
  Processes launched during the NIC load is high may hang up.

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  ❯ lsb_release -rd
  Description:Ubuntu 21.04
  Release:21.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ❯ LANG=C apt-cache policy linux-raspi
  linux-raspi:
Installed: 5.11.0.1009.7
Candidate: 5.11.0.1009.7
Version table:
   *** 5.11.0.1009.7 500
  500 http://ports.ubuntu.com/ubuntu-ports hirsute-updates/main arm64 
Packages
  500 http://ports.ubuntu.com/ubuntu-ports hirsute-security/main arm64 
Packages
  100 /var/lib/dpkg/status
   5.11.0.1007.5 500
  500 http://ports.ubuntu.com/ubuntu-ports hirsute/main arm64 Packages

  3) What you expected to happen
  Processes launched during the NIC load is high will exit normally.

  4) What happened instead
  I'm using hirsute on Raspberry Pi 4 model B(4GB RAM).
  Some processes launched during the NIC load is high might not exit.

  What "NIC load is high" means:
  - I have configured crontab to run Ookla's speedtest-cli which generates 
heavy network traffic every 15 minites.
  - During speedtest-cli, Softirq becomes higher.
  - SoC(BCM2711) built-in NIC(driver is bcmgenet)

  What "may not exit" means:
  - Some processes launched during speedtest-cli is running will not exit. It 
remains with consuming CPU 100% and not accept any signals including SIGKILL.
  - Those processes can't be attached by gdb or strace. Trying to do so, gdb 
and strace will freeze.

  I could't terminate the processes in any way. But the system could be
  rebooted by "sudo reboot" command.

  I configured RFS/RPS to distribute Softirq among CPU cores. It was
  quite effective, but did not prevent the problem completely.

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

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

[Kernel-packages] [Bug 1932582] [NEW] Implement support for Intel SGX

2021-06-18 Thread Tim Gardner

Public bug reported:

Backport Linux kernel 5.11 SGX native support to new Azure Ubuntu 20.04
releases.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: In Progress

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

** Affects: linux-azure (Ubuntu Focal)
 Importance: Undecided
 Status: In Progress

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

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

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

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

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

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

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

Title:
  Implement support for Intel SGX

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  New
Status in linux-azure source package in Focal:
  In Progress

Bug description:
  Backport Linux kernel 5.11 SGX native support to new Azure Ubuntu 20.04
  releases.

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

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

[Kernel-packages] [Bug 1927533] Re: selftests/net/test_bpf fails for linux-kvm due to lack of Kconfig

Observed in B/KVM cycle sru-20210531 .

** Tags added: sru-20210531

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

Title:
  selftests/net/test_bpf fails for linux-kvm due to lack of Kconfig

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

Bug description:
  Kernel selftest "test_bpf" fails for B/linux-kvm due to lack of
  Kconfig:

  
  grep -v "#" tools/testing/selftests/net/test_bpf.sh 

  if /sbin/modprobe -q test_bpf ; then
  /sbin/modprobe -q -r test_bpf;
  echo "test_bpf: ok";
  else
  echo "test_bpf: [FAIL]";
  exit 1;
  fi

  
  Checking the config files, for example:

  # grep -n "TEST_BPF" /boot/config-4.15.0-1089-kvm 
  2310:# CONFIG_TEST_BPF is not set

  # grep -n "TEST_BPF" /boot/config-4.15.0-142-generic 
  9105:CONFIG_TEST_BPF=m

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

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

[Kernel-packages] [Bug 1831449] Re: memory in ubuntu_kvm_unit_tests fails (clflushopt / cwlb ABSENT)

Observed in F/KVM, cycle sru-20210531.

** Tags added: focal

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

Title:
  memory in ubuntu_kvm_unit_tests fails (clflushopt / cwlb ABSENT)

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New

Bug description:
  Need to run this on oracle manually to get the full output:
   TESTNAME=memory TIMEOUT=90s ACCEL= ./x86/run x86/memory.flat -smp 1 -cpu host
   FAIL memory (8 tests, 2 unexpected failures)

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

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

[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed with timeout

Issue observed in F/KVM, cycle sru-20210531.

** Tags added: 5.4 focal

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

Title:
  apic test in kvm-unit-test failed with timeout

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure-edge source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-azure-edge source package in Bionic:
  New

Bug description:
  With Joshua's comment in bug 1719524: "Nested KVM can only be tried on
  instance sizes with nested Hypervisor support: Ev3 and Dv3.", although
  the instance name is E4v3 here but I can start a KVM on it.

  Test apic will timeout on it.

  Steps:
  1. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests; ./configure; make
  3. Run the apic test as root:
   
  # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline
  timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  FAIL: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  PASS: nmi-after-sti
  qemu-system-x86_64: terminating on signal 15 from pid 7246

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4
  ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14
  Uname: Linux 4.14.0-1004-azure-edge x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb  8 06:00:55 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-azure-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: linux-azure-edge
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-1009-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev 
sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1831449] Re: memory in ubuntu_kvm_unit_tests fails (clflushopt / cwlb ABSENT)

Observed in G/KVM, cycle sru-20210531.

** Tags added: 5.8 groovy

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

Title:
  memory in ubuntu_kvm_unit_tests fails (clflushopt / cwlb ABSENT)

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New

Bug description:
  Need to run this on oracle manually to get the full output:
   TESTNAME=memory TIMEOUT=90s ACCEL= ./x86/run x86/memory.flat -smp 1 -cpu host
   FAIL memory (8 tests, 2 unexpected failures)

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

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

[Kernel-packages] [Bug 1892855] Re: [Potential Regression] hyperv_connections / hyperv_stimer / hyperv_synic failed on B-i386 / B-5.4 i386

Issue observed in G/KVM, cycle sru-20210531.

** Tags added: 5.8 groovy kvm linux-kvm sru-20210531

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

Title:
  [Potential Regression] hyperv_connections / hyperv_stimer /
  hyperv_synic failed on B-i386 / B-5.4 i386

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

Bug description:
  Issue found on 4.15.0-114.115, with i386 generic /lowlatency on node
  fozzie.

  All 3 tests failed with timeout issue:
  * hyperv_connections
   timeout -k 1s --foreground 90s /usr/bin/qemu-system-i386 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.UwdQ0PZort -smp 2 
-cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd 
/tmp/tmp.GNmO7BfE7a
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   enabling apic
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 453000
   cr4 = 10
   EAX=00459001 EBX=0040aae0 ECX=4083 EDX=
   ESI= EDI= EBP=0044b158 ESP=0044b130
   EIP=004006b9 EFL=0202 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
   ES =0010   00c09300 DPL=0 DS [-WA]
   CS =0008   00c09b00 DPL=0 CS32 [-RA]
   SS =0010   00c09300 DPL=0 DS [-WA]
   DS =0010   00c09300 DPL=0 DS [-WA]
   FS =0010   00c09300 DPL=0 DS [-WA]
   GS =0010 0044a1f0  00c09300 DPL=0 DS [-WA]
   LDT=   8200 DPL=0 LDT
   TR =0080 00406280  8b00 DPL=0 TSS32-busy
   GDT= 00406000 027f
   IDT=  0fff
   CR0=80010011 CR2= CR3=00453000 CR4=0010
   DR0= DR1= DR2=664fb17c DR3=
   DR6=0ff0 DR7=0400
   EFER=
   Code=87 e0 aa 40 00 83 c8 01 ba 00 00 00 00 b9 83 00 00 40 0f 30 <8b> 43 04 
83 c8 01 b9 82 00 00 40 0f 30 b8 01 00 00 00 b9 80 00 00 40 0f 30 83 c4 0c 0f b6
   qemu-system-i386: terminating on signal 15 from pid 12753 (timeout)
   FAIL hyperv_connections (timeout; duration=90s)

  * hyperv_stimer
   timeout -k 1s --foreground 90s /usr/bin/qemu-system-i386 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.P9Uky1nZUD -smp 2 
-cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # 
-initrd /tmp/tmp.uulivUIlYy
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   enabling apic
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 453000
   cr4 = 10
   enabling apic
   cpus = 2
   EAX=00458001 EBX=0040aa9c ECX=4083 EDX=
   ESI= EDI=0004 EBP=0044aab8 ESP=0044aaa0
   EIP=0040070c EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
   ES =0010   00c09300 DPL=0 DS [-WA]
   CS =0008   00c09b00 DPL=0 CS32 [-RA]
   SS =0010   00c09300 DPL=0 DS [-WA]
   DS =0010   00c09300 DPL=0 DS [-WA]
   FS =0010   00c09300 DPL=0 DS [-WA]
   GS =0010 00449b60  00c09300 DPL=0 DS [-WA]
   LDT=   8200 DPL=0 LDT
   TR =0080 00406280  8b00 DPL=0 TSS32-busy
   GDT= 00406000 027f
   IDT=  0fff
   CR0=80010011 CR2= CR3=00453000 CR4=0010
   DR0= DR1= DR2=4036d141 DR3=
   DR6=0ff0 DR7=0400
   EFER=
   Code=86 64 aa 40 00 83 c8 01 ba 00 00 00 00 b9 83 00 00 40 0f 30 01 00 00 00 
b9 80 00 00 40 0f 30 83 ec 04 6a 00 68 f1 00 00 00 6a 02 e8 ac 02 00 00 83
   EAX=00459001 EBX=0040aad8 ECX=4083 EDX=
   ESI=003c EDI=0004 EBP=0009ffbc ESP=0009ffa4
   EIP=0040070c EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
   ES =0010   00c09300 DPL=0 DS [-WA]
   CS =0008   00c09b00 DPL=0 CS32 [-RA]
   SS =0010   00c09300 DPL=0 DS [-WA]
   DS =0010   00c09300 DPL=0 DS [-WA]
   FS =0010   00c09300 DPL=0 DS [-WA]
   GS =0010 0009f000  00c09300 DPL=0 DS [-WA]
   LDT=

[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed with timeout

Issue observed in G/KVM, cycle sru-20210531.

** Tags added: 5.8 groovy sru-20210531

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

Title:
  apic test in kvm-unit-test failed with timeout

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure-edge source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-azure-edge source package in Bionic:
  New

Bug description:
  With Joshua's comment in bug 1719524: "Nested KVM can only be tried on
  instance sizes with nested Hypervisor support: Ev3 and Dv3.", although
  the instance name is E4v3 here but I can start a KVM on it.

  Test apic will timeout on it.

  Steps:
  1. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests; ./configure; make
  3. Run the apic test as root:
   
  # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline
  timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  FAIL: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  PASS: nmi-after-sti
  qemu-system-x86_64: terminating on signal 15 from pid 7246

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4
  ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14
  Uname: Linux 4.14.0-1004-azure-edge x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb  8 06:00:55 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-azure-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: linux-azure-edge
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-1009-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev 
sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1927272] Re: Some kernel selftests fail on linux-kvm

New observation, on H/KVM (cycle sru-20210531), LP
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1932549 :

03:28:51 DEBUG| [stdout] # selftests: net: devlink_port_split.py
03:28:51 DEBUG| [stdout] # Error sending command: devlink -j dev show
03:28:51 DEBUG| [stdout] #
03:28:51 DEBUG| [stdout] # Failed to connect to devlink Netlink
03:28:51 DEBUG| [stdout] #
03:28:51 DEBUG| [stdout] # Traceback (most recent call last):
03:28:51 DEBUG| [stdout] # File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
03:28:51 DEBUG| [stdout] # main()
03:28:51 DEBUG| [stdout] # File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 239, in main
03:28:51 DEBUG| [stdout] # assert stderr == ""
03:28:51 DEBUG| [stdout] # AssertionError
03:28:51 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # 
exit=1

This was also noticed in previous cycles, not a regression per-se.

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

Title:
  Some kernel selftests fail on linux-kvm

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

Bug description:
  This is a catch-all Launchpad report to list the kernel selftests failures in 
linux-kvm kernel.
  The comments will be used to reference and discuss about the failures, 
pointing to individual issues.

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

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

[Kernel-packages] [Bug 1932549] [NEW] seltests/net: devlink port split failing in 5.11 kernels (hirsute)

Public bug reported:

Got the following selftests/net failure in Hirsute, cycle sru-20210531 :

03:28:51 DEBUG| [stdout] # selftests: net: devlink_port_split.py
03:28:51 DEBUG| [stdout] # Error sending command: devlink -j dev show
03:28:51 DEBUG| [stdout] # 
03:28:51 DEBUG| [stdout] # Failed to connect to devlink Netlink
03:28:51 DEBUG| [stdout] # 
03:28:51 DEBUG| [stdout] # Traceback (most recent call last):
03:28:51 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
03:28:51 DEBUG| [stdout] # main()
03:28:51 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 239, in main
03:28:51 DEBUG| [stdout] # assert stderr == ""
03:28:51 DEBUG| [stdout] # AssertionError
03:28:51 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # 
exit=1


Noticed that it also failed in previous cycles (I'm not sure why I couldn't 
find a report...)

** Affects: ubuntu-kernel-tests
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed

** Affects: linux-kvm (Ubuntu)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed

** Affects: linux-kvm (Ubuntu Hirsute)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed


** Tags: 5.11 hirsute kvm linux-kvm sru-20210531 ubuntu-kernel-selftests

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

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

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

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

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

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

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

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

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

Title:
  seltests/net: devlink port split failing in 5.11 kernels (hirsute)

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Hirsute:
  Confirmed

Bug description:
  Got the following selftests/net failure in Hirsute, cycle sru-20210531
  :

  03:28:51 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  03:28:51 DEBUG| [stdout] # Error sending command: devlink -j dev show
  03:28:51 DEBUG| [stdout] # 
  03:28:51 DEBUG| [stdout] # Failed to connect to devlink Netlink
  03:28:51 DEBUG| [stdout] # 
  03:28:51 DEBUG| [stdout] # Traceback (most recent call last):
  03:28:51 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
  03:28:51 DEBUG| [stdout] # main()
  03:28:51 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 239, in main
  03:28:51 DEBUG| [stdout] # assert stderr == ""
  03:28:51 DEBUG| [stdout] # AssertionError
  03:28:51 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # 
exit=1

  
  Noticed that it also failed in previous cycles (I'm not sure why I couldn't 
find a report...)

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

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

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

Found on focal/aws-5.8 5.8.0-1036.38~20.04.1

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

Title:
  cpuset_hotplug from controllers in ubuntu_ltp failed

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

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

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

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

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

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

[Kernel-packages] [Bug 1860724] Re: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => 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/1860724

Title:
  QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices

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

Bug description:
  My QLogic direct-connect host can't seem to SANboot or see any SCSI-FC
  devices in general. I'm also not able to discover any NVMe devices.
  I'm running with Ubuntu 20.04 kernel-5.4.0-9-generic.

  There are the HBAs I'm running with:

  root@ICTM1610S01H4:~# cat /sys/class/fc_host/host*/symbolic_name
  QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k
  QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k
  QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k
  QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k

  lsscsi and multipath -ll don't seem to see my SCSI devices:

  root@ICTM1610S01H4:/opt/iop/linux/scratch# multipath -ll
  root@ICTM1610S01H4:/opt/iop/linux/scratch# lsscsi
  [0:0:0:0]cd/dvd  KVM  vmDisk-CD0.01  /dev/sr0
  [1:0:0:0]cd/dvd  HL-DT-ST DVDRAM GUD0N PF02  /dev/sr1
  [3:0:0:0]diskATA  ST1000NX0313 SNA3  /dev/sda

  It doesn't appear to be a configuration/hardware issue as installing
  Ubuntu 18.04 on the same exact server is able to SANboot and see my
  SCSI devices.

  root@ICTM1610S01H4:/opt/iop/linux/scratch# lsb_release -rd
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  root@ICTM1610S01H4:/opt/iop/linux/scratch# apt-cache policy 
linux-image-generic
  linux-image-generic:
    Installed: 5.4.0.9.11
    Candidate: 5.4.0.9.11
    Version table:
   *** 5.4.0.9.11 500
  500 http://repomirror-ict.eng.netapp.com/ubuntu focal/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-generic 5.4.0.9.11
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 23 11:32 seq
   crw-rw 1 root audio 116, 33 Jan 23 11:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 23 15:04:42 2020
  InstallationDate: Installed on 2020-01-23 (0 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200107)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: FUJITSU PRIMERGY RX2540 M4
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=9b9e6b1a-b8d9-4d9c-8782-36729d7f88a4 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2019
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.35.0 for D3384-A1x
  dmi.board.name: D3384-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3384-A13 WGS04 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2540M4R4
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.35.0forD3384-A1x:bd06/25/2019:svnFUJITSU:pnPRIMERGYRX2540M4:pvr:rvnFUJITSU:rnD3384-A1:rvrS26361-D3384-A13WGS04GS04:cvnFUJITSU:ct23:cvrRX2540M4R4:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2540 M4
  dmi.product.sku: S26361-K1567-Vxxx
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1901406] Re: Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8

2021-06-18 Thread Jan Rieke

I'm experiencing the same issue on a Thinkpad T590 (with a i7-8565U CPU
@ 1.80GHz).

With kernels up to 5.8.0-55, the CPU frequency rarely exceeds 1200 MHz,
most of the time it stays at 400 MHz, even in high-load situations. Even
regular web browsing brings the system to its limits, let alone
compiling code.

With kernel 5.4.0-74, everything works fine.

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

Title:
  Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 to 20.20 on my laptop, the machine became
  extremely slow. After a days work I noticed that it never got any
  faster, and the machine was a lot colder than usual. Running cat
  /proc/cpuinfo and sudo cpupower frequency-info I noticed that the CPU
  was locked to 400Mhz.

  After some googling I found reports of people having trouble with CPU
  frequency governors on kernel 5.8. I tried to add intel_pstate=active
  to grub, but that didn't help.

  My short term workaround is to choose the old 5.4 kernel from 20.04.
  With this kernel everything is snappy again! Currently it's running at
  3.2 Ghz with little load.

  CPU info from /proc/cpuinfo (with kernel 5.4):

  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 142
  model name: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
  stepping  : 12
  microcode : 0xd6
  cpu MHz   : 4551.153
  cache size: 8192 KB
  physical id   : 0
  siblings  : 8
  core id   : 0
  cpu cores : 4
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 22
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow 
vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms 
invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves 
dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear 
flush_l1d arch_capabilities
  bugs  : spectre_v1 spectre_v2 spec_store_bypass swapgs taa 
itlb_multihit srbds
  bogomips  : 4199.88
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 39 bits physical, 48 bits virtual
  power management:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hennikul   2402 F pulseaudio
   /dev/snd/pcmC0D0p:   hennikul   2402 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-09-02 (418 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20N2CTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic 
root=UUID=a36f1344-fd6c-40ef-a397-57f5a57594df ro intel_pstate=active quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy wayland-session
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (2 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/19/2020
  dmi.bios.release: 1.61
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2IET83W (1.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20N2CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2IET83W(1.61):bd01/19/2020:br1.61:efr1.16:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T490
  dmi.product.name: 20N2CTO1WW
  dmi.product.sku: LENOVO_MT_20N2_BU_Think_FM_ThinkPad T490
  dmi.product.version: ThinkPad T490
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list:

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

Found on focal/aws-5.8 5.8.0-1036.38~20.04.1

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1929504] Re: Add support for IO functions of AAEON devices

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

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

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

Title:
  Add support for IO functions of AAEON devices

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  In Progress

Bug description:
  [Impact]
  Require drivers to enable AAEON devices.

  [Fix]
  AAEON provides a series of patches to support its GPIO/LED/Watchdog/HWMON 
devices.
  https://www.spinics.net/lists/linux-gpio/msg61301.html

  [Test]
  Verified on AAEON platform.

  [Where problems could occur]
  No, they are new drivers, should not introduce any regressions.

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

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

[Kernel-packages] [Bug 1932065] Re: Upstream v5.9 introduced 'module' patches that removed exported symbols

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

** Changed in: linux (Ubuntu Bionic)
   Status: New => 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/1932065

Title:
  Upstream v5.9 introduced 'module' patches that removed exported
  symbols

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

Bug description:
  SRU Justification:

  [Impact]

  * The following patches removed an exported symbol that will cause
  potential disruption and breakage for customers

   modules: inherit TAINT_PROPRIETARY_MODULE
   modules: return licensing information from find_symbol
   modules: rename the licence field in struct symsearch to license
   modules: unexport __module_address
   modules: unexport __module_text_address
   modules: mark each_symbol_section static
   modules: mark find_symbol static
   modules: mark ref_module static

  [Fix]

  * Temporarily revert as SAUCE patches to allow customers time to make
  necessary changes to support eventual patch changes.

  [Test Plan]

  * none

  [Where problems could occur]

  * The new functionality provided by patches will be removed, since we
  aren't removing existing functionality the risk should be low.

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

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

[Kernel-packages] [Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed

2021-06-18 Thread Carl

If it helps anyone, I have suggested a workaround in this Ask Ubuntu
answer: https://askubuntu.com/a/263510/77322

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

Title:
  Kernel 4.9+ regression: Suspend - Freezing of tasks failed

Status in linux package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears
  and allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.

  In syslog I found the line:

  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"

  According to syslog

  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor

  are responsible.
  I tried disabling some of them, but it did not solve the problem.

  Update: I tested different Kernel versions in the last days. So far
  there were no issues with suspend/resume using Kernel 4.8 and 4.9. The
  problem is present in 4.10 and 4.11.

  Update 2: I just encountered this issue with Kernel 4.9.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B8CN31WW(V2.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paganini
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 3 11
  dmi.modalias: 
dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311:
  dmi.product.name: 80J8
  dmi.product.version: Lenovo Yoga 3 11
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1926030] Re: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49

2021-06-18 Thread Kleber Sacilotto de Souza

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

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

Title:
  IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Patch:
* media: rc: fix timeout handling after switch to microsecond durations
* media: rc: ite-cir: fix min_timeout calculation

  Were applied to Groovy with our stable update process (bug 1918516)

  User reported that IR Remote key press will be repeated for multiple times
  with these patches applied.

  Commit 528222d853f92 ("media: rc: harmonize infrared durations to
  microseconds") that needs to be fixed by these two does not exist in
  5.8 kernel. The patch author Matthias Reichl also state these are for
  5.10 and onward.

  [Fix]
  Revert these two patches for groovy.

  [Test]
  Test kernels for G-5.8 / F-5.8 can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/

  User Ted L confirmed that F-5.8 test kernel can fix the problem.

  [Where problems could occur]
  The chance to cause regression can be considered as low since the original 
patch that need to be fix by these two patches does not exist in 5.8 at all. 

  
  [Original Bug Report]
  I use an IR remote with the ir-keytable package.  Everything was working fine 
until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu 
20.04.2.  When any key is pressed on the remote, the key is repeated about 500 
times.  The kernel is now 5.8.0-50, and the problem persists.

  Other users on the MythTV mailing list are reporting the issue, and it
  appears that the problem is related to changes in the following files:

  drivers/media/rc/ir-mce_kbd-decoder.c
  drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c
  drivers/media/rc/serial_ir.c

  It has been reported that reverting the ir-mce_kbd-decoder.c and rc-
  main.c files to the older versions fixes the problem.

  /proc/version_signature > version.log:
  Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18

  lspci -vnvn:
  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:590f] (rev 06)
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host 
Bridge/DRAM Registers [1043:8694]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  ir-keytable -V:
  IR keytable control version 1.18.0

  lsb_release -rd:
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ted1020 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-09-19 (217 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.

   enp0s31f6  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=529cae8e-19cd-4732-80d5-b3dca123afc6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.11
  RfKill:

  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd mythtv plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3405
  dmi.board.asset.tag: Default string
  dmi.board.name: H110T
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3405:bd07/05/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110T:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU

[Kernel-packages] [Bug 1931731] Re: pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63

2021-06-18 Thread Kleber Sacilotto de Souza

Confirmed that the pmtu.sh testcase completes successfully with
groovy/linux 5.8.0-57.64.

** Tags added: verification-done-groovy

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

Title:
  pmtu.sh from selftests.net in linux ADT test failure with
  linux/5.8.0-56.63

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

Bug description:
  [Impact]
  Upstream commit 6628ddfec7580882f11fdc5c194a8ea781fdadfa ("net: geneve: check 
skb is large enough for IPv4/IPv6 header"), applied to groovy/linux 5.8.0-56.63 
via upstream stable update (bug 1929132) introduced a regression caught by 
kernel selftests, pmtu.sh from net testcase:

  02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions   
 [FAIL]
  02:56:48 DEBUG| [stdout] #   PMTU exception wasn't created after exceeding 
link layer MTU on geneve interface
  02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop 
objects  [FAIL]
  02:56:49 DEBUG| [stdout] # PMTU exception wasn't created after exceeding link 
layer MTU on geneve interface

  [Fix]
  The issue is fixed by d13f048dd40e8577260cd43faea8ec9b77520197 ("net: geneve: 
modify IP header check in geneve6_xmit_skb and geneve_xmit_skb"), which is 
already applied for the next SRU cycle as part of upstream stable update (bug 
1930766).

  [Tests]
  I have applied the fix on top of 5.8.0-56.63 and ran pmtu.sh and the whole 
selftests.net suite. The testcase is now completed successfully and no other 
regression was found.

  [Where problems could occur]
  The fix could be a partial fix not covering all corner cases, this could lead 
to other failures with geneve tunnels.

  [Original Description]
  This is a scripted bug report about ADT failures while running linux tests 
for linux/5.8.0-56.63 on groovy. Whether this is caused by the dep8 tests of 
the tested source or the kernel has yet to be determined.

  Looks to be isolated to Groovy and appearing on all arches.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/amd64/l/linux/20210610_035450_9c9b9@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/l/linux/20210611_103429_5c4be@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/ppc64el/l/linux/20210611_013418_76b18@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/s390x/l/linux/20210610_030630_fb359@/log.gz

  02:56:31 DEBUG| [stdout] # selftests: net: pmtu.sh
  02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions
 [ OK ]
  02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects  
 [ OK ]
  02:56:31 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions
 [ OK ]
  02:56:32 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects  
 [ OK ]
  02:56:33 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions
 [ OK ]
  02:56:34 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions - nexthop 
objects   [ OK ]
  02:56:35 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions
 [ OK ]
  02:56:36 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions - nexthop 
objects   [ OK ]
  02:56:38 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions
 [ OK ]
  02:56:39 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions - nexthop 
objects   [ OK ]
  02:56:40 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions
 [ OK ]
  02:56:41 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions - nexthop 
objects   [ OK ]
  02:56:43 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions   
 [ OK ]
  02:56:44 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions - nexthop 
objects  [ OK ]
  02:56:45 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions   
 [ OK ]
  02:56:46 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions - nexthop 
objects  [ OK ]
  02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions   
 [FAIL]
  02:56:48 DEBUG| [stdout] #   PMTU exception wasn't created after exceeding 
link layer MTU on geneve interface
  02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop 
objects  [FAIL]
  02:56:49 DEBUG| [stdout] #   PMTU exception wasn't created after exceeding 
link layer MTU on geneve interface
  02:56:50 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions   
 [ OK ]
  02:56:51 DEBUG| [stdout] # TEST:

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

Sent fix to upstream (LTP):
https://lists.linux.it/pipermail/ltp/2021-June/023296.html

** Changed in: ubuntu-kernel-tests
   Status: Triaged => In Progress

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1912789] Re: Add support for selective build of special drivers

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

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

Title:
  Add support for selective build of special drivers

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

Bug description:
  [SRU Justification]

  = Impact =

  We want to add some driver code which exists in the primary kernel
  source but will not get included unless specifically asked for. As
  long as there are no drivers using this, there is no user-visible
  change.

  = Impact =

  This will be done by adding a new config option which gets turned on
  via build setup rules. The default will be off.

  = Testcase =

  As long as there are no consumers changes can only be seen by
  inspecting the build logs (if even that).

  = Regression Potential =

  This prepares for future consumers. At this stage either the build
  will fail completely or pass and in that case the produced kernel
  binaries are the same as they were before.

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

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

[Kernel-packages] [Bug 1932065] Re: Upstream v5.9 introduced 'module' patches that removed exported symbols

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

** Changed in: linux (Ubuntu Groovy)
   Status: New => 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/1932065

Title:
  Upstream v5.9 introduced 'module' patches that removed exported
  symbols

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

Bug description:
  SRU Justification:

  [Impact]

  * The following patches removed an exported symbol that will cause
  potential disruption and breakage for customers

   modules: inherit TAINT_PROPRIETARY_MODULE
   modules: return licensing information from find_symbol
   modules: rename the licence field in struct symsearch to license
   modules: unexport __module_address
   modules: unexport __module_text_address
   modules: mark each_symbol_section static
   modules: mark find_symbol static
   modules: mark ref_module static

  [Fix]

  * Temporarily revert as SAUCE patches to allow customers time to make
  necessary changes to support eventual patch changes.

  [Test Plan]

  * none

  [Where problems could occur]

  * The new functionality provided by patches will be removed, since we
  aren't removing existing functionality the risk should be low.

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

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

[Kernel-packages] [Bug 1932081] Re: Disable hv-kvp-daemon.service on certain instance types

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => 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/1932081

Title:
  Disable hv-kvp-daemon.service on certain instance types

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  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]

   * Disable hv-kvp-daemon.service on certain instance types. As
  requested for some azure instance types, hv-kvp-daemon is prohibited
  from starting, and currently it takes a long time to come up and fail.
  Configure to disable the service on those instances. At the moment, we
  can key off kernel command line to detect those.

  [Test Plan]

   * Boot preview image in azure
   * Check that hv-kvp-daemon.service is not running

  [Where problems could occur]

   * The conditions/detection could have been more specific as to when
  the daemon is pointless to run. Thus key-off kernel commandline is
  good enough for now, but may require changes in the future.

  [Other Info]

  @ Kernel team, also see https://trello.com/c/JbomiFOe

  https://lists.ubuntu.com/archives/kernel-team/2021-June/121384.html

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

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

[Kernel-packages] [Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work

2021-06-18 Thread Anton Sudak

Here what I was able to extract with the latest kernel:

Fn+F4
[   44.615947] lenovo_raw_event data 0x1:0x0:0x0
[   44.615950] report id/type/app: 1/0/786433 maxfield: 1
[   44.615952] field 0 physical: 0x00 logical 0x00 app 0x0c0001 flags 
0x00, max usage 573
[   44.615953] usage 0 hid: 0x0c index 0x00 code 0x00 type 0x0


Fn+F10
[   51.971153] lenovo_raw_event data 0x1:0x0:0x0
[   51.971183] report id/type/app: 1/0/786433 maxfield: 1
[   51.971185] field 0 physical: 0x00 logical 0x00 app 0x0c0001 flags 
0x00, max usage 573
[   51.971188] usage 0 hid: 0x0c index 0x00 code 0x00 type 0x0

After pressing fn+Fx keys keyboard and mouse stopped to work and last
line in logs above was printed forever.

** Attachment added: "dmesg with v6"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+attachment/5505510/+files/fnF10dmesg

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

Title:
  Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn
  keys don't work. First one is Mute mic (Fn+F4), second one is Scissors
  (Fn+F10, probably hotkey for Windows Snipping Tool for selective
  screenshot).gnome-control-panel, xev and evtest doesn't react on
  pressing these buttons.

  Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 
"%02X\n"' :
  For Mute key
  00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00

  For Scissors
  00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-generic 5.11.0.16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asudak 2085 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Thu May  6 22:36:50 2021
  InstallationDate: Installed on 2021-04-13 (23 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera
   Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
   Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard 
and Mouse Combo
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO F0FA0066UA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago)
  dmi.bios.date: 03/31/2021
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O4VKT32A
  dmi.board.asset.tag: INVALID
  dmi.board.name: 371F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN 3424143288435
  dmi.chassis.type: 13
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1:
  dmi.product.family: IdeaCentre AIO 5 27IMB05
  dmi.product.name: F0FA0066UA
  dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05
  dmi.product.version: IdeaCentre AIO 5 27IMB05
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1932081] Re: Disable hv-kvp-daemon.service on certain instance types

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

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

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

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => 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/1932081

Title:
  Disable hv-kvp-daemon.service on certain instance types

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

   * Disable hv-kvp-daemon.service on certain instance types. As
  requested for some azure instance types, hv-kvp-daemon is prohibited
  from starting, and currently it takes a long time to come up and fail.
  Configure to disable the service on those instances. At the moment, we
  can key off kernel command line to detect those.

  [Test Plan]

   * Boot preview image in azure
   * Check that hv-kvp-daemon.service is not running

  [Where problems could occur]

   * The conditions/detection could have been more specific as to when
  the daemon is pointless to run. Thus key-off kernel commandline is
  good enough for now, but may require changes in the future.

  [Other Info]

  @ Kernel team, also see https://trello.com/c/JbomiFOe

  https://lists.ubuntu.com/archives/kernel-team/2021-June/121384.html

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

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

[Kernel-packages] [Bug 1932528] Re: Touchpad stopped working after using as a tablet

2021-06-18 Thread Chris Guiver

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

I see no evidence of a system upgrade (from 20.10 to say 21.04) having
taken place... the installation media was 21.04 & system is still
currently 21.04, thus package was changed from `ubuntu-release-upgrader`
to the `linux` kernel.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  Touchpad stopped working after using as a tablet

Status in linux package in Ubuntu:
  New

Bug description:
  Hi Everyone.

  So my touchpad has stopped working now out of the blue. I have a
  Lenovo Yoga 3 Pro 1370, and I installed Ubuntu yesterday.

  It was working perfectly, but it has stopped working as soon as I got
  into tablet mode.

  This laptop has the ability to fold its keyboard, so I did that and
  turn the laptop in 90 degrees (which the screen also turned due to the
  gyroscope). When we do this, its normal that the cursor disapears so
  we can you use only the touchscreen as a tablet, however when I turned
  back to a laptop the touchpad hasn't worked ag=0ain.

  I have rebooted the system, but still not signs of it.

  I have executed "cat /proc/bus/input/devices", but didn't find
  anything related to the touchpad, as the result shows below, so I
  think it's a kernel issue, right? Any thought how I could fix this?

  Thank you!

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Ideapad extra buttons"
  P: Phys=ideapad/input0
  S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input6
  U: Uniq=
  H: Handlers=rfkill kbd event5
  B: PROP=0
  B: EV=13
  B: KEY=81000800100c03 4430 0 2
  B: MSC=10

  I: Bus=0018 Vendor=03eb Product=8a10 Version=0100
  N: Name="ATML1000:00 03EB:8A10"
  P: Phys=i2c-ATML1000:00
  S: 
Sysfs=/devices/pci:00/INT3433:00/i2c-1/i2c-ATML1000:00/0018:03EB:8A10.0001/input/input8
  U: Uniq=
  H: Handlers=mouse0 event4
  B: PROP=2
  B: EV=1b
  B: KEY=400 0 0 0 0 0
  B: ABS=2608003
  B: MSC=20

  I: Bus=0003 Vendor=5986 Product=0535 Version=3653
  N: Name="Lenovo EasyCamera: Lenovo EasyC"
  P: Phys=usb-:00:14.0-7/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input9
  U: Uniq=
  H: Handlers=kbd event6
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input10
  U: Uniq=
  H: Handlers=event7
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input11
  U: Uniq=
  H: Handlers=event8
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
  U: Uniq=
  H: Handlers=kbd event9
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel HDMI HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input13
  U: Uniq=
  H: Handlers=event10
  B: PROP=0

[Kernel-packages] [Bug 1932528] [NEW] Touchpad stopped working after using as a tablet

You have been subscribed to a public bug:

Hi Everyone.

So my touchpad has stopped working now out of the blue. I have a Lenovo
Yoga 3 Pro 1370, and I installed Ubuntu yesterday.

It was working perfectly, but it has stopped working as soon as I got
into tablet mode.

This laptop has the ability to fold its keyboard, so I did that and turn
the laptop in 90 degrees (which the screen also turned due to the
gyroscope). When we do this, its normal that the cursor disapears so we
can you use only the touchscreen as a tablet, however when I turned back
to a laptop the touchpad hasn't worked ag=0ain.

I have rebooted the system, but still not signs of it.

I have executed "cat /proc/bus/input/devices", but didn't find anything
related to the touchpad, as the result shows below, so I think it's a
kernel issue, right? Any thought how I could fix this?

Thank you!

I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds
B: PROP=0
B: EV=120013
B: KEY=40200 3803078f800d001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor= Product= Version=
N: Name="Ideapad extra buttons"
P: Phys=ideapad/input0
S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input6
U: Uniq=
H: Handlers=rfkill kbd event5
B: PROP=0
B: EV=13
B: KEY=81000800100c03 4430 0 2
B: MSC=10

I: Bus=0018 Vendor=03eb Product=8a10 Version=0100
N: Name="ATML1000:00 03EB:8A10"
P: Phys=i2c-ATML1000:00
S: 
Sysfs=/devices/pci:00/INT3433:00/i2c-1/i2c-ATML1000:00/0018:03EB:8A10.0001/input/input8
U: Uniq=
H: Handlers=mouse0 event4
B: PROP=2
B: EV=1b
B: KEY=400 0 0 0 0 0
B: ABS=2608003
B: MSC=20

I: Bus=0003 Vendor=5986 Product=0535 Version=3653
N: Name="Lenovo EasyCamera: Lenovo EasyC"
P: Phys=usb-:00:14.0-7/button
S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input9
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input10
U: Uniq=
H: Handlers=event7
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input11
U: Uniq=
H: Handlers=event8
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0019 Vendor= Product=0006 Version=
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
U: Uniq=
H: Handlers=kbd event9
B: PROP=0
B: EV=3
B: KEY=3e000b 0 0 0

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel HDMI HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input13
U: Uniq=
H: Handlers=event10
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel HDMI HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input14
U: Uniq=
H: Handlers=event11
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel HDMI HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input15
U: Uniq=
H: Handlers=event12
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel HDMI HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input16
U: Uniq=
H: Handlers=event13
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel HDMI HDMI/DP,pcm=10"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input17
U: Uniq=
H: Handlers=event14
B: PROP=0
B: EV=21
B: SW=140

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubuntu-release-upgrader-core 1:21.04.13
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 18 08:09:23 2021
InstallationDate: Installed on 2021-06-18 (0 days ago)

[Kernel-packages] [Bug 1932532] Re: package linux-firmware 1.187.14 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

2021-06-18 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

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

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

Title:
  package linux-firmware 1.187.14 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  package linux-firmware 1.187.14 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

  Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.14
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1140 F pulseaudio
asif   1878 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Jun 18 18:01:06 2021
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-05-01 (48 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP Pavilion Notebook
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=95e29b53-9813-4d1c-8bae-a0f1615606ae ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.12
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.187.14 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.release: 15.55
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.55
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 83.18
  dmi.modalias: 
dmi:bvnInsyde:bvrF.55:bd07/01/2020:br15.55:efr83.18:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.18:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.sku: Z1D72PA#UUF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1932532] [NEW] package linux-firmware 1.187.14 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

2021-06-18 Thread Asif Ahmed

Public bug reported:

package linux-firmware 1.187.14 failed to install/upgrade: installed
linux-firmware package post-installation script subprocess returned
error exit status 1

Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.14
ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-55-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1140 F pulseaudio
  asif   1878 F pulseaudio
CasperMD5CheckResult: skip
Date: Fri Jun 18 18:01:06 2021
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2021-05-01 (48 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: HP HP Pavilion Notebook
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=95e29b53-9813-4d1c-8bae-a0f1615606ae ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.12
SourcePackage: linux-firmware
Title: package linux-firmware 1.187.14 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.release: 15.55
dmi.bios.vendor: Insyde
dmi.bios.version: F.55
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8216
dmi.board.vendor: HP
dmi.board.version: 83.18
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 83.18
dmi.modalias: 
dmi:bvnInsyde:bvrF.55:bd07/01/2020:br15.55:efr83.18:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.18:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion Notebook
dmi.product.sku: Z1D72PA#UUF
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-package focal

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

Title:
  package linux-firmware 1.187.14 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  package linux-firmware 1.187.14 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

  Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.14
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1140 F pulseaudio
asif   1878 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Jun 18 18:01:06 2021
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-05-01 (48 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP Pavilion Notebook
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=95e29b53-9813-4d1c-8bae-a0f1615606ae ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.12
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.187.14 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.release: 15.55
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.55
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor:

[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15

** Description changed:

  [Impact]
- Test case cfs_bandwidth01 in LTP sched test suite is a reproducer for the 
following commits:
-   * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning
-   * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more
-   * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list
-   * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path
-   * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair()
+ Test case cfs_bandwidth01 in LTP sched test suite is a reproducer of the CFS 
unthrottle_cfs_rq() issue:
  
- This test will trigger warning on our 4.15 kernel:
+ This test triggers a warning on our 4.15 kernel:
   LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5)
   [ cut here ]
   rq->tmp_alone_branch != >leaf_cfs_rq_list
   WARNING: CPU: 0 PID: 0 at 
/build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 
unthrottle_cfs_rq+0x16f/0x200
   Modules linked in: input_leds joydev serio_raw mac_hid qemu_fw_cfg kvm_intel 
kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl 
lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm psmouse virtio_blk pata_acpi floppy 
virtio_net i2c_piix4
   CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic #148-Ubuntu
   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 
04/01/2014
   RIP: 0010:unthrottle_cfs_rq+0x16f/0x200
   RSP: 0018:989ebfc03e80 EFLAGS: 00010082
   RAX:  RBX: 989eb4c6ac00 RCX: 
   RDX: 0005 RSI: acb63c4d RDI: 0046
   RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: acb63c20
   R10:  R11: 0001 R12: 989eb57fe400
   R13: 989ebfc21900 R14: 0001 R15: 0001
   FS: () GS:989ebfc0() knlGS:
   CS: 0010 DS:  ES:  CR0: 80050033
   CR2: 55593258d618 CR3: 7a044000 CR4: 06f0
   DR0:  DR1:  DR2: 
   DR3:  DR6: fffe0ff0 DR7: 0400
   Call Trace:
   
   distribute_cfs_runtime+0xc3/0x110
   sched_cfs_period_timer+0xff/0x220
   ? sched_cfs_slack_timer+0xd0/0xd0
   __hrtimer_run_queues+0xdf/0x230
   hrtimer_interrupt+0xa0/0x1d0
   smp_apic_timer_interrupt+0x6f/0x140
   apic_timer_interrupt+0x90/0xa0
   
   RIP: 0010:native_safe_halt+0x12/0x20
   RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: ff11
   RAX: abbc9280 RBX:  RCX: 
   RDX:  RSI:  RDI: 
   RBP: ac603e28 R08: 00af39850067 R09: 989e73749d00
   R10:  R11: 7fff R12: 
   R13:  R14:  R15: 
   ? __sched_text_end+0x1/0x1
   default_idle+0x20/0x100
   arch_cpu_idle+0x15/0x20
   default_idle_call+0x23/0x30
   do_idle+0x172/0x1f0
   cpu_startup_entry+0x73/0x80
   rest_init+0xae/0xb0
   start_kernel+0x4dc/0x500
   x86_64_start_reservations+0x24/0x26
   x86_64_start_kernel+0x74/0x77
   secondary_startup_64+0xa5/0xb0
   Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 00 75 5f 31 
db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 48 85 db 74 
43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00
   ---[ end trace b6b9a70bc2945c0c ]---
  
  [Fix]
-   * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning
-   * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more
-   * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list
-   * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path
-   * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair()
+   * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning
+   * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more
+   * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list
+   * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path
+   * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair()
  
  Backport needed for Bionic since we're missing some new variables introduced 
in the following commits and their corresponding fixes:
-   * 9f68395333ad7f sched/pelt: Add a new runnable average signal
-   * 6212437f0f6043 sched/fair: Fix runnable_avg for throttled cfs
-   * 43e9f7f231e40e sched/fair: Start tracking SCHED_IDLE tasks count in cfs_rq
+   * 9f68395333ad7f sched/pelt: Add a new runnable average signal
+   * 6212437f0f6043 sched/fair: Fix runnable_avg

[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15

** Description changed:

  [Impact]
  Test case cfs_bandwidth01 in LTP sched test suite is a reproducer for the 
following commits:
    * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning
    * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more
    * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list
    * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path
    * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair()
  
  This test will trigger warning on our 4.15 kernel:
-  LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5)
-  [ cut here ]
-  rq->tmp_alone_branch != >leaf_cfs_rq_list
-  WARNING: CPU: 0 PID: 0 at 
/build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 
unthrottle_cfs_rq+0x16f/0x200
-  Modules linked in: input_leds joydev serio_raw mac_hid qemu_fw_cfg kvm_intel 
kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl 
lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm psmouse virtio_blk pata_acpi floppy 
virtio_net i2c_piix4
-  CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic #148-Ubuntu
-  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 
04/01/2014
-  RIP: 0010:unthrottle_cfs_rq+0x16f/0x200
-  RSP: 0018:989ebfc03e80 EFLAGS: 00010082
-  RAX:  RBX: 989eb4c6ac00 RCX: 
-  RDX: 0005 RSI: acb63c4d RDI: 0046
-  RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: acb63c20
-  R10:  R11: 0001 R12: 989eb57fe400
-  R13: 989ebfc21900 R14: 0001 R15: 0001
-  FS: () GS:989ebfc0() knlGS:
-  CS: 0010 DS:  ES:  CR0: 80050033
-  CR2: 55593258d618 CR3: 7a044000 CR4: 06f0
-  DR0:  DR1:  DR2: 
-  DR3:  DR6: fffe0ff0 DR7: 0400
-  Call Trace:
-  
-  distribute_cfs_runtime+0xc3/0x110
-  sched_cfs_period_timer+0xff/0x220
-  ? sched_cfs_slack_timer+0xd0/0xd0
-  __hrtimer_run_queues+0xdf/0x230
-  hrtimer_interrupt+0xa0/0x1d0
-  smp_apic_timer_interrupt+0x6f/0x140
-  apic_timer_interrupt+0x90/0xa0
-  
-  RIP: 0010:native_safe_halt+0x12/0x20
-  RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: ff11
-  RAX: abbc9280 RBX:  RCX: 
-  RDX:  RSI:  RDI: 
-  RBP: ac603e28 R08: 00af39850067 R09: 989e73749d00
-  R10:  R11: 7fff R12: 
-  R13:  R14:  R15: 
-  ? __sched_text_end+0x1/0x1
-  default_idle+0x20/0x100
-  arch_cpu_idle+0x15/0x20
-  default_idle_call+0x23/0x30
-  do_idle+0x172/0x1f0
-  cpu_startup_entry+0x73/0x80
-  rest_init+0xae/0xb0
-  start_kernel+0x4dc/0x500
-  x86_64_start_reservations+0x24/0x26
-  x86_64_start_kernel+0x74/0x77
-  secondary_startup_64+0xa5/0xb0
-  Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 00 75 5f 31 
db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 48 85 db 74 
43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00
-  ---[ end trace b6b9a70bc2945c0c ]---
- 
+  LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5)
+  [ cut here ]
+  rq->tmp_alone_branch != >leaf_cfs_rq_list
+  WARNING: CPU: 0 PID: 0 at 
/build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 
unthrottle_cfs_rq+0x16f/0x200
+  Modules linked in: input_leds joydev serio_raw mac_hid qemu_fw_cfg kvm_intel 
kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl 
lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm psmouse virtio_blk pata_acpi floppy 
virtio_net i2c_piix4
+  CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic #148-Ubuntu
+  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 
04/01/2014
+  RIP: 0010:unthrottle_cfs_rq+0x16f/0x200
+  RSP: 0018:989ebfc03e80 EFLAGS: 00010082
+  RAX:  RBX: 989eb4c6ac00 RCX: 
+  RDX: 0005 RSI: acb63c4d RDI: 0046
+  RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: acb63c20
+  R10:  R11: 0001 R12: 989eb57fe400
+  R13:

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.4.0.1045.54)

2021-06-18 Thread Ubuntu SRU Bot

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

lime-forensics/1.9-1ubuntu0.2 (amd64)
openafs/1.8.4~pre1-1ubuntu2.1 (amd64)
nvidia-graphics-drivers-418-server/418.197.02-0ubuntu0.20.04.1 (amd64)
gost-crypto/0.3.2-2ubuntu0.2 (amd64)
bbswitch/0.8-8ubuntu0.20.04.1 (amd64)
sl-modem/2.9.11~20110321-16ubuntu1 (amd64)
ddcci-driver-linux/0.3.3-1 (amd64)
dpdk/19.11.7-0ubuntu0.20.04.1 (amd64)
sysdig/0.26.4-1ubuntu0.3 (amd64)
openrazer/2.5.0+dfsg-1ubuntu2 (amd64)
tp-smapi/0.43-1 (amd64)
acpi-call/1.1.0-5ubuntu0.2 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 (amd64)
nvidia-graphics-drivers-460/460.80-0ubuntu0.20.04.2 (amd64)
nat-rtsp/0.7+4.18-0.1ubuntu1 (amd64)
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 (amd64)
nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.20.04.2 (amd64)
iptables-netflow/2.4-2ubuntu0.4 (amd64)
virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 (amd64)
jool/4.0.7-1 (amd64)
oss4/4.2-build2010-5ubuntu6~20.04.2 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 (amd64)
dm-writeboost/2.2.9-1ubuntu1.2 (amd64)
nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.04.1 (amd64)
r8168/8.048.00-1ubuntu0.20.04.2 (amd64)
langford/0.0.20130228-6build1 (amd64)
virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (amd64)
nvidia-graphics-drivers-390/390.143-0ubuntu0.20.04.1 (amd64)
lttng-modules/2.12.2-1ubuntu1~20.04.2 (amd64)
rtl8821ce/5.5.2.1-0ubuntu4~20.04.3 (amd64)
bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 (amd64)
west-chamber/20100405+svn2007.r124-12ubuntu0.3~20.04.1 (amd64)
v4l2loopback/0.12.3-1ubuntu0.4 (amd64)
nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64)
adv-17v35x/5.0.3.0-2 (amd64)
xtables-addons/3.9-1ubuntu0.2~20.04.1 (amd64)
ndiswrapper/1.60-8ubuntu3 (amd64)
broadcom-sta/6.30.223.271-12 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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

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

[Kernel-packages] [Bug 1931841] Re: generic arm64 kernel can not boot initrdless and there is no -kvm kernel

2021-06-18 Thread Thomas Bechtold

** Summary changed:

- generic arm64 kernel can not boot initrdless
+ generic arm64 kernel can not boot initrdless and there is no -kvm kernel

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

Title:
  generic arm64 kernel can not boot initrdless and there is no -kvm
  kernel

Status in linux package in Ubuntu:
  New

Bug description:
  The CPC team wants to build minimal arm64 images. Those images should boot 
initrdless (similar to the amd64 images where the -kvm kernel is used).
  But booting an initrdless image (build with livecd-rootfs) does fail with:

  $ sudo qemu-system-aarch64 -m 2G -M virt -cpu max   -bios /usr/share
  /qemu-efi-aarch64/QEMU_EFI.fd   -drive
  if=none,format=qcow2,file=livecd.ubuntu-cpc.img,id=hd0 -device virtio-
  blk-device,drive=hd0   -device e1000,netdev=net0 -netdev
  user,id=net0,hostfwd=tcp:127.0.0.1:-:22 -nographic

  [snipped]

  [0.945928] VFS: Cannot open root device 
"PARTUUID=15058d73-bec1-4c7d-9cd7-f0f73f3ec694" or unknown-block(0,0): error -6
  [0.946117] Please append a correct "root=" boot option; here are the 
available partitions:
  [0.947611] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [0.948139] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-74-generic 
#83-Ubuntu
  [0.948237] Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015
  [0.948453] Call trace:
  [0.948736]  dump_backtrace+0x0/0x190
  [0.948864]  show_stack+0x28/0x38
  [0.948918]  dump_stack+0xb4/0x10c
  [0.948974]  panic+0x150/0x364
  [0.949027]  mount_block_root+0x248/0x304
  [0.949090]  mount_root+0x48/0x50
  [0.949145]  prepare_namespace+0x13c/0x1bc
  [0.949205]  kernel_init_freeable+0x270/0x2c4
  [0.949274]  kernel_init+0x1c/0x114
  [0.949336]  ret_from_fork+0x10/0x18
  [0.949913] Kernel Offset: disabled
  [0.950175] CPU features: 0x0952,20e0a230
  [0.950251] Memory Limit: none
  [0.950595] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0) ]---

  The reason is, that the the virtio drivers are modules
  (CONFIG_VIRTIO_BLK=m) but for initrdless boot, they need to be
  compiled into the kernel.

  
  Expected behavior:
  Booting an arm64 image without an initrd does work in a virtualized 
environment similar to an amd64 image (that uses the -kvm kernel)

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

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

[Kernel-packages] [Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work

2021-06-18 Thread Chris Chiu

It's a pity that there's nothing distinguishable for them. I'll need
more information. Please help try
https://people.canonical.com/~mschiu77/lp1927545/v6/. Thanks

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

Title:
  Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn
  keys don't work. First one is Mute mic (Fn+F4), second one is Scissors
  (Fn+F10, probably hotkey for Windows Snipping Tool for selective
  screenshot).gnome-control-panel, xev and evtest doesn't react on
  pressing these buttons.

  Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 
"%02X\n"' :
  For Mute key
  00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00

  For Scissors
  00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-generic 5.11.0.16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asudak 2085 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Thu May  6 22:36:50 2021
  InstallationDate: Installed on 2021-04-13 (23 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera
   Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
   Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard 
and Mouse Combo
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO F0FA0066UA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago)
  dmi.bios.date: 03/31/2021
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O4VKT32A
  dmi.board.asset.tag: INVALID
  dmi.board.name: 371F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN 3424143288435
  dmi.chassis.type: 13
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1:
  dmi.product.family: IdeaCentre AIO 5 27IMB05
  dmi.product.name: F0FA0066UA
  dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05
  dmi.product.version: IdeaCentre AIO 5 27IMB05
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15

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

** Description changed:

  [Impact]
  Test case cfs_bandwidth01 in LTP sched test suite is a reproducer for the 
following commits:
    * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning
    * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more
    * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list
    * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path
    * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair()
  
  This test will trigger warning on our 4.15 kernel:
- [  694.761774] LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5)
- [  695.801637] [ cut here ]
- [  695.801640] rq->tmp_alone_branch != >leaf_cfs_rq_list
- [  695.801694] WARNING: CPU: 0 PID: 0 at 
/build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 
unthrottle_cfs_rq+0x16f/0x200
- [  695.801695] Modules linked in: input_leds joydev serio_raw mac_hid 
qemu_fw_cfg kvm_intel kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm 
iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse 
virtio_blk pata_acpi floppy virtio_net i2c_piix4
- [  695.801726] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic 
#148-Ubuntu
- [  695.801727] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
- [  695.801729] RIP: 0010:unthrottle_cfs_rq+0x16f/0x200
- [  695.801730] RSP: 0018:989ebfc03e80 EFLAGS: 00010082
- [  695.801732] RAX:  RBX: 989eb4c6ac00 RCX: 

- [  695.801732] RDX: 0005 RSI: acb63c4d RDI: 
0046
- [  695.801734] RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: 
acb63c20
- [  695.801734] R10:  R11: 0001 R12: 
989eb57fe400
- [  695.801735] R13: 989ebfc21900 R14: 0001 R15: 
0001
- [  695.801737] FS:  () GS:989ebfc0() 
knlGS:
- [  695.801738] CS:  0010 DS:  ES:  CR0: 80050033
- [  695.801739] CR2: 55593258d618 CR3: 7a044000 CR4: 
06f0
- [  695.801742] DR0:  DR1:  DR2: 

- [  695.801743] DR3:  DR6: fffe0ff0 DR7: 
0400
- [  695.801744] Call Trace:
- [  695.801755]  
- [  695.801765]  distribute_cfs_runtime+0xc3/0x110
- [  695.801767]  sched_cfs_period_timer+0xff/0x220
- [  695.801768]  ? sched_cfs_slack_timer+0xd0/0xd0
- [  695.801775]  __hrtimer_run_queues+0xdf/0x230
- [  695.801777]  hrtimer_interrupt+0xa0/0x1d0
- [  695.801786]  smp_apic_timer_interrupt+0x6f/0x140
- [  695.801789]  apic_timer_interrupt+0x90/0xa0
- [  695.801789]  
- [  695.801791] RIP: 0010:native_safe_halt+0x12/0x20
- [  695.801792] RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: 
ff11
- [  695.801793] RAX: abbc9280 RBX:  RCX: 

- [  695.801794] RDX:  RSI:  RDI: 

- [  695.801795] RBP: ac603e28 R08: 00af39850067 R09: 
989e73749d00
- [  695.801796] R10:  R11: 7fff R12: 

- [  695.801796] R13:  R14:  R15: 

- [  695.801801]  ? __sched_text_end+0x1/0x1
- [  695.801804]  default_idle+0x20/0x100
- [  695.801813]  arch_cpu_idle+0x15/0x20
- [  695.801814]  default_idle_call+0x23/0x30
- [  695.801821]  do_idle+0x172/0x1f0
- [  695.801823]  cpu_startup_entry+0x73/0x80
- [  695.801825]  rest_init+0xae/0xb0
- [  695.801843]  start_kernel+0x4dc/0x500
- [  695.801845]  x86_64_start_reservations+0x24/0x26
- [  695.801847]  x86_64_start_kernel+0x74/0x77
- [  695.801851]  secondary_startup_64+0xa5/0xb0
- [  695.801852] Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 
00 75 5f 31 db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 
48 85 db 74 43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00
- [  695.801875] ---[ end trace b6b9a70bc2945c0c ]---
+  LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5)
+  [ cut here ]
+  rq->tmp_alone_branch != >leaf_cfs_rq_list
+  WARNING: CPU: 0 PID: 0 at 
/build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 
unthrottle_cfs_rq+0x16f/0x200
+  Modules linked in: input_leds joydev serio_raw mac_hid qemu_fw_cfg kvm_intel 
kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl 
lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456

[Kernel-packages] [Bug 1932303] Re: Dell XPS 17 9700 wifi

2021-06-18 Thread Jeremy Miller

What I'd like to see is the sound fixes from 5.11.0-20-generic kernel
make it into the OEM kernel so that both wifi and sound work on the Dell
XPS 17 9700.

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

** No longer affects: linux (Ubuntu)

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

Title:
  Dell XPS 17 9700 wifi

Status in Ubuntu:
  New
Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  Release:
  devops@devops-XPS-17-9700:~$ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  devops@devops-XPS-17-9700:~$ 

  Problem:
  Cannot get both wifi and sound working on a Dell XPS 17 9700 (i9 processor) 
at the same time.

  With the 5.10.0-1029-oem kernel wifi works, but sound (microphone)
  does not.

  With the 5.11.0-20-generic kernel, the microphone and sound works
  (thank you for fix:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632) but the
  wifi does not.

  With the 5.11.0-20-generic kernel and the linux-firmware (1.187.14)
  pkg installed (sound works but no wifi):

  Information with 5.11.0-20-generic kernel:

  devops@devops-XPS-17-9700:~$ sudo lspci -knn | grep Net -A3; rfkill list
  [sudo] password for devops: 
  04:00.0 Network controller [0280]: Qualcomm Device [17cb:1101] (rev 01)
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
Kernel driver in use: ath11k_pci
Kernel modules: ath11k_pci
  05:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge 
[Titan Ridge 4C 2018] [8086:15ea] (rev 06)
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  devops@devops-XPS-17-9700:~$ sudo lshw -C network
*-network 
 description: Network controller
 product: Qualcomm
 vendor: Qualcomm
 physical id: 0
 bus info: pci@:04:00.0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list
 configuration: driver=ath11k_pci latency=0
 resources: irq:195 memory:d210-d21f
  devops@devops-XPS-17-9700:~$ uname -sr
  Linux 5.11.0-20-generic
  devops@devops-XPS-17-9700:~$ sudo dmesg | grep ath11k
  [2.671864] ath11k_pci :04:00.0: WARNING: ath11k PCI support is 
experimental!
  [2.679263] ath11k_pci :04:00.0: BAR 0: assigned [mem 
0xd210-0xd21f 64bit]
  [2.679309] ath11k_pci :04:00.0: enabling device ( -> 0002)
  devops@devops-XPS-17-9700:~$ sudo dpkg -l | grep firmware
  ii  amd64-microcode 3.20191218.1ubuntu1   
amd64Processor microcode firmware for AMD CPUs
  ii  intel-microcode 3.20201110.0ubuntu0.20.04.2   
amd64Processor microcode firmware for Intel CPUs
  ii  linux-firmware  1.187.14  
all  Firmware for Linux kernel drivers
  devops@devops-XPS-17-9700:~$ sudo ip addr
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  devops@devops-XPS-17-9700:~$

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

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

[Kernel-packages] [Bug 1932354] Re: systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21 (Test dependencies are unsatisfiable)

I am told it is an apt bug, due to systemd package being phased.

See https://launchpad.net/bugs/1925745

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

Title:
  systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21
  (Test dependencies are unsatisfiable)

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

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

  Testing failed on:
    amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210617_171802_98347@/log.gz
    armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/armhf/s/systemd/20210616_224930_60c1e@/log.gz

  
  storage  PASS
  networkd-test.py FAIL non-zero exit status 1
  build-login  FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  boot-and-servicesFAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  udev FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  root-unittests   FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  tests-in-lxd SKIP installation fails and skip-not-installable set
  upstream FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  boot-smoke   FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  systemd-fsckdSKIP exit status 77 and marked as skippable

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

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

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

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Krzysztof Kozlowski (krzk)

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1932303] Re: Dell XPS 17 9700 wifi

2021-06-18 Thread Jeremy Miller

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

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

Title:
  Dell XPS 17 9700 wifi

Status in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Release:
  devops@devops-XPS-17-9700:~$ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  devops@devops-XPS-17-9700:~$ 

  Problem:
  Cannot get both wifi and sound working on a Dell XPS 17 9700 (i9 processor) 
at the same time.

  With the 5.10.0-1029-oem kernel wifi works, but sound (microphone)
  does not.

  With the 5.11.0-20-generic kernel, the microphone and sound works
  (thank you for fix:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632) but the
  wifi does not.

  With the 5.11.0-20-generic kernel and the linux-firmware (1.187.14)
  pkg installed (sound works but no wifi):

  Information with 5.11.0-20-generic kernel:

  devops@devops-XPS-17-9700:~$ sudo lspci -knn | grep Net -A3; rfkill list
  [sudo] password for devops: 
  04:00.0 Network controller [0280]: Qualcomm Device [17cb:1101] (rev 01)
Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]
Kernel driver in use: ath11k_pci
Kernel modules: ath11k_pci
  05:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge 
[Titan Ridge 4C 2018] [8086:15ea] (rev 06)
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  devops@devops-XPS-17-9700:~$ sudo lshw -C network
*-network 
 description: Network controller
 product: Qualcomm
 vendor: Qualcomm
 physical id: 0
 bus info: pci@:04:00.0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list
 configuration: driver=ath11k_pci latency=0
 resources: irq:195 memory:d210-d21f
  devops@devops-XPS-17-9700:~$ uname -sr
  Linux 5.11.0-20-generic
  devops@devops-XPS-17-9700:~$ sudo dmesg | grep ath11k
  [2.671864] ath11k_pci :04:00.0: WARNING: ath11k PCI support is 
experimental!
  [2.679263] ath11k_pci :04:00.0: BAR 0: assigned [mem 
0xd210-0xd21f 64bit]
  [2.679309] ath11k_pci :04:00.0: enabling device ( -> 0002)
  devops@devops-XPS-17-9700:~$ sudo dpkg -l | grep firmware
  ii  amd64-microcode 3.20191218.1ubuntu1   
amd64Processor microcode firmware for AMD CPUs
  ii  intel-microcode 3.20201110.0ubuntu0.20.04.2   
amd64Processor microcode firmware for Intel CPUs
  ii  linux-firmware  1.187.14  
all  Firmware for Linux kernel drivers
  devops@devops-XPS-17-9700:~$ sudo ip addr
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  devops@devops-XPS-17-9700:~$

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

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

[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15

** Description changed:

  [Impact]
  Test case cfs_bandwidth01 in LTP sched test suite is a reproducer for the 
following commits:
-   * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning
-   * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more
-   * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list
-   * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path
-   * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair()
+   * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning
+   * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more
+   * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list
+   * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path
+   * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair()
  
  Without these patches, this test will trigger warning:
  [  694.761774] LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5)
  [  695.801637] [ cut here ]
  [  695.801640] rq->tmp_alone_branch != >leaf_cfs_rq_list
  [  695.801694] WARNING: CPU: 0 PID: 0 at 
/build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 
unthrottle_cfs_rq+0x16f/0x200
  [  695.801695] Modules linked in: input_leds joydev serio_raw mac_hid 
qemu_fw_cfg kvm_intel kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm 
iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse 
virtio_blk pata_acpi floppy virtio_net i2c_piix4
  [  695.801726] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic 
#148-Ubuntu
  [  695.801727] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [  695.801729] RIP: 0010:unthrottle_cfs_rq+0x16f/0x200
  [  695.801730] RSP: 0018:989ebfc03e80 EFLAGS: 00010082
  [  695.801732] RAX:  RBX: 989eb4c6ac00 RCX: 

  [  695.801732] RDX: 0005 RSI: acb63c4d RDI: 
0046
  [  695.801734] RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: 
acb63c20
  [  695.801734] R10:  R11: 0001 R12: 
989eb57fe400
  [  695.801735] R13: 989ebfc21900 R14: 0001 R15: 
0001
  [  695.801737] FS:  () GS:989ebfc0() 
knlGS:
  [  695.801738] CS:  0010 DS:  ES:  CR0: 80050033
  [  695.801739] CR2: 55593258d618 CR3: 7a044000 CR4: 
06f0
  [  695.801742] DR0:  DR1:  DR2: 

  [  695.801743] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  695.801744] Call Trace:
  [  695.801755]  
  [  695.801765]  distribute_cfs_runtime+0xc3/0x110
  [  695.801767]  sched_cfs_period_timer+0xff/0x220
  [  695.801768]  ? sched_cfs_slack_timer+0xd0/0xd0
  [  695.801775]  __hrtimer_run_queues+0xdf/0x230
  [  695.801777]  hrtimer_interrupt+0xa0/0x1d0
  [  695.801786]  smp_apic_timer_interrupt+0x6f/0x140
  [  695.801789]  apic_timer_interrupt+0x90/0xa0
  [  695.801789]  
  [  695.801791] RIP: 0010:native_safe_halt+0x12/0x20
  [  695.801792] RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: 
ff11
  [  695.801793] RAX: abbc9280 RBX:  RCX: 

  [  695.801794] RDX:  RSI:  RDI: 

  [  695.801795] RBP: ac603e28 R08: 00af39850067 R09: 
989e73749d00
  [  695.801796] R10:  R11: 7fff R12: 

  [  695.801796] R13:  R14:  R15: 

  [  695.801801]  ? __sched_text_end+0x1/0x1
  [  695.801804]  default_idle+0x20/0x100
  [  695.801813]  arch_cpu_idle+0x15/0x20
  [  695.801814]  default_idle_call+0x23/0x30
  [  695.801821]  do_idle+0x172/0x1f0
  [  695.801823]  cpu_startup_entry+0x73/0x80
  [  695.801825]  rest_init+0xae/0xb0
  [  695.801843]  start_kernel+0x4dc/0x500
  [  695.801845]  x86_64_start_reservations+0x24/0x26
  [  695.801847]  x86_64_start_kernel+0x74/0x77
  [  695.801851]  secondary_startup_64+0xa5/0xb0
  [  695.801852] Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 
00 75 5f 31 db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 
48 85 db 74 43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00
  [  695.801875] ---[ end trace b6b9a70bc2945c0c ]---
  
  [Fix]
  
  [Test]
  Test kernel can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1931325-cfs_bandwidth01/
  
  With these patches applied, the test can pass without any issue.
  
  I have also run the whole sched test suite in LTP to make sure it didn't

[Kernel-packages] [Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic

2021-06-18 Thread Leon van Heerden

Hi, 
We think we are affected by the same bug. 
We were on version 4.15.0-139 and upgraded to 144 before finding this post. 
Is there any confirmation that this issue also occurs in 4.15.0-144? 

I have have installed version 4.15.0-136 in the meantime to allow us to
reboot and select that kernel, incase the issue is present.

Hope to see a fix for this issue soon.

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

Title:
  Disk IO very slow on kernel 4.15.0-142-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  After upgrading Ubuntu 18.04 kernel from 4.15.0-136-generic to kernel
  4.15.0-142-generic disk IOs (writes) are suffering from terrible
  delay.

  Time required to write 1GB of data to the dist is ~12 minutes.
   
  1GB in 12 minutes:
  strace -ttvvff -o mel.strace dd bs=1024k count=1024  if=/dev/zero 
of=/data/disk_test/dd_test

  Before the upgrade,  it took seconds to complete.
  The only change which was done on the system was security upgrade done with 
unattended-upgrade utility and main repositories for bionic and bionic-security.

  This is physical server LENOVO System x3650 M5, with Symbios Logic
  MegaRAID SAS-3 3108  disk controller.

  The only difference which I see is that there are more modules loaded
  by the latest kernel.

  I would expect that the performance would be the same. There were no
  changes to the physical server and the disks are reported as online
  and healthy. No only dd is affected but also all disk-based operation
  by barman (we are using postgres steaming backup along with rsync/ssh
  archiving).

  I think this could be a kernel bug. I would be happy to provide other
  information which would help in fixing this problem.

  =
  Details:

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  lsmod
  Module  Size  Used by
  ip6_tables 28672  0
  iptable_filter 16384  0
  ip_tables  28672  1 iptable_filter
  x_tables   40960  3 iptable_filter,ip6_tables,ip_tables
  tcp_diag   16384  0
  udp_diag   16384  0
  raw_diag   16384  0
  inet_diag  24576  3 tcp_diag,raw_diag,udp_diag
  unix_diag  16384  0
  binfmt_misc20480  1
  ipmi_ssif  32768  0
  kvm_intel 217088  0
  kvm   614400  1 kvm_intel
  irqbypass  16384  1 kvm
  crct10dif_pclmul   16384  0
  crc32_pclmul   16384  0
  ghash_clmulni_intel16384  0
  pcbc   16384  0
  aesni_intel   188416  0
  aes_x86_64 20480  1 aesni_intel
  crypto_simd16384  1 aesni_intel
  glue_helper16384  1 aesni_intel
  cryptd 24576  3 crypto_simd,ghash_clmulni_intel,aesni_intel
  ipmi_si57344  0
  ipmi_devintf   20480  0
  ipmi_msghandler53248  3 ipmi_devintf,ipmi_si,ipmi_ssif
  acpi_pad  180224  0
  bonding   163840  0
  lp 20480  0
  parport49152  1 lp
  autofs440960  2
  mgag20045056  1
  i2c_algo_bit   16384  1 mgag200
  ttm   106496  1 mgag200
  drm_kms_helper172032  1 mgag200
  syscopyarea16384  1 drm_kms_helper
  tg3   167936  0
  sysfillrect16384  1 drm_kms_helper
  sysimgblt  16384  1 drm_kms_helper
  fb_sys_fops16384  1 drm_kms_helper
  ptp20480  1 tg3
  drm   401408  4 drm_kms_helper,mgag200,ttm
  pps_core   20480  1 ptp
  megaraid_sas  143360  12


  lspci  -vnn -s 0b:00.0
  0b:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS-3 
3108 [Invader] [1000:005d] (rev 02)
Subsystem: IBM MegaRAID SAS-3 3108 [Invader] [1014:0454]
Physical Slot: 9
Flags: bus master, fast devsel, latency 0, IRQ 31, NUMA node 0
I/O ports at 2e00 [size=256]
Memory at 903f (64-bit, non-prefetchable) [size=64K]
Memory at 9040 (64-bit, non-prefetchable) [size=1M]
Expansion ROM at  [disabled]
Capabilities: [50] Power Management version 3
Capabilities: [68] Express Endpoint, MSI 00
Capabilities: [d0] Vital Product Data
Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=97 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [1e0] #19
Capabilities: [1c0] Power Budgeting 
Capabilities: [148] Alternative Routing-ID Interpretation (ARI)
Kernel driver in use: megaraid_sas
Kernel modules: megaraid_sas

  Strace example

[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15

** Description changed:

  [Impact]
+ Test case cfs_bandwidth01 in LTP sched test suite is a reproducer for the 
following commits:
+ * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning
+ * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more
+ * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list
+ * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path 
+ * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair()
  
+ Without these patches, this test will trigger warning:
+ [  694.761774] LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5)
+ [  695.801637] [ cut here ]
+ [  695.801640] rq->tmp_alone_branch != >leaf_cfs_rq_list
+ [  695.801694] WARNING: CPU: 0 PID: 0 at 
/build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 
unthrottle_cfs_rq+0x16f/0x200
+ [  695.801695] Modules linked in: input_leds joydev serio_raw mac_hid 
qemu_fw_cfg kvm_intel kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm 
iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse 
virtio_blk pata_acpi floppy virtio_net i2c_piix4
+ [  695.801726] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic 
#148-Ubuntu
+ [  695.801727] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
+ [  695.801729] RIP: 0010:unthrottle_cfs_rq+0x16f/0x200
+ [  695.801730] RSP: 0018:989ebfc03e80 EFLAGS: 00010082
+ [  695.801732] RAX:  RBX: 989eb4c6ac00 RCX: 

+ [  695.801732] RDX: 0005 RSI: acb63c4d RDI: 
0046
+ [  695.801734] RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: 
acb63c20
+ [  695.801734] R10:  R11: 0001 R12: 
989eb57fe400
+ [  695.801735] R13: 989ebfc21900 R14: 0001 R15: 
0001
+ [  695.801737] FS:  () GS:989ebfc0() 
knlGS:
+ [  695.801738] CS:  0010 DS:  ES:  CR0: 80050033
+ [  695.801739] CR2: 55593258d618 CR3: 7a044000 CR4: 
06f0
+ [  695.801742] DR0:  DR1:  DR2: 

+ [  695.801743] DR3:  DR6: fffe0ff0 DR7: 
0400
+ [  695.801744] Call Trace:
+ [  695.801755]  
+ [  695.801765]  distribute_cfs_runtime+0xc3/0x110
+ [  695.801767]  sched_cfs_period_timer+0xff/0x220
+ [  695.801768]  ? sched_cfs_slack_timer+0xd0/0xd0
+ [  695.801775]  __hrtimer_run_queues+0xdf/0x230
+ [  695.801777]  hrtimer_interrupt+0xa0/0x1d0
+ [  695.801786]  smp_apic_timer_interrupt+0x6f/0x140
+ [  695.801789]  apic_timer_interrupt+0x90/0xa0
+ [  695.801789]  
+ [  695.801791] RIP: 0010:native_safe_halt+0x12/0x20
+ [  695.801792] RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: 
ff11
+ [  695.801793] RAX: abbc9280 RBX:  RCX: 

+ [  695.801794] RDX:  RSI:  RDI: 

+ [  695.801795] RBP: ac603e28 R08: 00af39850067 R09: 
989e73749d00
+ [  695.801796] R10:  R11: 7fff R12: 

+ [  695.801796] R13:  R14:  R15: 

+ [  695.801801]  ? __sched_text_end+0x1/0x1
+ [  695.801804]  default_idle+0x20/0x100
+ [  695.801813]  arch_cpu_idle+0x15/0x20
+ [  695.801814]  default_idle_call+0x23/0x30
+ [  695.801821]  do_idle+0x172/0x1f0
+ [  695.801823]  cpu_startup_entry+0x73/0x80
+ [  695.801825]  rest_init+0xae/0xb0
+ [  695.801843]  start_kernel+0x4dc/0x500
+ [  695.801845]  x86_64_start_reservations+0x24/0x26
+ [  695.801847]  x86_64_start_kernel+0x74/0x77
+ [  695.801851]  secondary_startup_64+0xa5/0xb0
+ [  695.801852] Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 
00 75 5f 31 db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 
48 85 db 74 43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00
+ [  695.801875] ---[ end trace b6b9a70bc2945c0c ]--- 
+ 
+ [Fix]
+ 
+ 
+ [Test]
+ Test kernel can be found here:
+ https://people.canonical.com/~phlin/kernel/lp-1931325-cfs_bandwidth01/
+ 
+ With these patches applied, the test can pass without any issue.
+ 
+ I have also run the whole sched test suite in LTP to make sure it didn't
+ cause any other problem.
+ 
+ [Regression Potential]
+ 
+ 
+ [Original Bug Report]
  Issue found on Azure 4.15.0-1116.129 Bionic
  
  This is a new test case added 8 days ago. So this is not a regression:
  
https://github.com/linux-test-project/ltp/commit/d7b2d7cea71feaea1f27cae185abfe39f238d649
  
  Test log:
  
   cfs_bandwidth01.c:49: TINFO: Set 'worker1/cpu.max' =

[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15

** Description changed:

+ [Impact]
+ 
  Issue found on Azure 4.15.0-1116.129 Bionic
  
  This is a new test case added 8 days ago. So this is not a regression:
  
https://github.com/linux-test-project/ltp/commit/d7b2d7cea71feaea1f27cae185abfe39f238d649
  
  Test log:
  
   cfs_bandwidth01.c:49: TINFO: Set 'worker1/cpu.max' = '3000 1'
   cfs_bandwidth01.c:49: TINFO: Set 'worker2/cpu.max' = '2000 1'
   cfs_bandwidth01.c:49: TINFO: Set 'worker3/cpu.max' = '3000 1'
   cfs_bandwidth01.c:113: TPASS: Scheduled bandwidth constrained workers
   cfs_bandwidth01.c:49: TINFO: Set 'level2/cpu.max' = '5000 1'
   cfs_bandwidth01.c:125: TPASS: Workers exited
   cfs_bandwidth01.c:113: TPASS: Scheduled bandwidth constrained workers
   cfs_bandwidth01.c:49: TINFO: Set 'level2/cpu.max' = '5000 1'
   cfs_bandwidth01.c:125: TPASS: Workers exited
   cfs_bandwidth01.c:113: TPASS: Scheduled bandwidth constrained workers
   cfs_bandwidth01.c:49: TINFO: Set 'level2/cpu.max' = '5000 1'
   cfs_bandwidth01.c:125: TPASS: Workers exited
   cfs_bandwidth01.c:113: TPASS: Scheduled bandwidth constrained workers
   cfs_bandwidth01.c:49: TINFO: Set 'level2/cpu.max' = '5000 1'
   cfs_bandwidth01.c:125: TPASS: Workers exited
   cfs_bandwidth01.c:113: TPASS: Scheduled bandwidth constrained workers
   cfs_bandwidth01.c:49: TINFO: Set 'level2/cpu.max' = '5000 1'
   cfs_bandwidth01.c:125: TPASS: Workers exited
   tst_test.c:1349: TFAIL: Kernel is now tainted.
  
   HINT: You _MAY_ be missing kernel fixes, see:
  
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=39f23ce07b93
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b34cb07dde7c
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe61468b2cbc
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5ab297bab984
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d4d22468dae
  
   Summary:
   passed 10
   failed 1
   broken 0
   skipped 0
   warnings 0
   tag=cfs_bandwidth01 stime=1622734092 dur=15 exit=exited stat=1 core=no 
cu=478 cs=303
  
  Note that this test has failed on the following instances:
    * Basic_A2
    * Standard_B1ms
    * Standard_D48_v3
    * Standard_F32s_v2
  
  But passed with:
    * Standard_DS15_v2
    * Standard_DS5_v2
  
- 
  When this issue happens, kernel will be tainted with warning:
  [  694.761774] LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5)
  [  695.801637] [ cut here ]
  [  695.801640] rq->tmp_alone_branch != >leaf_cfs_rq_list
  [  695.801694] WARNING: CPU: 0 PID: 0 at 
/build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 
unthrottle_cfs_rq+0x16f/0x200
  [  695.801695] Modules linked in: input_leds joydev serio_raw mac_hid 
qemu_fw_cfg kvm_intel kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm 
iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse 
virtio_blk pata_acpi floppy virtio_net i2c_piix4
  [  695.801726] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic 
#148-Ubuntu
  [  695.801727] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [  695.801729] RIP: 0010:unthrottle_cfs_rq+0x16f/0x200
  [  695.801730] RSP: 0018:989ebfc03e80 EFLAGS: 00010082
  [  695.801732] RAX:  RBX: 989eb4c6ac00 RCX: 

  [  695.801732] RDX: 0005 RSI: acb63c4d RDI: 
0046
  [  695.801734] RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: 
acb63c20
  [  695.801734] R10:  R11: 0001 R12: 
989eb57fe400
  [  695.801735] R13: 989ebfc21900 R14: 0001 R15: 
0001
  [  695.801737] FS:  () GS:989ebfc0() 
knlGS:
  [  695.801738] CS:  0010 DS:  ES:  CR0: 80050033
  [  695.801739] CR2: 55593258d618 CR3: 7a044000 CR4: 
06f0
  [  695.801742] DR0:  DR1:  DR2: 

  [  695.801743] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  695.801744] Call Trace:
  [  695.801755]  
  [  695.801765]  distribute_cfs_runtime+0xc3/0x110
  [  695.801767]  sched_cfs_period_timer+0xff/0x220
  [  695.801768]  ? sched_cfs_slack_timer+0xd0/0xd0
  [  695.801775]  __hrtimer_run_queues+0xdf/0x230
  [  695.801777]  hrtimer_interrupt+0xa0/0x1d0
  [  695.801786]  smp_apic_timer_interrupt+0x6f/0x140
  [  695.801789]  apic_timer_interrupt+0x90/0xa0
  [  695.801789]  
  [  695.801791] RIP: 0010:native_safe_halt+0x12/0x20
  [  695.801792] RSP:

[Kernel-packages] [Bug 1932354] Re: systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21 (Test dependencies are unsatisfiable)

The following packages have unmet dependencies:
 systemd-tests : Depends: libsystemd0 (= 247.3-3ubuntu3.1) but 247.3-3ubuntu3 
is to be installed
 Depends: systemd (= 247.3-3ubuntu3.1)

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

Title:
  systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21
  (Test dependencies are unsatisfiable)

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

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

  Testing failed on:
    amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210617_171802_98347@/log.gz
    armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/armhf/s/systemd/20210616_224930_60c1e@/log.gz

  
  storage  PASS
  networkd-test.py FAIL non-zero exit status 1
  build-login  FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  boot-and-servicesFAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  udev FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  root-unittests   FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  tests-in-lxd SKIP installation fails and skip-not-installable set
  upstream FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  boot-smoke   FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  systemd-fsckdSKIP exit status 77 and marked as skippable

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

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

[Kernel-packages] [Bug 1932354] Re: systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21 (Test dependencies are unsatisfiable)

Retrying these once.

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

Title:
systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21
(Test dependencies are unsatisfiable)

Status in linux package in Ubuntu:
New
Status in systemd package in Ubuntu:
New

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

Testing failed on:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210617_171802_98347@/log.gz
armhf:
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/armhf/s/systemd/20210616_224930_60c1e@/log.gz

storage PASS
networkd-test.py FAIL non-zero exit status 1
build-login FAIL badpkg
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
boot-and-servicesFAIL badpkg
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
udev FAIL badpkg
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
root-unittests FAIL badpkg
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
tests-in-lxd SKIP installation fails and skip-not-installable set
upstream FAIL badpkg
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
boot-smoke FAIL badpkg
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
systemd-fsckdSKIP exit status 77 and marked as skippable

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

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

[Kernel-packages] [Bug 1932354] Re: systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21 (Test dependencies are unsatisfiable)

I wonder if this is ADT cloud failure.

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

Title:
systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21
(Test dependencies are unsatisfiable)

Status in linux package in Ubuntu:
New
Status in systemd package in Ubuntu:
New

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

[Kernel-packages] [Bug 1929504] Re: Add support for IO functions of AAEON devices

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

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => 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/1929504

Title:
  Add support for IO functions of AAEON devices

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  In Progress

Bug description:
  [Impact]
  Require drivers to enable AAEON devices.

  [Fix]
  AAEON provides a series of patches to support its GPIO/LED/Watchdog/HWMON 
devices.
  https://www.spinics.net/lists/linux-gpio/msg61301.html

  [Test]
  Verified on AAEON platform.

  [Where problems could occur]
  No, they are new drivers, should not introduce any regressions.

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

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

[Kernel-packages] [Bug 1932081] Re: Disable hv-kvp-daemon.service on certain instance types

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => 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/1932081

Title:
  Disable hv-kvp-daemon.service on certain instance types

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
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:
  Fix Committed

Bug description:
  [Impact]

   * Disable hv-kvp-daemon.service on certain instance types. As
  requested for some azure instance types, hv-kvp-daemon is prohibited
  from starting, and currently it takes a long time to come up and fail.
  Configure to disable the service on those instances. At the moment, we
  can key off kernel command line to detect those.

  [Test Plan]

   * Boot preview image in azure
   * Check that hv-kvp-daemon.service is not running

  [Where problems could occur]

   * The conditions/detection could have been more specific as to when
  the daemon is pointless to run. Thus key-off kernel commandline is
  good enough for now, but may require changes in the future.

  [Other Info]

  @ Kernel team, also see https://trello.com/c/JbomiFOe

  https://lists.ubuntu.com/archives/kernel-team/2021-June/121384.html

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

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

[Kernel-packages] [Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic

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

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

Title:
  Disk IO very slow on kernel 4.15.0-142-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  After upgrading Ubuntu 18.04 kernel from 4.15.0-136-generic to kernel
  4.15.0-142-generic disk IOs (writes) are suffering from terrible
  delay.

  Time required to write 1GB of data to the dist is ~12 minutes.
   
  1GB in 12 minutes:
  strace -ttvvff -o mel.strace dd bs=1024k count=1024  if=/dev/zero 
of=/data/disk_test/dd_test

  Before the upgrade,  it took seconds to complete.
  The only change which was done on the system was security upgrade done with 
unattended-upgrade utility and main repositories for bionic and bionic-security.

  This is physical server LENOVO System x3650 M5, with Symbios Logic
  MegaRAID SAS-3 3108  disk controller.

  The only difference which I see is that there are more modules loaded
  by the latest kernel.

  I would expect that the performance would be the same. There were no
  changes to the physical server and the disks are reported as online
  and healthy. No only dd is affected but also all disk-based operation
  by barman (we are using postgres steaming backup along with rsync/ssh
  archiving).

  I think this could be a kernel bug. I would be happy to provide other
  information which would help in fixing this problem.

  =
  Details:

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  lsmod
  Module  Size  Used by
  ip6_tables 28672  0
  iptable_filter 16384  0
  ip_tables  28672  1 iptable_filter
  x_tables   40960  3 iptable_filter,ip6_tables,ip_tables
  tcp_diag   16384  0
  udp_diag   16384  0
  raw_diag   16384  0
  inet_diag  24576  3 tcp_diag,raw_diag,udp_diag
  unix_diag  16384  0
  binfmt_misc20480  1
  ipmi_ssif  32768  0
  kvm_intel 217088  0
  kvm   614400  1 kvm_intel
  irqbypass  16384  1 kvm
  crct10dif_pclmul   16384  0
  crc32_pclmul   16384  0
  ghash_clmulni_intel16384  0
  pcbc   16384  0
  aesni_intel   188416  0
  aes_x86_64 20480  1 aesni_intel
  crypto_simd16384  1 aesni_intel
  glue_helper16384  1 aesni_intel
  cryptd 24576  3 crypto_simd,ghash_clmulni_intel,aesni_intel
  ipmi_si57344  0
  ipmi_devintf   20480  0
  ipmi_msghandler53248  3 ipmi_devintf,ipmi_si,ipmi_ssif
  acpi_pad  180224  0
  bonding   163840  0
  lp 20480  0
  parport49152  1 lp
  autofs440960  2
  mgag20045056  1
  i2c_algo_bit   16384  1 mgag200
  ttm   106496  1 mgag200
  drm_kms_helper172032  1 mgag200
  syscopyarea16384  1 drm_kms_helper
  tg3   167936  0
  sysfillrect16384  1 drm_kms_helper
  sysimgblt  16384  1 drm_kms_helper
  fb_sys_fops16384  1 drm_kms_helper
  ptp20480  1 tg3
  drm   401408  4 drm_kms_helper,mgag200,ttm
  pps_core   20480  1 ptp
  megaraid_sas  143360  12


  lspci  -vnn -s 0b:00.0
  0b:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS-3 
3108 [Invader] [1000:005d] (rev 02)
Subsystem: IBM MegaRAID SAS-3 3108 [Invader] [1014:0454]
Physical Slot: 9
Flags: bus master, fast devsel, latency 0, IRQ 31, NUMA node 0
I/O ports at 2e00 [size=256]
Memory at 903f (64-bit, non-prefetchable) [size=64K]
Memory at 9040 (64-bit, non-prefetchable) [size=1M]
Expansion ROM at  [disabled]
Capabilities: [50] Power Management version 3
Capabilities: [68] Express Endpoint, MSI 00
Capabilities: [d0] Vital Product Data
Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=97 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [1e0] #19
Capabilities: [1c0] Power Budgeting 
Capabilities: [148] Alternative Routing-ID Interpretation (ARI)
Kernel driver in use: megaraid_sas
Kernel modules: megaraid_sas

  Strace example for 10MB:
  strace -ttvvff -o mel.strace   dd bs=1024k count=10  if=/dev/zero 
of=/data/disk_test/dd_test 
  10+0 records in
  10+0 records out
  10485760 bytes (10 MB, 10 MiB) copied, 6.73972 s, 1.6 MB/s

  14:59:19.145037

[Kernel-packages] [Bug 1912789] Re: Add support for selective build of special drivers

** Changed in: linux (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => 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/1912789

Title:
  Add support for selective build of special drivers

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed

Bug description:
  [SRU Justification]

  = Impact =

  We want to add some driver code which exists in the primary kernel
  source but will not get included unless specifically asked for. As
  long as there are no drivers using this, there is no user-visible
  change.

  = Impact =

  This will be done by adding a new config option which gets turned on
  via build setup rules. The default will be off.

  = Testcase =

  As long as there are no consumers changes can only be seen by
  inspecting the build logs (if even that).

  = Regression Potential =

  This prepares for future consumers. At this stage either the build
  will fail completely or pass and in that case the produced kernel
  binaries are the same as they were before.

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

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

[Kernel-packages] [Bug 1932055] Re: Mute/Mic mute LEDs and right speaker are not work on HP platforms

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

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

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

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

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

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

Title:
  Mute/Mic mute LEDs and right speaker are not work on HP platforms

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

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on
  1) HP Elite Dragonfly G2 Notebook PC
  2) HP EliteBook x360 1040 G8 Notebook PC
  3) HP EliteBook 840 Aero G8 Notebook PC
  4) HP ZBook Power 15.6 inch G8 Mobile Workstation PC
  The right channel of internal speaker doesn't work on
  1) HP Elite Dragonfly G2 Notebook PC
  2) HP EliteBook x360 1040 G8 Notebook PC

  [Fix]
  These four platforms need specific quirk for different hardware layout.
  Thus, add the quirks for them.

  [Test]
  After applying the quirk, the LEDs/speaker are work good on
  1) HP Elite Dragonfly G2 Notebook PC
  2) HP EliteBook x360 1040 G8 Notebook PC
  3) HP EliteBook 840 Aero G8 Notebook PC
  4) HP ZBook Power 15.6 inch G8 Mobile Workstation PC

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

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

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

[Kernel-packages] [Bug 1929444] Re: SD card initialization on insertion fails

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

** Changed in: linux (Ubuntu Impish)
   Status: Fix Committed => Triaged

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

Title:
  SD card initialization on insertion fails

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

Bug description:
  [SRU Justification]

  [Impact]
  The memory card can be detected and mount correctly when the system starts 
with the card inserted. But it will fail to be detected at the subsequent 
re-plug. It only happens on particular Realtek older PCI interfaced card 
readers. The RTL8411B (10ec:5287) is reported problematic for this issue.

  [Fix]
  Found the commit 121e9c6b5c4c ("misc: rtsx: modify and fix init_hw function") 
in 5.11.0-rc1 introduces this regression. The fix from upstream use the old 
ASPM control for particular realtek card reader models: 8411 5209 5227 5229 
5249 5250.

  [Test]
  Verified on the Realtek PCI interfaced card reader RTL8411B and verify 
whether the memory card can be detected for each re-plug.

  
  [Where problem could occur]
  The regression can be considered as low since the fix has specified separate 
ASPM control for particular Realtek Card Readers.

  
  == Original Bug Description ==

  If I boot my laptop with an SD card (actually SDXC) in the MMC slot
  the system sees it and I can mount and use it.

  If I then unmount it, remove it then re-insert it I get this in the
  system ,og:

  [  194.673108] mmc0: card e624 removed
  [  205.462065] mmc0: cannot verify signal voltage switch
  [  205.567479] mmc0: error -84 whilst initialising SD card

  and the card cannot then be used.

  It was OK in groovy. It's failing in hirsute.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-generic 5.11.0.17.18
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gml44104153 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon May 24 17:36:49 2021
  HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c
  InstallationDate: Installed on 2020-08-13 (284 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: PC Specialist LTD N150CU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago)
  dmi.bios.date: 11/15/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TPCS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N151CU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N150CU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist LTD

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

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

[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15

** Description changed:

  Issue found on Azure 4.15.0-1116.129 Bionic
  
  This is a new test case added 8 days ago. So this is not a regression:
  
https://github.com/linux-test-project/ltp/commit/d7b2d7cea71feaea1f27cae185abfe39f238d649
  
  Test log:
  
   cfs_bandwidth01.c:49: TINFO: Set 'worker1/cpu.max' = '3000 1'
   cfs_bandwidth01.c:49: TINFO: Set 'worker2/cpu.max' = '2000 1'
   cfs_bandwidth01.c:49: TINFO: Set 'worker3/cpu.max' = '3000 1'
   cfs_bandwidth01.c:113: TPASS: Scheduled bandwidth constrained workers
   cfs_bandwidth01.c:49: TINFO: Set 'level2/cpu.max' = '5000 1'
   cfs_bandwidth01.c:125: TPASS: Workers exited
   cfs_bandwidth01.c:113: TPASS: Scheduled bandwidth constrained workers
   cfs_bandwidth01.c:49: TINFO: Set 'level2/cpu.max' = '5000 1'
   cfs_bandwidth01.c:125: TPASS: Workers exited
   cfs_bandwidth01.c:113: TPASS: Scheduled bandwidth constrained workers
   cfs_bandwidth01.c:49: TINFO: Set 'level2/cpu.max' = '5000 1'
   cfs_bandwidth01.c:125: TPASS: Workers exited
   cfs_bandwidth01.c:113: TPASS: Scheduled bandwidth constrained workers
   cfs_bandwidth01.c:49: TINFO: Set 'level2/cpu.max' = '5000 1'
   cfs_bandwidth01.c:125: TPASS: Workers exited
   cfs_bandwidth01.c:113: TPASS: Scheduled bandwidth constrained workers
   cfs_bandwidth01.c:49: TINFO: Set 'level2/cpu.max' = '5000 1'
   cfs_bandwidth01.c:125: TPASS: Workers exited
   tst_test.c:1349: TFAIL: Kernel is now tainted.
  
   HINT: You _MAY_ be missing kernel fixes, see:
  
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=39f23ce07b93
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b34cb07dde7c
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe61468b2cbc
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5ab297bab984
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d4d22468dae
  
   Summary:
   passed 10
   failed 1
   broken 0
   skipped 0
   warnings 0
   tag=cfs_bandwidth01 stime=1622734092 dur=15 exit=exited stat=1 core=no 
cu=478 cs=303
  
  Note that this test has failed on the following instances:
-   * Basic_A2
-   * Standard_B1ms
-   * Standard_D48_v3
-   * Standard_F32s_v2
+   * Basic_A2
+   * Standard_B1ms
+   * Standard_D48_v3
+   * Standard_F32s_v2
  
  But passed with:
-   * Standard_DS15_v2
-   * Standard_DS5_v2
+   * Standard_DS15_v2
+   * Standard_DS5_v2
+ 
+ 
+ When this issue happens, kernel will be tainted with warning:
+ [  694.761774] LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5)
+ [  695.801637] [ cut here ]
+ [  695.801640] rq->tmp_alone_branch != >leaf_cfs_rq_list
+ [  695.801694] WARNING: CPU: 0 PID: 0 at 
/build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 
unthrottle_cfs_rq+0x16f/0x200
+ [  695.801695] Modules linked in: input_leds joydev serio_raw mac_hid 
qemu_fw_cfg kvm_intel kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm 
iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse 
virtio_blk pata_acpi floppy virtio_net i2c_piix4
+ [  695.801726] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic 
#148-Ubuntu
+ [  695.801727] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
+ [  695.801729] RIP: 0010:unthrottle_cfs_rq+0x16f/0x200
+ [  695.801730] RSP: 0018:989ebfc03e80 EFLAGS: 00010082
+ [  695.801732] RAX:  RBX: 989eb4c6ac00 RCX: 

+ [  695.801732] RDX: 0005 RSI: acb63c4d RDI: 
0046
+ [  695.801734] RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: 
acb63c20
+ [  695.801734] R10:  R11: 0001 R12: 
989eb57fe400
+ [  695.801735] R13: 989ebfc21900 R14: 0001 R15: 
0001
+ [  695.801737] FS:  () GS:989ebfc0() 
knlGS:
+ [  695.801738] CS:  0010 DS:  ES:  CR0: 80050033
+ [  695.801739] CR2: 55593258d618 CR3: 7a044000 CR4: 
06f0
+ [  695.801742] DR0:  DR1:  DR2: 

+ [  695.801743] DR3:  DR6: fffe0ff0 DR7: 
0400
+ [  695.801744] Call Trace:
+ [  695.801755]  
+ [  695.801765]  distribute_cfs_runtime+0xc3/0x110
+ [  695.801767]  sched_cfs_period_timer+0xff/0x220
+ [  695.801768]  ? sched_cfs_slack_timer+0xd0/0xd0
+ [  695.801775]  __hrtimer_run_queues+0xdf/0x230
+ [  695.801777]  hrtimer_interrupt+0xa0/0x1d0
+ [  695.801786]  smp_apic_timer_interrupt+0x6f/0x140
+ [  695.801789]

[Kernel-packages] [Bug 1928315] Re: Touchpad problem

2021-06-18 Thread Etele Berszány

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928315/+attachment/5505429/+files/dmesg.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/1928315

Title:
  Touchpad problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fujitsu Lifebook U931x
  The touchpad is not detected at all (as far as I understand it - newbie) and 
does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-72-generic 5.4.0-72.80
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-72-generic.
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kari884 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 
'sofhdadsp'/'FUJITSUCLIENTCOMPUTINGLIMITED-LIFEBOOKU9310X-10601736746-FJNB2DB'
 Mixer name : 'Realtek ALC255'
 Components : 'HDA:8086280b,80860101,0010 
HDA:10ec0255,1e267505,0012 cfg-dmics:2'
 Controls  : 47
 Simple ctrls  : 18
  CasperMD5CheckResult: skip
  CurrentDesktop: Enlightenment
  Date: Thu May 13 11:06:23 2021
  InstallationDate: Installed on 2021-05-13 (0 days ago)
  InstallationMedia: Bodhi 20.04 - Release amd64 (20210510.0)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U9310X
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic 
root=UUID=3ea6e40f-26b4-454d-b009-4d6eb6cc2b4d ro i8042.notimeout i8042.nomux 
quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-72-generic N/A
   linux-backports-modules-5.4.0-72-generic  N/A
   linux-firmware1.187.12
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2020
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 2.13
  dmi.board.name: FJNB2DB
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: A2
  dmi.chassis.type: 31
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.chassis.version: LIFEBOOK U9310X
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.13:bd06/19/2020:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU9310X:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DB:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvrLIFEBOOKU9310X:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK U9310X
  dmi.product.sku: SK00
  dmi.product.version: 10601736746
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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

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

[Kernel-packages] [Bug 1928315] Re: Touchpad problem

2021-06-18 Thread Etele Berszány

** Attachment added: "lsmod.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928315/+attachment/5505430/+files/lsmod.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/1928315

Title:
  Touchpad problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fujitsu Lifebook U931x
  The touchpad is not detected at all (as far as I understand it - newbie) and 
does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-72-generic 5.4.0-72.80
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-72-generic.
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kari884 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 
'sofhdadsp'/'FUJITSUCLIENTCOMPUTINGLIMITED-LIFEBOOKU9310X-10601736746-FJNB2DB'
 Mixer name : 'Realtek ALC255'
 Components : 'HDA:8086280b,80860101,0010 
HDA:10ec0255,1e267505,0012 cfg-dmics:2'
 Controls  : 47
 Simple ctrls  : 18
  CasperMD5CheckResult: skip
  CurrentDesktop: Enlightenment
  Date: Thu May 13 11:06:23 2021
  InstallationDate: Installed on 2021-05-13 (0 days ago)
  InstallationMedia: Bodhi 20.04 - Release amd64 (20210510.0)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U9310X
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic 
root=UUID=3ea6e40f-26b4-454d-b009-4d6eb6cc2b4d ro i8042.notimeout i8042.nomux 
quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-72-generic N/A
   linux-backports-modules-5.4.0-72-generic  N/A
   linux-firmware1.187.12
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2020
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 2.13
  dmi.board.name: FJNB2DB
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: A2
  dmi.chassis.type: 31
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.chassis.version: LIFEBOOK U9310X
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.13:bd06/19/2020:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU9310X:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DB:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvrLIFEBOOKU9310X:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK U9310X
  dmi.product.sku: SK00
  dmi.product.version: 10601736746
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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

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

[Kernel-packages] [Bug 1931131] Re: Update the 465 and the 460 NVIDIA driver series

2021-06-18 Thread Andy Whitcroft

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-390 into bionic-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-390/390.143-0ubuntu0.18.04.2 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-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. 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: nvidia-graphics-drivers-390 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  Update the 465 and the 460 NVIDIA driver series

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  In Progress
Status in nvidia-settings package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Hirsute:
  Fix Committed
Status in nvidia-settings source package in Hirsute:
  Fix Committed

Bug description:
  Update the 465 and the 460 NVIDIA driver series, and add support for
  Linux 5.13 to all the driver series.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

[Kernel-packages] [Bug 1929444] Re: SD card initialization on insertion fails

2021-06-18 Thread Chris Chiu

Understood. Thanks

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

Title:
  SD card initialization on insertion fails

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]
  The memory card can be detected and mount correctly when the system starts 
with the card inserted. But it will fail to be detected at the subsequent 
re-plug. It only happens on particular Realtek older PCI interfaced card 
readers. The RTL8411B (10ec:5287) is reported problematic for this issue.

  [Fix]
  Found the commit 121e9c6b5c4c ("misc: rtsx: modify and fix init_hw function") 
in 5.11.0-rc1 introduces this regression. The fix from upstream use the old 
ASPM control for particular realtek card reader models: 8411 5209 5227 5229 
5249 5250.

  [Test]
  Verified on the Realtek PCI interfaced card reader RTL8411B and verify 
whether the memory card can be detected for each re-plug.

  
  [Where problem could occur]
  The regression can be considered as low since the fix has specified separate 
ASPM control for particular Realtek Card Readers.

  
  == Original Bug Description ==

  If I boot my laptop with an SD card (actually SDXC) in the MMC slot
  the system sees it and I can mount and use it.

  If I then unmount it, remove it then re-insert it I get this in the
  system ,og:

  [  194.673108] mmc0: card e624 removed
  [  205.462065] mmc0: cannot verify signal voltage switch
  [  205.567479] mmc0: error -84 whilst initialising SD card

  and the card cannot then be used.

  It was OK in groovy. It's failing in hirsute.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-generic 5.11.0.17.18
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gml44104153 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon May 24 17:36:49 2021
  HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c
  InstallationDate: Installed on 2020-08-13 (284 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: PC Specialist LTD N150CU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago)
  dmi.bios.date: 11/15/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TPCS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N151CU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N150CU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist LTD

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

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

[Kernel-packages] [Bug 1932081] Re: Disable hv-kvp-daemon.service on certain instance types

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

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

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

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

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

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

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

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

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

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

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

Title:
  Disable hv-kvp-daemon.service on certain instance types

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
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]

   * Disable hv-kvp-daemon.service on certain instance types. As
  requested for some azure instance types, hv-kvp-daemon is prohibited
  from starting, and currently it takes a long time to come up and fail.
  Configure to disable the service on those instances. At the moment, we
  can key off kernel command line to detect those.

  [Test Plan]

   * Boot preview image in azure
   * Check that hv-kvp-daemon.service is not running

  [Where problems could occur]

   * The conditions/detection could have been more specific as to when
  the daemon is pointless to run. Thus key-off kernel commandline is
  good enough for now, but may require changes in the future.

  [Other Info]

  @ Kernel team, also see https://trello.com/c/JbomiFOe

  https://lists.ubuntu.com/archives/kernel-team/2021-June/121384.html

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

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

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

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

-- 
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:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  Confirmed

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 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed

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

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

-- 
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:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  Confirmed

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 1847982] Re: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E/F/G

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

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

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

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

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

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

  Failed on instance:
* Standard_GS2
* Standard_D16s_v3

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

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

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

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

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

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

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

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

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

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

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

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

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

  Failed on instance:
* Standard_GS2
* Standard_D16s_v3

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

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

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

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

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

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

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

Sent patch to upstream (LTP):
https://lists.linux.it/pipermail/ltp/2021-June/023254.html

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

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

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

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

  Failed on instance:
* Standard_GS2
* Standard_D16s_v3

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

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

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

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

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

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

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

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

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

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

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

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

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

  Failed on instance:
* Standard_GS2
* Standard_D16s_v3

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

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

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

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

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

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

[Kernel-packages] [Bug 1929444] Re: SD card initialization on insertion fails