[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-10-07 Thread AceLan Kao
Could you try this test kernel to see if it helps.
I applied one commit[1] on top of focal kernel master-next branch
https://people.canonical.com/~acelan/bugs/lp1874464

1. https://patchwork.ozlabs.org/project/linux-
pci/patch/20201007132808.647589-1-ian.kuml...@gmail.com/

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

Title:
  NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Groovy:
  Confirmed

Bug description:
  Running focal on a desktop, I accidentally clicked "Enable networking"
  in nm-applet, disabling my networking.  When I clicked it again to
  reenable it, my networking did not return.  After unsuccessfully
  poking at it for a while, I rebooted and saw the below (and still no
  networking).  `rmmod r8169; modprobe r8169` had no (apparent) effect,
  nor did further reboots.  I rebooted onto two different kernels, both
  exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic.

  I was finally only able to restore networking by _rebooting into
  Windows_ and then rebooting back into Ubuntu.

  (My supposition is that NetworkManager/the kernel set *waves hands*
  something on the network card that persists across boots when it was
  disabled, and that wasn't correctly unset when I reenabled networking
  (or on following boots), but Windows _does_ correctly handle that case
  on boot, and reset it to a working state.)

  Apr 23 10:07:43 surprise kernel: [ cut here ]
  Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit 
queue 0 timed out
  Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260
  Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_>
  Apr 23 10:07:43 surprise kernel:  autofs4 btrfs xor zstd_compress raid6_pq 
libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj 
hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km>
  Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P 
  OE 5.4.0-26-generic #30-Ubuntu
  Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. 
B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019
  Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260
  Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 
e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 
3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7
  Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286
  Apr 23 10:07:43 surprise kernel: RAX:  RBX: 8a7578b00400 
RCX: 
  Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 
RDI: 0300
  Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 
R09: 0004
  Apr 23 10:07:43 surprise kernel: R10:  R11: 0001 
R12: 0001
  Apr 23 10:07:43 surprise kernel: R13:  R14: 8a758cadc480 
R15: 8a758cadc000
  Apr 23 10:07:43 surprise kernel: FS:  () 
GS:8a758ee4() knlGS:
  Apr 23 10:07:43 surprise kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 
CR4: 003406e0
  Apr 23 10:07:43 surprise kernel: Call Trace:
  Apr 23 10:07:43 surprise kernel:  
  Apr 23 10:07:43 surprise kernel:  ? pfifo_fast_enqueue+0x150/0x150
  Apr 23 10:07:43 surprise kernel:  call_timer_fn+0x32/0x130
  Apr 23 10:07:43 surprise kernel:  __run_timers.part.0+0x180/0x280
  Apr 23 10:07:43 surprise kernel:  ? tick_sched_handle+0x33/0x60
  Apr 23 10:07:43 surprise kernel:  ? tick_sched_timer+0x3d/0x80
  Apr 23 10:07:43 surprise kernel:  ? ktime_get+0x3e/0xa0
  Apr 23 10:07:43 surprise kernel:  run_timer_softirq+0x2a/0x50
  Apr 23 10:07:43 surprise kernel:  __do_softirq+0xe1/0x2d6
  Apr 23 10:07:43 surprise kernel:  ? hrtimer_interrupt+0x13b/0x220
  Apr 23 10:07:43 surprise kernel:  irq_exit+0xae/0xb0
  Apr 23 10:07:43 surprise kernel:  smp_apic_timer_interrupt+0x7b/0x140
  Apr 23 10:07:43 surprise kernel:  apic_timer_interrupt+0xf/0x20
  Apr 23 10:07:43 surprise kernel:  
  Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450
  Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 
58 0f 1f 44 00 00 f6 

[Kernel-packages] [Bug 1893711] Re: [hns3-0901]add hns3_gro_complete for HW GRO process

2020-10-07 Thread Ike Panhc
Patches sent.

https://lists.ubuntu.com/archives/kernel-team/2020-October/113962.html

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

Title:
  [hns3-0901]add hns3_gro_complete for HW GRO process

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Released
Status in kunpeng920 ubuntu-20.04 series:
  Fix Released
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  kernel oops on hns3 driver when GRO is enabled.

  [Fix]
  Cherry-pick patches from upstream
  d474d88f8826 net: hns3: add hns3_gro_complete for HW GRO process
  a4d2cdcbb878 net: hns3: minor refactor for hns3_rx_checksum

  [Test]
  No known way to reproduce it in our lab. Regression test only.

  [Regression Potential]
  Patchset only affects hns3 driver. Minimal risk for other drivers and 
platform.
  Stress test on hns3 driver looks good and we also have positive
  feedback from different lab.
  Patches also in Ubuntu kernel since Eoan and no regression observed.

  
  [Bug Description]
  When a GRO packet is received by driver, the cwr field in the
  struct tcphdr needs to be checked to decide whether to set the
  SKB_GSO_TCP_ECN for skb_shinfo(skb)->gso_type.

  [Steps to Reproduce]
  1.load PF driver
  2.turn off GRO of stack, turn on HW GRO

  [Actual Results]
  [   32.597752] bond-dcn: link status definitely up for interface enp189s0f0, 
1 Mbps full duplex
  [1048422.589438] Unable to handle kernel paging request at virtual address 
80605d0c
  [1048422.597506] Mem abort info:
  [1048422.600463]   ESR = 0x9605
  [1048422.603679]   Exception class = DABT (current EL), IL = 32 bits
  [1048422.609747]   SET = 0, FnV = 0
  [1048422.612963]   EA = 0, S1PTW = 0
  [1048422.616265] Data abort info:
  [1048422.619309]   ISV = 0, ISS = 0x0005
  [1048422.623301]   CM = 0, WnR = 0
  [1048422.626431] swapper pgtable: 4k pages, 48-bit VAs, pgd = 96615bf4
  [1048422.633360] [80605d0c] *pgd=205f6003, 
*pud=
  [1048422.640465] Internal error: Oops: 9605 [#1] SMP
  [1048422.645496] Modules linked in: bonding zfs(PO) zunicode(PO) zavl(PO) 
icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) joydev input_leds 
ipmi_ssif ipmi_si ipmi_devintf shpchp ipmi_msghandler cppc_cpufreq sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 xfs btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure hibmc_drm aes_ce_blk 
aes_ce_cipher ttm realtek crc32_ce drm_kms_helper crct10dif_ce syscopyarea 
ghash_ce hisi_sas_v3_hw sysfillrect sha2_ce sysimgblt hns3 nvme hisi_sas_main 
sha256_arm64 fb_sys_fops sha1_ce drm hclge libsas nvme_core ahci megaraid_sas 
hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic
  [1048422.715911]  usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd 
aes_arm64
  [1048422.723192] Process swapper/22 (pid: 0, stack limit = 0xdc9798e5)
  [1048422.730122] CPU: 22 PID: 0 Comm: swapper/22 Tainted: P   O 
4.15.0-96-generic #97-Ubuntu
  [1048422.739297] Hardware name: Huawei TaiShan 200 (Model 2280)/BC82AMDDA, 
BIOS 1.35 04/30/2020
  [1048422.747695] pstate: 8049 (Nzcv daif +PAN -UAO)
  [1048422.752641] pc : tcp_gro_complete+0x4c/0x80
  [1048422.756988] lr : hns3_clean_rx_ring+0x63c/0x6f0 [hns3]
  [1048422.762274] sp : 09893d00
  [1048422.765746] x29: 09893d00 x28: a05de384d900
  [1048422.771207] x27: a05dc660c6c0 x26: a05dc7a6c280
  [1048422.776668] x25: 0040 x24: a05dc7a4e000
  [1048422.782130] x23: 0002 x22: 
  [1048422.787590] x21:  x20: 
  [1048422.793051] x19: a05de384d900 x18: a3bf2a70
  [1048422.798512] x17: a3b68698 x16: 08307aa0
  [1048422.803973] x15: 0d920112ac4e x14: 0c96b6405c2a0a08
  [1048422.809435] x13: 01011cc0f601 x12: 188058b201fc85fd
  [1048422.814896] x11: cd979f72c04ce5db x10: 2087e1db2087679d
  [1048422.820358] x9 : 0640004090cff807 x8 : 00450008f034d971
  [1048422.825820] x7 : 1502726647903506 x6 : 0002
  [1048422.831281] x5 : a05dc7ad0480 x4 : 0002
  [1048422.836743] x3 : 805f5d00 x2 : 0060
  [1048422.842203] x1 : 805f5f00 x0 : 80605cff
  [1048422.847665] Call trace:
  [1048422.850276]  tcp_gro_complete+0x4c/0x80
  [1048422.854274]  hns3_clean_rx_ring+0x63c/0x6f0 [hns3]
  [1048422.859217]  hns3_nic_common_poll+0x98/0x220 [hns3]
  [1048422.864247]  net_rx_action+0x160/0x3d8
  

[Kernel-packages] [Bug 1893711] Re: [hns3-0901]add hns3_gro_complete for HW GRO process

2020-10-07 Thread Ike Panhc
** Description changed:

+ [Impact]
+ kernel oops on hns3 driver when GRO is enabled.
+ 
+ [Fix]
+ Cherry-pick patches from upstream
+ d474d88f8826 net: hns3: add hns3_gro_complete for HW GRO process
+ a4d2cdcbb878 net: hns3: minor refactor for hns3_rx_checksum
+ 
+ [Test]
+ No known way to reproduce it in our lab. Regression test only.
+ 
+ [Regression Potential]
+ Patchset only affects hns3 driver. Minimal risk for other drivers and 
platform.
+ Stress test on hns3 driver looks good and we also have positive
+ feedback from different lab.
+ Patches also in Ubuntu kernel since Eoan and no regression observed.
+ 
+ 
  [Bug Description]
  When a GRO packet is received by driver, the cwr field in the
  struct tcphdr needs to be checked to decide whether to set the
  SKB_GSO_TCP_ECN for skb_shinfo(skb)->gso_type.
  
  [Steps to Reproduce]
  1.load PF driver
  2.turn off GRO of stack, turn on HW GRO
  
  [Actual Results]
  [   32.597752] bond-dcn: link status definitely up for interface enp189s0f0, 
1 Mbps full duplex
  [1048422.589438] Unable to handle kernel paging request at virtual address 
80605d0c
  [1048422.597506] Mem abort info:
  [1048422.600463]   ESR = 0x9605
  [1048422.603679]   Exception class = DABT (current EL), IL = 32 bits
  [1048422.609747]   SET = 0, FnV = 0
  [1048422.612963]   EA = 0, S1PTW = 0
  [1048422.616265] Data abort info:
  [1048422.619309]   ISV = 0, ISS = 0x0005
  [1048422.623301]   CM = 0, WnR = 0
  [1048422.626431] swapper pgtable: 4k pages, 48-bit VAs, pgd = 96615bf4
  [1048422.633360] [80605d0c] *pgd=205f6003, 
*pud=
  [1048422.640465] Internal error: Oops: 9605 [#1] SMP
  [1048422.645496] Modules linked in: bonding zfs(PO) zunicode(PO) zavl(PO) 
icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) joydev input_leds 
ipmi_ssif ipmi_si ipmi_devintf shpchp ipmi_msghandler cppc_cpufreq sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 xfs btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure hibmc_drm aes_ce_blk 
aes_ce_cipher ttm realtek crc32_ce drm_kms_helper crct10dif_ce syscopyarea 
ghash_ce hisi_sas_v3_hw sysfillrect sha2_ce sysimgblt hns3 nvme hisi_sas_main 
sha256_arm64 fb_sys_fops sha1_ce drm hclge libsas nvme_core ahci megaraid_sas 
hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic
  [1048422.715911]  usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd 
aes_arm64
  [1048422.723192] Process swapper/22 (pid: 0, stack limit = 0xdc9798e5)
  [1048422.730122] CPU: 22 PID: 0 Comm: swapper/22 Tainted: P   O 
4.15.0-96-generic #97-Ubuntu
  [1048422.739297] Hardware name: Huawei TaiShan 200 (Model 2280)/BC82AMDDA, 
BIOS 1.35 04/30/2020
  [1048422.747695] pstate: 8049 (Nzcv daif +PAN -UAO)
  [1048422.752641] pc : tcp_gro_complete+0x4c/0x80
  [1048422.756988] lr : hns3_clean_rx_ring+0x63c/0x6f0 [hns3]
  [1048422.762274] sp : 09893d00
- [1048422.765746] x29: 09893d00 x28: a05de384d900 
- [1048422.771207] x27: a05dc660c6c0 x26: a05dc7a6c280 
- [1048422.776668] x25: 0040 x24: a05dc7a4e000 
- [1048422.782130] x23: 0002 x22:  
- [1048422.787590] x21:  x20:  
- [1048422.793051] x19: a05de384d900 x18: a3bf2a70 
- [1048422.798512] x17: a3b68698 x16: 08307aa0 
- [1048422.803973] x15: 0d920112ac4e x14: 0c96b6405c2a0a08 
- [1048422.809435] x13: 01011cc0f601 x12: 188058b201fc85fd 
- [1048422.814896] x11: cd979f72c04ce5db x10: 2087e1db2087679d 
- [1048422.820358] x9 : 0640004090cff807 x8 : 00450008f034d971 
- [1048422.825820] x7 : 1502726647903506 x6 : 0002 
- [1048422.831281] x5 : a05dc7ad0480 x4 : 0002 
- [1048422.836743] x3 : 805f5d00 x2 : 0060 
- [1048422.842203] x1 : 805f5f00 x0 : 80605cff 
+ [1048422.765746] x29: 09893d00 x28: a05de384d900
+ [1048422.771207] x27: a05dc660c6c0 x26: a05dc7a6c280
+ [1048422.776668] x25: 0040 x24: a05dc7a4e000
+ [1048422.782130] x23: 0002 x22: 
+ [1048422.787590] x21:  x20: 
+ [1048422.793051] x19: a05de384d900 x18: a3bf2a70
+ [1048422.798512] x17: a3b68698 x16: 08307aa0
+ [1048422.803973] x15: 0d920112ac4e x14: 0c96b6405c2a0a08
+ [1048422.809435] x13: 01011cc0f601 x12: 188058b201fc85fd
+ [1048422.814896] x11: cd979f72c04ce5db x10: 2087e1db2087679d
+ [1048422.820358] x9 : 0640004090cff807 x8 : 00450008f034d971
+ [1048422.825820] x7 : 1502726647903506 x6 : 0002
+ [1048422.831281] x5 : a05dc7ad0480 x4 : 0002
+ [1048422.836743] x3 : 805f5d00 x2 : 0060
+ [1048422.842203] x1 : 

[Kernel-packages] [Bug 1898949] Re: ThinkBook 14-IIL can't wake from sleep by opening lid

2020-10-07 Thread Azis naufal
Is there any ssdt/dsdt patch for this?

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

Title:
  ThinkBook 14-IIL can't wake from sleep by opening lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  As the summary. My ThinkBook 14-IIL can't wake from sleep by opening lid.
  But it can sleep by closing the lid.

  Here is the output of cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  XHC S4*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*enabled   pci::00:1c.0
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*enabled   pci::00:1c.4
  PXSXS4*disabled  pci::02:00.0
  RP06S4*disabled
  PXSXS4*disabled
  RP07S4*disabled
  PXSXS4*disabled
  RP08S4*disabled
  PXSXS4*disabled
  RP09S5*enabled   pci::00:1d.0
  PXSXS4*disabled  pci::03:00.0
  RP10S4*disabled
  PXSXS4*disabled
  RP11S4*enabled   pci::00:1d.2
  PXSXS4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
  RP12S4*disabled
  PXSXS4*disabled
  RP13S4*enabled   pci::00:1d.4
  PXSXS4*disabled  pci::05:00.0
  RP14S4*disabled
  PXSXS4*disabled
  RP15S4*disabled
  PXSXS4*disabled
  RP16S4*disabled
  PXSXS4*disabled
  RP17S4*disabled
  PXSXS4*disabled
  RP18S4*disabled
  PXSXS4*disabled
  RP19S4*disabled
  PXSXS4*disabled
  RP20S4*disabled
  PXSXS4*disabled
  RP21S4*disabled
  PXSXS4*disabled
  RP22S4*disabled
  PXSXS4*disabled
  RP23S4*disabled
  PXSXS4*disabled
  RP24S4*disabled
  PXSXS4*disabled
  CNVWS4*disabled  pci::00:14.3
  TXHCS4*enabled   pci::00:0d.0
  TDM0S4*disabled
  TDM1S4*disabled
  TRP0S4*disabled
  PXSXS4*disabled
  TRP1S4*disabled
  PXSXS4*disabled
  TRP2S4*disabled
  PXSXS4*disabled
  TRP3S4*disabled
  PXSXS4*disabled
  AWACS4*enabled   platform:ACPI000E:00

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-generic 5.8.0.20.25
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oazisn 2276 F pulseaudio
   /dev/snd/pcmC0D0p:   oazisn 2276 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  8 06:01:54 2020
  InstallationDate: Installed on 2020-10-06 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
  MachineType: LENOVO 20SL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=3b2bf932-d5f1-4367-913c-30b76ab7eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN18WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN18WW:bd05/08/2020:br1.18:efr1.16:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1898949] Re: ThinkBook 14-IIL can't wake from sleep by opening lid

2020-10-07 Thread Kai-Heng Feng
Ok, if this system uses legacy S3 then what Alex Hung said is right.
Please ask vendor for help.

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

Title:
  ThinkBook 14-IIL can't wake from sleep by opening lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  As the summary. My ThinkBook 14-IIL can't wake from sleep by opening lid.
  But it can sleep by closing the lid.

  Here is the output of cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  XHC S4*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*enabled   pci::00:1c.0
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*enabled   pci::00:1c.4
  PXSXS4*disabled  pci::02:00.0
  RP06S4*disabled
  PXSXS4*disabled
  RP07S4*disabled
  PXSXS4*disabled
  RP08S4*disabled
  PXSXS4*disabled
  RP09S5*enabled   pci::00:1d.0
  PXSXS4*disabled  pci::03:00.0
  RP10S4*disabled
  PXSXS4*disabled
  RP11S4*enabled   pci::00:1d.2
  PXSXS4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
  RP12S4*disabled
  PXSXS4*disabled
  RP13S4*enabled   pci::00:1d.4
  PXSXS4*disabled  pci::05:00.0
  RP14S4*disabled
  PXSXS4*disabled
  RP15S4*disabled
  PXSXS4*disabled
  RP16S4*disabled
  PXSXS4*disabled
  RP17S4*disabled
  PXSXS4*disabled
  RP18S4*disabled
  PXSXS4*disabled
  RP19S4*disabled
  PXSXS4*disabled
  RP20S4*disabled
  PXSXS4*disabled
  RP21S4*disabled
  PXSXS4*disabled
  RP22S4*disabled
  PXSXS4*disabled
  RP23S4*disabled
  PXSXS4*disabled
  RP24S4*disabled
  PXSXS4*disabled
  CNVWS4*disabled  pci::00:14.3
  TXHCS4*enabled   pci::00:0d.0
  TDM0S4*disabled
  TDM1S4*disabled
  TRP0S4*disabled
  PXSXS4*disabled
  TRP1S4*disabled
  PXSXS4*disabled
  TRP2S4*disabled
  PXSXS4*disabled
  TRP3S4*disabled
  PXSXS4*disabled
  AWACS4*enabled   platform:ACPI000E:00

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-generic 5.8.0.20.25
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oazisn 2276 F pulseaudio
   /dev/snd/pcmC0D0p:   oazisn 2276 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  8 06:01:54 2020
  InstallationDate: Installed on 2020-10-06 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
  MachineType: LENOVO 20SL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=3b2bf932-d5f1-4367-913c-30b76ab7eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN18WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN18WW:bd05/08/2020:br1.18:efr1.16:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1898949] Re: ThinkBook 14-IIL can't wake from sleep by opening lid

2020-10-07 Thread Azis naufal
No, there is no Windows/Linux option in BIOS/UEFI setting.
There is only OS Optimized Default option with enabled for windows 8 or later. 
and disabled for older OS.

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

Title:
  ThinkBook 14-IIL can't wake from sleep by opening lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  As the summary. My ThinkBook 14-IIL can't wake from sleep by opening lid.
  But it can sleep by closing the lid.

  Here is the output of cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  XHC S4*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*enabled   pci::00:1c.0
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*enabled   pci::00:1c.4
  PXSXS4*disabled  pci::02:00.0
  RP06S4*disabled
  PXSXS4*disabled
  RP07S4*disabled
  PXSXS4*disabled
  RP08S4*disabled
  PXSXS4*disabled
  RP09S5*enabled   pci::00:1d.0
  PXSXS4*disabled  pci::03:00.0
  RP10S4*disabled
  PXSXS4*disabled
  RP11S4*enabled   pci::00:1d.2
  PXSXS4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
  RP12S4*disabled
  PXSXS4*disabled
  RP13S4*enabled   pci::00:1d.4
  PXSXS4*disabled  pci::05:00.0
  RP14S4*disabled
  PXSXS4*disabled
  RP15S4*disabled
  PXSXS4*disabled
  RP16S4*disabled
  PXSXS4*disabled
  RP17S4*disabled
  PXSXS4*disabled
  RP18S4*disabled
  PXSXS4*disabled
  RP19S4*disabled
  PXSXS4*disabled
  RP20S4*disabled
  PXSXS4*disabled
  RP21S4*disabled
  PXSXS4*disabled
  RP22S4*disabled
  PXSXS4*disabled
  RP23S4*disabled
  PXSXS4*disabled
  RP24S4*disabled
  PXSXS4*disabled
  CNVWS4*disabled  pci::00:14.3
  TXHCS4*enabled   pci::00:0d.0
  TDM0S4*disabled
  TDM1S4*disabled
  TRP0S4*disabled
  PXSXS4*disabled
  TRP1S4*disabled
  PXSXS4*disabled
  TRP2S4*disabled
  PXSXS4*disabled
  TRP3S4*disabled
  PXSXS4*disabled
  AWACS4*enabled   platform:ACPI000E:00

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-generic 5.8.0.20.25
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oazisn 2276 F pulseaudio
   /dev/snd/pcmC0D0p:   oazisn 2276 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  8 06:01:54 2020
  InstallationDate: Installed on 2020-10-06 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
  MachineType: LENOVO 20SL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=3b2bf932-d5f1-4367-913c-30b76ab7eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN18WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN18WW:bd05/08/2020:br1.18:efr1.16:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1898949] Re: ThinkBook 14-IIL can't wake from sleep by opening lid

2020-10-07 Thread Kai-Heng Feng
[  179.953721] PM: suspend entry (deep)

I thought laptop this new should use s2idle...

Is there a Windows/Linux option in BIOS setup? Please choose Windows
over Linux.

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

Title:
  ThinkBook 14-IIL can't wake from sleep by opening lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  As the summary. My ThinkBook 14-IIL can't wake from sleep by opening lid.
  But it can sleep by closing the lid.

  Here is the output of cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  XHC S4*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*enabled   pci::00:1c.0
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*enabled   pci::00:1c.4
  PXSXS4*disabled  pci::02:00.0
  RP06S4*disabled
  PXSXS4*disabled
  RP07S4*disabled
  PXSXS4*disabled
  RP08S4*disabled
  PXSXS4*disabled
  RP09S5*enabled   pci::00:1d.0
  PXSXS4*disabled  pci::03:00.0
  RP10S4*disabled
  PXSXS4*disabled
  RP11S4*enabled   pci::00:1d.2
  PXSXS4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
  RP12S4*disabled
  PXSXS4*disabled
  RP13S4*enabled   pci::00:1d.4
  PXSXS4*disabled  pci::05:00.0
  RP14S4*disabled
  PXSXS4*disabled
  RP15S4*disabled
  PXSXS4*disabled
  RP16S4*disabled
  PXSXS4*disabled
  RP17S4*disabled
  PXSXS4*disabled
  RP18S4*disabled
  PXSXS4*disabled
  RP19S4*disabled
  PXSXS4*disabled
  RP20S4*disabled
  PXSXS4*disabled
  RP21S4*disabled
  PXSXS4*disabled
  RP22S4*disabled
  PXSXS4*disabled
  RP23S4*disabled
  PXSXS4*disabled
  RP24S4*disabled
  PXSXS4*disabled
  CNVWS4*disabled  pci::00:14.3
  TXHCS4*enabled   pci::00:0d.0
  TDM0S4*disabled
  TDM1S4*disabled
  TRP0S4*disabled
  PXSXS4*disabled
  TRP1S4*disabled
  PXSXS4*disabled
  TRP2S4*disabled
  PXSXS4*disabled
  TRP3S4*disabled
  PXSXS4*disabled
  AWACS4*enabled   platform:ACPI000E:00

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-generic 5.8.0.20.25
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oazisn 2276 F pulseaudio
   /dev/snd/pcmC0D0p:   oazisn 2276 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  8 06:01:54 2020
  InstallationDate: Installed on 2020-10-06 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
  MachineType: LENOVO 20SL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=3b2bf932-d5f1-4367-913c-30b76ab7eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN18WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN18WW:bd05/08/2020:br1.18:efr1.16:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1893711] Re: [hns3-0901]add hns3_gro_complete for HW GRO process

2020-10-07 Thread Ike Panhc
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

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

Title:
  [hns3-0901]add hns3_gro_complete for HW GRO process

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Released
Status in kunpeng920 ubuntu-20.04 series:
  Fix Released
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Bug Description]
  When a GRO packet is received by driver, the cwr field in the
  struct tcphdr needs to be checked to decide whether to set the
  SKB_GSO_TCP_ECN for skb_shinfo(skb)->gso_type.

  [Steps to Reproduce]
  1.load PF driver
  2.turn off GRO of stack, turn on HW GRO

  [Actual Results]
  [   32.597752] bond-dcn: link status definitely up for interface enp189s0f0, 
1 Mbps full duplex
  [1048422.589438] Unable to handle kernel paging request at virtual address 
80605d0c
  [1048422.597506] Mem abort info:
  [1048422.600463]   ESR = 0x9605
  [1048422.603679]   Exception class = DABT (current EL), IL = 32 bits
  [1048422.609747]   SET = 0, FnV = 0
  [1048422.612963]   EA = 0, S1PTW = 0
  [1048422.616265] Data abort info:
  [1048422.619309]   ISV = 0, ISS = 0x0005
  [1048422.623301]   CM = 0, WnR = 0
  [1048422.626431] swapper pgtable: 4k pages, 48-bit VAs, pgd = 96615bf4
  [1048422.633360] [80605d0c] *pgd=205f6003, 
*pud=
  [1048422.640465] Internal error: Oops: 9605 [#1] SMP
  [1048422.645496] Modules linked in: bonding zfs(PO) zunicode(PO) zavl(PO) 
icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) joydev input_leds 
ipmi_ssif ipmi_si ipmi_devintf shpchp ipmi_msghandler cppc_cpufreq sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 xfs btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure hibmc_drm aes_ce_blk 
aes_ce_cipher ttm realtek crc32_ce drm_kms_helper crct10dif_ce syscopyarea 
ghash_ce hisi_sas_v3_hw sysfillrect sha2_ce sysimgblt hns3 nvme hisi_sas_main 
sha256_arm64 fb_sys_fops sha1_ce drm hclge libsas nvme_core ahci megaraid_sas 
hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic
  [1048422.715911]  usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd 
aes_arm64
  [1048422.723192] Process swapper/22 (pid: 0, stack limit = 0xdc9798e5)
  [1048422.730122] CPU: 22 PID: 0 Comm: swapper/22 Tainted: P   O 
4.15.0-96-generic #97-Ubuntu
  [1048422.739297] Hardware name: Huawei TaiShan 200 (Model 2280)/BC82AMDDA, 
BIOS 1.35 04/30/2020
  [1048422.747695] pstate: 8049 (Nzcv daif +PAN -UAO)
  [1048422.752641] pc : tcp_gro_complete+0x4c/0x80
  [1048422.756988] lr : hns3_clean_rx_ring+0x63c/0x6f0 [hns3]
  [1048422.762274] sp : 09893d00
  [1048422.765746] x29: 09893d00 x28: a05de384d900 
  [1048422.771207] x27: a05dc660c6c0 x26: a05dc7a6c280 
  [1048422.776668] x25: 0040 x24: a05dc7a4e000 
  [1048422.782130] x23: 0002 x22:  
  [1048422.787590] x21:  x20:  
  [1048422.793051] x19: a05de384d900 x18: a3bf2a70 
  [1048422.798512] x17: a3b68698 x16: 08307aa0 
  [1048422.803973] x15: 0d920112ac4e x14: 0c96b6405c2a0a08 
  [1048422.809435] x13: 01011cc0f601 x12: 188058b201fc85fd 
  [1048422.814896] x11: cd979f72c04ce5db x10: 2087e1db2087679d 
  [1048422.820358] x9 : 0640004090cff807 x8 : 00450008f034d971 
  [1048422.825820] x7 : 1502726647903506 x6 : 0002 
  [1048422.831281] x5 : a05dc7ad0480 x4 : 0002 
  [1048422.836743] x3 : 805f5d00 x2 : 0060 
  [1048422.842203] x1 : 805f5f00 x0 : 80605cff 
  [1048422.847665] Call trace:
  [1048422.850276]  tcp_gro_complete+0x4c/0x80
  [1048422.854274]  hns3_clean_rx_ring+0x63c/0x6f0 [hns3]
  [1048422.859217]  hns3_nic_common_poll+0x98/0x220 [hns3]
  [1048422.864247]  net_rx_action+0x160/0x3d8
  [1048422.868153]  __do_softirq+0x134/0x330
  [1048422.871973]  irq_exit+0xcc/0xe0
  [1048422.875275]  __handle_domain_irq+0x6c/0xc0
  [1048422.879526]  gic_handle_irq+0x84/0x180
  [1048422.883431]  el1_irq+0xe8/0x180
  [1048422.886733] 

[Kernel-packages] [Bug 1898949] Re: ThinkBook 14-IIL can't wake from sleep by opening lid

2020-10-07 Thread Azis naufal
Hi @kaihengfeng !

I've test the kernel and the bug is still there.
Here is the output of cat /proc/acpi/wakeup


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

Title:
  ThinkBook 14-IIL can't wake from sleep by opening lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  As the summary. My ThinkBook 14-IIL can't wake from sleep by opening lid.
  But it can sleep by closing the lid.

  Here is the output of cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  XHC S4*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*enabled   pci::00:1c.0
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*enabled   pci::00:1c.4
  PXSXS4*disabled  pci::02:00.0
  RP06S4*disabled
  PXSXS4*disabled
  RP07S4*disabled
  PXSXS4*disabled
  RP08S4*disabled
  PXSXS4*disabled
  RP09S5*enabled   pci::00:1d.0
  PXSXS4*disabled  pci::03:00.0
  RP10S4*disabled
  PXSXS4*disabled
  RP11S4*enabled   pci::00:1d.2
  PXSXS4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
  RP12S4*disabled
  PXSXS4*disabled
  RP13S4*enabled   pci::00:1d.4
  PXSXS4*disabled  pci::05:00.0
  RP14S4*disabled
  PXSXS4*disabled
  RP15S4*disabled
  PXSXS4*disabled
  RP16S4*disabled
  PXSXS4*disabled
  RP17S4*disabled
  PXSXS4*disabled
  RP18S4*disabled
  PXSXS4*disabled
  RP19S4*disabled
  PXSXS4*disabled
  RP20S4*disabled
  PXSXS4*disabled
  RP21S4*disabled
  PXSXS4*disabled
  RP22S4*disabled
  PXSXS4*disabled
  RP23S4*disabled
  PXSXS4*disabled
  RP24S4*disabled
  PXSXS4*disabled
  CNVWS4*disabled  pci::00:14.3
  TXHCS4*enabled   pci::00:0d.0
  TDM0S4*disabled
  TDM1S4*disabled
  TRP0S4*disabled
  PXSXS4*disabled
  TRP1S4*disabled
  PXSXS4*disabled
  TRP2S4*disabled
  PXSXS4*disabled
  TRP3S4*disabled
  PXSXS4*disabled
  AWACS4*enabled   platform:ACPI000E:00

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-generic 5.8.0.20.25
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oazisn 2276 F pulseaudio
   /dev/snd/pcmC0D0p:   oazisn 2276 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  8 06:01:54 2020
  InstallationDate: Installed on 2020-10-06 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
  MachineType: LENOVO 20SL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=3b2bf932-d5f1-4367-913c-30b76ab7eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN18WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN18WW:bd05/08/2020:br1.18:efr1.16:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot

2020-10-07 Thread Rob Frohne
*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159

I can confirm that in 20.10 removing "quiet splash" allows it to boot,
and for me that is better anyway.

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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


[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot

2020-10-07 Thread Rob Frohne
*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159

This bug also affects me with a fresh install of Ubuntu 20.10 beta.  The
kernel is 5.8.0-20-generic.  If I hit esc when it is stuck on booting, I
can see it is waiting.  The boot message is too cryptic for me, but
maybe someone else has an idea.  I'm using a Lenovo too (Yoga 260).
Here is a photo of the boot messages.
https://photos.app.goo.gl/UxkwnF7HNQEiuPC87

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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


[Kernel-packages] [Bug 1893578] Re: Touchpad recognized as a generic mouse

2020-10-07 Thread Kai-Heng Feng
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc8/amd64/


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

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

Title:
  Touchpad recognized as a generic mouse

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  The touchpad of my "Bangho G05 Zero" laptop is recognized by "xinput
  list" as a "ImPS/2 Generic Wheel Mouse".

  I been try everything these days, but I do anything about it :(. I had
  come to the conclusion that probably is a kernel bug, it shouldn't
  recognize it at least as some kind of "generic touchpad"?

  The thing is that I can't do gestures like two-fingers scrolling and
  that is a killing drawback for me to use this laptop. There is a way
  to force the touchpad recognition with some hack? Any help will we
  much appreaciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frietziek  10837 F pulseaudio
   /dev/snd/controlC1:  frietziek  10837 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 30 18:41:02 2020
  InstallationDate: Installed on 2020-08-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: BANGHO ZERO G0505
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=455d9605-569b-45f7-94d9-a02d06677e8d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: ZERO G0505
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Fab2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd05/03/2016:svnBANGHO:pnZEROG0505:pvrZEROG0505:rvnIntelCorp.:rnZEROG0505:rvrFab2:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: SharkBay System
  dmi.product.name: ZERO G0505
  dmi.product.sku: ZERO G0505
  dmi.product.version: ZERO G0505
  dmi.sys.vendor: BANGHO

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

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


[Kernel-packages] [Bug 1893564] Re: Kernel issue and then system freeze when USB device goes to sleep

2020-10-07 Thread Kai-Heng Feng
Please discuss this bug at linux-usb mailing list, 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/1893564

Title:
  Kernel issue and then system freeze when USB device goes to sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This issue is very closely related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143

  I have a microcontroller plugged into a USB port, doing CDC-ACM. I
  have either Arduino or Cutecom open with a serial terminal to the
  device. After some idle time the microcontroller will go into sleep
  mode and therefore usb will stop working. On previous versions of
  Ubuntu the serial port will close and the Arduino or Cutecom terminal
  will be notified and closed too. On Ubuntu 20.04 this does not happen,
  and the UI will lock up. After some time the entire Gnome session will
  lock up and I need to force power cycle my computer.

  I have kept dmesg tailing in a terminal when this happens and I see
  the following log:


  [  +0.235966] usb 2-2: new full-speed USB device number 9 using xhci_hcd
  [  +0.148705] usb 2-2: config 1 interface 1 altsetting 0 endpoint 0x1 has 
invalid maxpacket 128, setting to 64
  [  +0.03] usb 2-2: config 1 interface 1 altsetting 0 endpoint 0x81 has 
invalid maxpacket 128, setting to 64
  [  +0.000541] usb 2-2: New USB device found, idVendor=0483, idProduct=5740, 
bcdDevice= 2.00
  [  +0.01] usb 2-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  +0.02] usb 2-2: Product: Foxtrackr
  [  +0.01] usb 2-2: Manufacturer: IngeniousThings
  [  +0.01] usb 2-2: SerialNumber: 024737453533
  [  +0.035228] cdc_acm 2-2:1.0: ttyACM0: USB ACM device
  [  +0.000511] usbcore: registered new interface driver cdc_acm
  [  +0.01] cdc_acm: USB Abstract Control Model driver for USB modems and 
ISDN adapters
  [Aug30 17:48] D T: urb 12 failed submission with -22
  [  +0.14] BUG: unable to handle page fault for address: 00020a831230
  [  +0.03] #PF: supervisor read access in kernel mode
  [  +0.03] #PF: error_code(0x) - not-present page
  [  +0.02] PGD 0 P4D 0 
  [  +0.06] Oops:  [#1] SMP PTI
  [  +0.05] CPU: 0 PID: 593 Comm: kworker/0:4 Not tainted 5.4.0-42-generic 
#46-Ubuntu
  [  +0.02] Hardware name: Dell Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  [  +0.10] Workqueue: events acm_softint [cdc_acm]
  [  +0.08] RIP: 0010:usb_submit_urb+0x22/0x5e0
  [  +0.05] Code: 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 
41 56 41 55 41 54 53 48 83 ec 18 89 75 d0 48 85 ff 0f 84 ec 03 00 00 <48> 83 bf 
b0 00 00 00 00 49 89 fc 0f 84 db 03 00 00 48 83 7f 08 00
  [  +0.03] RSP: 0018:b49ec0347dc0 EFLAGS: 00010202
  [  +0.04] RAX:  RBX: 940aa7a87020 RCX: 

  [  +0.02] RDX: 0c00 RSI: 0c00 RDI: 
00020a831180
  [  +0.03] RBP: b49ec0347e00 R08: 940ad76178c8 R09: 
94bab5e0
  [  +0.02] R10: 94b941a8 R11: b49ec0347b58 R12: 
940aa7a877a0
  [  +0.03] R13: 000e R14: 940aa7a87020 R15: 
940ace929780
  [  +0.03] FS:  () GS:940ad760() 
knlGS:
  [  +0.03] CS:  0010 DS:  ES:  CR0: 80050033
  [  +0.02] CR2: 00020a831230 CR3: 00013f40a002 CR4: 
001606f0
  [  +0.03] Call Trace:
  [  +0.09]  acm_submit_read_urb+0x3f/0x70 [cdc_acm]
  [  +0.06]  acm_softint+0x68/0xe0 [cdc_acm]
  [  +0.07]  process_one_work+0x1eb/0x3b0
  [  +0.05]  worker_thread+0x4d/0x400
  [  +0.05]  kthread+0x104/0x140
  [  +0.05]  ? process_one_work+0x3b0/0x3b0
  [  +0.04]  ? kthread_park+0x90/0x90
  [  +0.07]  ret_from_fork+0x35/0x40
  [  +0.03] Modules linked in: cdc_acm rfcomm xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c 
bpfilter br_netfilter bridge stp llc ccm aufs cmac algif_hash algif_skcipher 
af_alg overlay bnep snd_hda_codec_hdmi binfmt_misc nls_iso8859_1 intel_rapl_msr 
mei_hdcp intel_rapl_common snd_hda_codec_realtek x86_pkg_temp_thermal 
intel_powerclamp snd_hda_codec_generic coretemp snd_hda_intel kvm_intel 
snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep kvm snd_pcm snd_seq_midi 
snd_seq_midi_event crct10dif_pclmul ghash_clmulni_intel dell_laptop 
ledtrig_audio snd_rawmidi dell_smm_hwmon i915 btusb aesni_intel btrtl 
crypto_simd btbcm btintel cryptd glue_helper intel_cstate bluetooth 
intel_rapl_perf snd_seq iwlmvm dell_wmi mac80211 dell_smbios dcdbas 
sparse_keymap wmi_bmof libarc4 dell_wmi_descriptor serio_raw snd_seq_device 
snd_timer input_leds joydev iwlwifi ecdh_generic ecc
  [  +0.54]  hid_multitouch drm_kms_helper uvcvideo i2c_algo_bit 
fb_sys_fops snd 

[Kernel-packages] [Bug 1898949] Re: ThinkBook 14-IIL can't wake from sleep by opening lid

2020-10-07 Thread Kai-Heng Feng
Newer laptops (like this one) may use EC GPE instead of PNP0C0D device
to wake up the system.

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc8/amd64/


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

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

Title:
  ThinkBook 14-IIL can't wake from sleep by opening lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  As the summary. My ThinkBook 14-IIL can't wake from sleep by opening lid.
  But it can sleep by closing the lid.

  Here is the output of cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  XHC S4*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*enabled   pci::00:1c.0
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*enabled   pci::00:1c.4
  PXSXS4*disabled  pci::02:00.0
  RP06S4*disabled
  PXSXS4*disabled
  RP07S4*disabled
  PXSXS4*disabled
  RP08S4*disabled
  PXSXS4*disabled
  RP09S5*enabled   pci::00:1d.0
  PXSXS4*disabled  pci::03:00.0
  RP10S4*disabled
  PXSXS4*disabled
  RP11S4*enabled   pci::00:1d.2
  PXSXS4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
  RP12S4*disabled
  PXSXS4*disabled
  RP13S4*enabled   pci::00:1d.4
  PXSXS4*disabled  pci::05:00.0
  RP14S4*disabled
  PXSXS4*disabled
  RP15S4*disabled
  PXSXS4*disabled
  RP16S4*disabled
  PXSXS4*disabled
  RP17S4*disabled
  PXSXS4*disabled
  RP18S4*disabled
  PXSXS4*disabled
  RP19S4*disabled
  PXSXS4*disabled
  RP20S4*disabled
  PXSXS4*disabled
  RP21S4*disabled
  PXSXS4*disabled
  RP22S4*disabled
  PXSXS4*disabled
  RP23S4*disabled
  PXSXS4*disabled
  RP24S4*disabled
  PXSXS4*disabled
  CNVWS4*disabled  pci::00:14.3
  TXHCS4*enabled   pci::00:0d.0
  TDM0S4*disabled
  TDM1S4*disabled
  TRP0S4*disabled
  PXSXS4*disabled
  TRP1S4*disabled
  PXSXS4*disabled
  TRP2S4*disabled
  PXSXS4*disabled
  TRP3S4*disabled
  PXSXS4*disabled
  AWACS4*enabled   platform:ACPI000E:00

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-generic 5.8.0.20.25
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oazisn 2276 F pulseaudio
   /dev/snd/pcmC0D0p:   oazisn 2276 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  8 06:01:54 2020
  InstallationDate: Installed on 2020-10-06 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
  MachineType: LENOVO 20SL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=3b2bf932-d5f1-4367-913c-30b76ab7eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN18WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN18WW:bd05/08/2020:br1.18:efr1.16:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1898949] Re: ThinkBook 14-IIL can't wake from sleep by opening lid

2020-10-07 Thread Azis naufal
Oh okay then. 
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/1898949

Title:
  ThinkBook 14-IIL can't wake from sleep by opening lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  As the summary. My ThinkBook 14-IIL can't wake from sleep by opening lid.
  But it can sleep by closing the lid.

  Here is the output of cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  XHC S4*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*enabled   pci::00:1c.0
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*enabled   pci::00:1c.4
  PXSXS4*disabled  pci::02:00.0
  RP06S4*disabled
  PXSXS4*disabled
  RP07S4*disabled
  PXSXS4*disabled
  RP08S4*disabled
  PXSXS4*disabled
  RP09S5*enabled   pci::00:1d.0
  PXSXS4*disabled  pci::03:00.0
  RP10S4*disabled
  PXSXS4*disabled
  RP11S4*enabled   pci::00:1d.2
  PXSXS4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
  RP12S4*disabled
  PXSXS4*disabled
  RP13S4*enabled   pci::00:1d.4
  PXSXS4*disabled  pci::05:00.0
  RP14S4*disabled
  PXSXS4*disabled
  RP15S4*disabled
  PXSXS4*disabled
  RP16S4*disabled
  PXSXS4*disabled
  RP17S4*disabled
  PXSXS4*disabled
  RP18S4*disabled
  PXSXS4*disabled
  RP19S4*disabled
  PXSXS4*disabled
  RP20S4*disabled
  PXSXS4*disabled
  RP21S4*disabled
  PXSXS4*disabled
  RP22S4*disabled
  PXSXS4*disabled
  RP23S4*disabled
  PXSXS4*disabled
  RP24S4*disabled
  PXSXS4*disabled
  CNVWS4*disabled  pci::00:14.3
  TXHCS4*enabled   pci::00:0d.0
  TDM0S4*disabled
  TDM1S4*disabled
  TRP0S4*disabled
  PXSXS4*disabled
  TRP1S4*disabled
  PXSXS4*disabled
  TRP2S4*disabled
  PXSXS4*disabled
  TRP3S4*disabled
  PXSXS4*disabled
  AWACS4*enabled   platform:ACPI000E:00

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-generic 5.8.0.20.25
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oazisn 2276 F pulseaudio
   /dev/snd/pcmC0D0p:   oazisn 2276 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  8 06:01:54 2020
  InstallationDate: Installed on 2020-10-06 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
  MachineType: LENOVO 20SL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=3b2bf932-d5f1-4367-913c-30b76ab7eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN18WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN18WW:bd05/08/2020:br1.18:efr1.16:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3

2020-10-07 Thread Mathi
@Gabirele
thanks for reporting that the problem does not happen with kernel 5.8.x
I'd like to do some testing with kernel 5.8 but that won't be atleast for a 
week. I'll report back when i test.

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

Title:
  No sound from internal card chtmax98090 - missing UCM2 files in alsa-
  ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3

Status in alsa-ucm-conf package in Ubuntu:
  Confirmed

Bug description:
  Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script)  - 
Kubuntu Focal minimal fresh installation.
  The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in 
alsamixer and it's not muted.
  I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case 
config files: no success.
  I tried and unmute speakers left and right in alsamixer: no success.

  I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the
  same issue.

  I'm running on the same rig Debian Bullseye, kernel 5.4: sound card
  output and input are both working perfectly - I noticed that in
  Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH
  (the HDMI card), while in Debian I find Pulseaudio.

  
  I attach the alsa-info.sh output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.17
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Tue Apr  7 08:55:46 2020
  InstallationDate: Installed on 2020-04-04 (2 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gabriel3937 F pulseaudio
   /dev/snd/controlC0:  gabriel3937 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-04 (3 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam
   Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Quawks
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/17/2020
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox-4.11.2
  dmi.board.name: Quawks
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr:
  dmi.product.name: Quawks
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions

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


[Kernel-packages] [Bug 1897694] Re: alsa/hda: mic doesn't work on a HP AIO machine

2020-10-07 Thread Hui Wang
Changed the description and verification done on the machine.


** Description changed:

- This bug is for tracking purpose.
+ This fix is only for oem-5.6 kernel, other kernels will merge this
+ patch with stable update. Our oem project needs this patch to be merged
+ ASAP, and I am going to have a 8 days public holiday, so sent this SRU.
+ 
+ [Impact]
+ We had a HP AIO machine, after plugging the headset and trying
+ to record sound from Mic, but can't record any sound.
+ 
+ [Fix]
+ Set the auto detect mode for Mic, this patch is going to be merged
+ by upstream, now backport it to oem-5.6 kernel.
+ 
+ [Test Case]
+ Boot the system, plug a headset and check the gnome-control-center,
+ the Mic is active in the UI, and record the sound, it could record
+ the sound.
+ 
+ 
+ [Regression Risk]
+ This patch could introduce audio jack detection problem on this HP
+ machine, but the possibility is very low, since we have tested it
+ on 3 SKUs of this machine, all worked well. And this patch only affects
+ this HP machine since it specifies the subsystem id of this machine.

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

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

Title:
  alsa/hda: mic doesn't work on a HP AIO machine

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

Bug description:
  This fix is only for oem-5.6 kernel, other kernels will merge this
  patch with stable update. Our oem project needs this patch to be merged
  ASAP, and I am going to have a 8 days public holiday, so sent this SRU.

  [Impact]
  We had a HP AIO machine, after plugging the headset and trying
  to record sound from Mic, but can't record any sound.

  [Fix]
  Set the auto detect mode for Mic, this patch is going to be merged
  by upstream, now backport it to oem-5.6 kernel.

  [Test Case]
  Boot the system, plug a headset and check the gnome-control-center,
  the Mic is active in the UI, and record the sound, it could record
  the sound.

  
  [Regression Risk]
  This patch could introduce audio jack detection problem on this HP
  machine, but the possibility is very low, since we have tested it
  on 3 SKUs of this machine, all worked well. And this patch only affects
  this HP machine since it specifies the subsystem id of this machine.

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

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


[Kernel-packages] [Bug 1898878] Re: Ubuntu slow boot

2020-10-07 Thread Daniel van Vugt
I'm not sure what to make of that. Perhaps systemd or snapd people can
help...

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

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

** Changed in: snapd (Ubuntu)
   Status: Confirmed => 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/1898878

Title:
  Ubuntu slow boot

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  My PC takes about 2 minutes till Desktop, it's just slow. I am
  attaching logs in hope of seeing if there is a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-lowlatency 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60
  Uname: Linux 5.4.0-48-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lyubo  2186 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Oct  7 17:00:19 2020
  InstallationDate: Installed on 2020-02-08 (242 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 1bbb:0195 T & A Mobile Phones Mobilebroadband
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash 
resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality 
init=/lib/systemd/systemd-bootchart vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-lowlatency N/A
   linux-backports-modules-5.4.0-48-lowlatency  N/A
   linux-firmware   1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-20 (169 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742

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

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


[Kernel-packages] [Bug 1898878] Re: Ubuntu slow boot

2020-10-07 Thread Alex Hung
Did you try "systemd-analyze time" or "systemd-analyze blame" to
identify the boot-time's bottleneck?

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

Title:
  Ubuntu slow boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My PC takes about 2 minutes till Desktop, it's just slow. I am
  attaching logs in hope of seeing if there is a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-lowlatency 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60
  Uname: Linux 5.4.0-48-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lyubo  2186 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Oct  7 17:00:19 2020
  InstallationDate: Installed on 2020-02-08 (242 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 1bbb:0195 T & A Mobile Phones Mobilebroadband
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash 
resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality 
init=/lib/systemd/systemd-bootchart vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-lowlatency N/A
   linux-backports-modules-5.4.0-48-lowlatency  N/A
   linux-firmware   1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-20 (169 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742

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

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


[Kernel-packages] [Bug 1898949] Re: ThinkBook 14-IIL can't wake from sleep by opening lid

2020-10-07 Thread Alex Hung
This is a BIOS issue and a fix is required from OEM and is not from
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/1898949

Title:
  ThinkBook 14-IIL can't wake from sleep by opening lid

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  As the summary. My ThinkBook 14-IIL can't wake from sleep by opening lid.
  But it can sleep by closing the lid.

  Here is the output of cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  XHC S4*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*enabled   pci::00:1c.0
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*enabled   pci::00:1c.4
  PXSXS4*disabled  pci::02:00.0
  RP06S4*disabled
  PXSXS4*disabled
  RP07S4*disabled
  PXSXS4*disabled
  RP08S4*disabled
  PXSXS4*disabled
  RP09S5*enabled   pci::00:1d.0
  PXSXS4*disabled  pci::03:00.0
  RP10S4*disabled
  PXSXS4*disabled
  RP11S4*enabled   pci::00:1d.2
  PXSXS4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
  RP12S4*disabled
  PXSXS4*disabled
  RP13S4*enabled   pci::00:1d.4
  PXSXS4*disabled  pci::05:00.0
  RP14S4*disabled
  PXSXS4*disabled
  RP15S4*disabled
  PXSXS4*disabled
  RP16S4*disabled
  PXSXS4*disabled
  RP17S4*disabled
  PXSXS4*disabled
  RP18S4*disabled
  PXSXS4*disabled
  RP19S4*disabled
  PXSXS4*disabled
  RP20S4*disabled
  PXSXS4*disabled
  RP21S4*disabled
  PXSXS4*disabled
  RP22S4*disabled
  PXSXS4*disabled
  RP23S4*disabled
  PXSXS4*disabled
  RP24S4*disabled
  PXSXS4*disabled
  CNVWS4*disabled  pci::00:14.3
  TXHCS4*enabled   pci::00:0d.0
  TDM0S4*disabled
  TDM1S4*disabled
  TRP0S4*disabled
  PXSXS4*disabled
  TRP1S4*disabled
  PXSXS4*disabled
  TRP2S4*disabled
  PXSXS4*disabled
  TRP3S4*disabled
  PXSXS4*disabled
  AWACS4*enabled   platform:ACPI000E:00

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-generic 5.8.0.20.25
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oazisn 2276 F pulseaudio
   /dev/snd/pcmC0D0p:   oazisn 2276 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  8 06:01:54 2020
  InstallationDate: Installed on 2020-10-06 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
  MachineType: LENOVO 20SL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=3b2bf932-d5f1-4367-913c-30b76ab7eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN18WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN18WW:bd05/08/2020:br1.18:efr1.16:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1898949] Re: ThinkBook 14-IIL can't wake from sleep by opening lid

2020-10-07 Thread Alex Hung
The ACPI's lid device "LID0" is not listed in /proc/acpi/wakeup, and it
can be the result of missing "_PRW" object in ACPI BIOS. It has only
_HID, _LID and _DSW objects such as below (extracted from acpidump.txt).

   Device (LID0)
   {
   Name (_HID, EisaId ("PNP0C0D")
   Method (_LID, 0, NotSerialized)
   {
  // skipped
   }

   Method (_DSW, 3, NotSerialized)
   {
  // skipped
   }
   }

According to ACPI spec, _PRW is required for wake such as below

7.3.13 _PRW (Power Resources for Wake)
This object evaluates to a list of power resources upon which this device 
depends for wake. It also contains additional information needed for wake, 
including wake events and sleep or soft-off state information. _PRW is only 
required for devices that have the ability to wake the system from a system 
sleeping state.

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

Title:
  ThinkBook 14-IIL can't wake from sleep by opening lid

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  As the summary. My ThinkBook 14-IIL can't wake from sleep by opening lid.
  But it can sleep by closing the lid.

  Here is the output of cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  XHC S4*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*enabled   pci::00:1c.0
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*enabled   pci::00:1c.4
  PXSXS4*disabled  pci::02:00.0
  RP06S4*disabled
  PXSXS4*disabled
  RP07S4*disabled
  PXSXS4*disabled
  RP08S4*disabled
  PXSXS4*disabled
  RP09S5*enabled   pci::00:1d.0
  PXSXS4*disabled  pci::03:00.0
  RP10S4*disabled
  PXSXS4*disabled
  RP11S4*enabled   pci::00:1d.2
  PXSXS4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
  RP12S4*disabled
  PXSXS4*disabled
  RP13S4*enabled   pci::00:1d.4
  PXSXS4*disabled  pci::05:00.0
  RP14S4*disabled
  PXSXS4*disabled
  RP15S4*disabled
  PXSXS4*disabled
  RP16S4*disabled
  PXSXS4*disabled
  RP17S4*disabled
  PXSXS4*disabled
  RP18S4*disabled
  PXSXS4*disabled
  RP19S4*disabled
  PXSXS4*disabled
  RP20S4*disabled
  PXSXS4*disabled
  RP21S4*disabled
  PXSXS4*disabled
  RP22S4*disabled
  PXSXS4*disabled
  RP23S4*disabled
  PXSXS4*disabled
  RP24S4*disabled
  PXSXS4*disabled
  CNVWS4*disabled  pci::00:14.3
  TXHCS4*enabled   pci::00:0d.0
  TDM0S4*disabled
  TDM1S4*disabled
  TRP0S4*disabled
  PXSXS4*disabled
  TRP1S4*disabled
  PXSXS4*disabled
  TRP2S4*disabled
  PXSXS4*disabled
  TRP3S4*disabled
  PXSXS4*disabled
  AWACS4*enabled   platform:ACPI000E:00

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-generic 5.8.0.20.25
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oazisn 2276 F pulseaudio
   /dev/snd/pcmC0D0p:   oazisn 2276 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  8 06:01:54 2020
  InstallationDate: Installed on 2020-10-06 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
  MachineType: LENOVO 20SL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=3b2bf932-d5f1-4367-913c-30b76ab7eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN18WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN18WW:bd05/08/2020:br1.18:efr1.16:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 

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

2020-10-07 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  ThinkBook 14-IIL can't wake from sleep by opening lid

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  As the summary. My ThinkBook 14-IIL can't wake from sleep by opening lid.
  But it can sleep by closing the lid.

  Here is the output of cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  XHC S4*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*enabled   pci::00:1c.0
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*enabled   pci::00:1c.4
  PXSXS4*disabled  pci::02:00.0
  RP06S4*disabled
  PXSXS4*disabled
  RP07S4*disabled
  PXSXS4*disabled
  RP08S4*disabled
  PXSXS4*disabled
  RP09S5*enabled   pci::00:1d.0
  PXSXS4*disabled  pci::03:00.0
  RP10S4*disabled
  PXSXS4*disabled
  RP11S4*enabled   pci::00:1d.2
  PXSXS4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
  RP12S4*disabled
  PXSXS4*disabled
  RP13S4*enabled   pci::00:1d.4
  PXSXS4*disabled  pci::05:00.0
  RP14S4*disabled
  PXSXS4*disabled
  RP15S4*disabled
  PXSXS4*disabled
  RP16S4*disabled
  PXSXS4*disabled
  RP17S4*disabled
  PXSXS4*disabled
  RP18S4*disabled
  PXSXS4*disabled
  RP19S4*disabled
  PXSXS4*disabled
  RP20S4*disabled
  PXSXS4*disabled
  RP21S4*disabled
  PXSXS4*disabled
  RP22S4*disabled
  PXSXS4*disabled
  RP23S4*disabled
  PXSXS4*disabled
  RP24S4*disabled
  PXSXS4*disabled
  CNVWS4*disabled  pci::00:14.3
  TXHCS4*enabled   pci::00:0d.0
  TDM0S4*disabled
  TDM1S4*disabled
  TRP0S4*disabled
  PXSXS4*disabled
  TRP1S4*disabled
  PXSXS4*disabled
  TRP2S4*disabled
  PXSXS4*disabled
  TRP3S4*disabled
  PXSXS4*disabled
  AWACS4*enabled   platform:ACPI000E:00

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-generic 5.8.0.20.25
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oazisn 2276 F pulseaudio
   /dev/snd/pcmC0D0p:   oazisn 2276 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  8 06:01:54 2020
  InstallationDate: Installed on 2020-10-06 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
  MachineType: LENOVO 20SL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=3b2bf932-d5f1-4367-913c-30b76ab7eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN18WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN18WW:bd05/08/2020:br1.18:efr1.16:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: aws

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

Title:
  btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

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

Bug description:
  Test failure in fallocate06 was composed by two issues, one is xfs
  fill_fs test issue addressed in bug 1865967.

  Another is this one, this is the case 2 of btrfs (fill_fs):

  tst_test.c:1290: INFO: Testing on btrfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts=''
  tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
  fallocate06.c:117: INFO: Copy-on-write is supported
  fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no
  fallocate06.c:157: PASS: write() successful
  fallocate06.c:201: PASS: Misaligned allocation works as expected
  fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) successful
  fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) cleared the correct file range
  fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962
  tst_fill_fs.c:59: INFO: write(): ENOSPC (28)
  fallocate06.c:157: PASS: write() successful
  fallocate06.c:201: PASS: Misaligned allocation works as expected
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2

  This issue can be found from X to F
  X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/
  B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/
  D - https://pastebin.ubuntu.com/p/cryTnnn5wF/
  E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/
  F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/

  Note that the hint printed in the test:
HINT: You _MAY_ be missing kernel fixes, see:
   
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e

  It something that will get printed after the test, as it's for XFS so
  it has nothing to do with this issue here.

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

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


[Kernel-packages] [Bug 1851619] Re: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4

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

Title:
  test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP
  5.3

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

Bug description:
  The test_blackhole_dev from net in ubuntu_kernel_selftests failed on
  B-GCP 5.3 (5.3.0-1007.7~18.04.1-gcp)

   # selftests: net: test_blackhole_dev.sh
   # test_blackhole_dev: [FAIL]
   not ok 13 selftests: net: test_blackhole_dev.sh

  Need to run this manually to see what's going on there.

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

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


[Kernel-packages] [Bug 1845870] Re: test_verifier from ubuntu_bpf failed on B-hwe-edge 5.3 / 5.4 ARM64

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: aws focal

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

Title:
  test_verifier from ubuntu_bpf failed on B-hwe-edge 5.3 / 5.4 ARM64

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

Bug description:
  Issue found on a Moonshot node with B-hwe-edge 5.3 kernel,
  test failed with:
#13/p valid read map access into a read-only array 2 FAIL retval 65507 != 
-29 (run 1/1)
verification time 41 usec
stack depth 8
processed 14 insns (limit 100) max_states_per_insn 0 total_states 1 
peak_states 1 mark_read 1

  This is the only test failing in this test suite:
Summary: 1547 PASSED, 0 SKIPPED, 1 FAILED

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

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


[Kernel-packages] [Bug 1797348] Re: msgstress04 test in ubuntu_ltp_syscalls failed with X-KVM

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4 aws focal sru-20200921

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

Title:
  msgstress04 test in ubuntu_ltp_syscalls failed with X-KVM

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

Bug description:
  Test failed with many "message queue mismatch" error message:
  Message queue mismatch in the reader of child group 75 for message queue 
id 545948306

  And

  <<>>
  tag=msgstress04 stime=1539249959
  cmdline="msgstress04"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  msgstress040  TINFO  :  Found 31997 available message queues
  msgstress040  TINFO  :  Using upto 1986 pids
  Message queue mismatch in the reader of child group 37 for message queue id 
524910642
  Message queue mismatch in the reader of child group 37 for message queue id 
524943411
  Message queue mismatch in the reader of child group 40 for message queue id 
525271101
  
  Child exit status = 1 from child group 37
  Message queue mismatch in the reader of child group 38 for message queue id 
526123096
  
  Child exit status = 1 from child group 39
  
  Child exit status = 1 from child group 42
  msgstress041  TFAIL  :  msgstress04.c:220: Child exit status = 1
  Message queue mismatch in the reader of child group 66 for message queue id 
543883860
  <<>>
  initiation_status="ok"
  duration=197 termination_type=exited termination_id=1 corefile=no
  cutime=575 cstime=1037
  <<>>

  
  Complete test log: https://pastebin.ubuntu.com/p/YtTXBh2tvP/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1036-kvm 4.4.0-1036.42
  ProcVersionSignature: User Name 4.4.0-1036.42-kvm 4.4.155
  Uname: Linux 4.4.0-1036-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Oct 11 09:33:08 2018
  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/1797348/+subscriptions

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


[Kernel-packages] [Bug 1865965] Re: kill11 from ubuntu_ltp_syscalls failed

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4 aws focal

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

Title:
  kill11 from ubuntu_ltp_syscalls failed

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

Bug description:
   startup='Tue Mar 3 15:46:25 2020'
   tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
   kill11.c:97: PASS: signal SIGHUP
   kill11.c:97: PASS: signal SIGINT
   kill11.c:97: PASS: signal SIGQUIT dumped core
   kill11.c:97: PASS: signal SIGILL dumped core
   kill11.c:97: PASS: signal SIGTRAP dumped core
   kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core
   kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core
   kill11.c:97: PASS: signal SIGBUS dumped core
   kill11.c:97: PASS: signal SIGFPE dumped core
   kill11.c:97: PASS: signal SIGKILL
   kill11.c:97: PASS: signal SIGUSR1
   kill11.c:97: PASS: signal SIGSEGV dumped core
   kill11.c:97: PASS: signal SIGUSR2
   kill11.c:97: PASS: signal SIGPIPE
   kill11.c:97: PASS: signal SIGALRM
   kill11.c:97: PASS: signal SIGTERM
   kill11.c:97: PASS: signal SIGSTKFLT
   kill11.c:97: PASS: signal SIGXCPU dumped core
   Test timeouted, sending SIGKILL!
   tst_test.c:1269: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
   tst_test.c:1270: BROK: Test killed! (timeout?)

   Summary:
   passed 18
   failed 0
   skipped 0
   warnings 0
   tag=kill11 stime=1583250385 dur=302 exit=exited stat=2 core=no cu=0 cs=0

  Need to see if bump the timeout threshold can help.

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

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


[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 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/1783881

Title:
  ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits
  number of processes

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  As systemd limits the number of processes, this test will fail because
  it can't fork enough processes. That is limited to when the test is
  run after logging as user 1000, then running sudo. I guess that
  logging as root may not cause this to happen.

  # ./testcases/bin/msgstress03 
  Fork failed (may be OK if under stress)
  Fork failed (may be OK if under stress)
  msgstress031  TFAIL  :  msgstress03.c:157:  Fork failed (may be OK if 
under stress)
  #

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

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

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: aws

-- 
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 1898949] [NEW] ThinkBook 14-IIL can't wake from sleep by opening lid

2020-10-07 Thread Azis naufal
Public bug reported:

Hi!

As the summary. My ThinkBook 14-IIL can't wake from sleep by opening lid.
But it can sleep by closing the lid.

Here is the output of cat /proc/acpi/wakeup

Device  S-state   Status   Sysfs node
XHC   S4*enabled   pci::00:14.0
XDCI  S4*disabled
HDAS  S4*disabled  pci::00:1f.3
RP01  S4*enabled   pci::00:1c.0
PXSX  S4*disabled
RP02  S4*disabled
PXSX  S4*disabled
RP03  S4*disabled
PXSX  S4*disabled
RP04  S4*disabled
PXSX  S4*disabled
RP05  S4*enabled   pci::00:1c.4
PXSX  S4*disabled  pci::02:00.0
RP06  S4*disabled
PXSX  S4*disabled
RP07  S4*disabled
PXSX  S4*disabled
RP08  S4*disabled
PXSX  S4*disabled
RP09  S5*enabled   pci::00:1d.0
PXSX  S4*disabled  pci::03:00.0
RP10  S4*disabled
PXSX  S4*disabled
RP11  S4*enabled   pci::00:1d.2
PXSX  S4*disabled  pci::04:00.0
*disabled  platform:rtsx_pci_sdmmc.0
RP12  S4*disabled
PXSX  S4*disabled
RP13  S4*enabled   pci::00:1d.4
PXSX  S4*disabled  pci::05:00.0
RP14  S4*disabled
PXSX  S4*disabled
RP15  S4*disabled
PXSX  S4*disabled
RP16  S4*disabled
PXSX  S4*disabled
RP17  S4*disabled
PXSX  S4*disabled
RP18  S4*disabled
PXSX  S4*disabled
RP19  S4*disabled
PXSX  S4*disabled
RP20  S4*disabled
PXSX  S4*disabled
RP21  S4*disabled
PXSX  S4*disabled
RP22  S4*disabled
PXSX  S4*disabled
RP23  S4*disabled
PXSX  S4*disabled
RP24  S4*disabled
PXSX  S4*disabled
CNVW  S4*disabled  pci::00:14.3
TXHC  S4*enabled   pci::00:0d.0
TDM0  S4*disabled
TDM1  S4*disabled
TRP0  S4*disabled
PXSX  S4*disabled
TRP1  S4*disabled
PXSX  S4*disabled
TRP2  S4*disabled
PXSX  S4*disabled
TRP3  S4*disabled
PXSX  S4*disabled
AWAC  S4*enabled   platform:ACPI000E:00

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-generic 5.8.0.20.25
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  oazisn 2276 F pulseaudio
 /dev/snd/pcmC0D0p:   oazisn 2276 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct  8 06:01:54 2020
InstallationDate: Installed on 2020-10-06 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
MachineType: LENOVO 20SL
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=3b2bf932-d5f1-4367-913c-30b76ab7eb42 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-20-generic N/A
 linux-backports-modules-5.8.0-20-generic  N/A
 linux-firmware1.190
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/08/2020
dmi.bios.release: 1.18
dmi.bios.vendor: LENOVO
dmi.bios.version: DJCN18WW
dmi.board.name: LVAC/LVAD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55726 WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ThinkBook 14-IIL
dmi.ec.firmware.release: 1.16
dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN18WW:bd05/08/2020:br1.18:efr1.16:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
dmi.product.family: Thinkbook 14-IIL
dmi.product.name: 20SL
dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
dmi.product.version: Lenovo ThinkBook 14-IIL
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug 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/1898949

Title:
  ThinkBook 14-IIL can't wake from sleep by opening lid

Status in linux package in Ubuntu:
  New

Bug description:
  Hi!

  As the summary. My ThinkBook 14-IIL can't wake from sleep by opening lid.
  But it can sleep by closing the lid.

  Here is the output of cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  XHC S4*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*enabled   pci::00:1c.0
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*enabled   pci::00:1c.4
  PXSXS4*disabled  pci::02:00.0
  RP06S4*disabled
  

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

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4 aws focal

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

Title:
  memcg_usage_in_bytes from controllers test suite in LTP failed

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

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

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

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

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


[Kernel-packages] [Bug 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed

2020-10-07 Thread Kelsey Margarete Skunberg
*** This bug is a duplicate of bug 1829984 ***
https://bugs.launchpad.net/bugs/1829984

** Tags added: 5.4 focal

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

Title:
  memcg_max_usage_in_bytes from controllers test suite in LTP failed

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

Bug description:
   startup='Wed May 22 05:58:50 2019'
   memcg_max_usage_in_bytes_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_max_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy 
to 0 failed
   memcg_max_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 
4194304
   memcg_max_usage_in_bytes_test 1 TINFO: Warming up pid: 30821
   memcg_max_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 
30821
   memcg_max_usage_in_bytes_test 1 TFAIL: memory.max_usage_in_bytes is 4325376, 
4194304 expected
   memcg_max_usage_in_bytes_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy 
to 0 failed
   memcg_max_usage_in_bytes_test 2 TCONF: mem+swap is not enabled
   memcg_max_usage_in_bytes_test 2 TINFO: Starting test 3
   sh: echo: I/O error
   memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy 
to 0 failed
   memcg_max_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 
4194304
   memcg_max_usage_in_bytes_test 2 TINFO: Warming up pid: 30855
   memcg_max_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 
30855
   memcg_max_usage_in_bytes_test 2 TFAIL: memory.max_usage_in_bytes is 4329472, 
4194304 expected
   memcg_max_usage_in_bytes_test 3 TFAIL: memory.max_usage_in_bytes is 8192, 0 
expected 
   memcg_max_usage_in_bytes_test 4 TINFO: Starting test 4
   sh: echo: I/O error
   memcg_max_usage_in_bytes_test 4 TINFO: set /dev/memcg/memory.use_hierarchy 
to 0 failed
   memcg_max_usage_in_bytes_test 4 TCONF: mem+swap is not enabled
   tag=memcg_max_usage_in_bytes stime=1558504730 dur=3 exit=exited stat=33 
core=no cu=8 cs=7

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:06:31 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/1829979/+subscriptions

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


[Kernel-packages] [Bug 1829983] Re: memcg_stat from controllers test suite in LTP failed

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4 aws focal

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

Title:
  memcg_stat from controllers test suite in LTP failed

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

Bug description:
   memcg_stat_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168
   memcg_stat_test 1 TINFO: Warming up pid: 31352
   memcg_stat_test 1 TINFO: Process is still here after warm up: 31352
   memcg_stat_test 1 TPASS: cache is 135168 as expected
   memcg_stat_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168
   memcg_stat_test 2 TINFO: Warming up pid: 31380
   memcg_stat_test 2 TINFO: Process is still here after warm up: 31380
   memcg_stat_test 2 TPASS: mapped_file is 135168 as expected
   memcg_stat_test 3 TINFO: Starting test 3
   sh: echo: I/O error
   memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096
   memcg_stat_test 3 TINFO: Warming up pid: 31409
   memcg_stat_test 3 TINFO: Process is still here after warm up: 31409
   memcg_stat_test 3 TPASS: unevictable is 4096 as expected
   memcg_stat_test 4 TINFO: Starting test 4
   sh: echo: I/O error
   memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096
   memcg_stat_test 4 TINFO: Warming up pid: 31434
   memcg_stat_test 4 TINFO: Process is still here after warm up: 31434
   memcg_stat_test 4 TPASS: unevictable is 4096 as expected
   memcg_stat_test 5 TINFO: Starting test 5
   sh: echo: I/O error
   memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected
   memcg_stat_test 6 TINFO: Starting test 6
   sh: echo: I/O error
   memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   sh: echo: I/O error
   memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected
   memcg_stat_test 7 TINFO: Starting test 7
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   memcg_stat_test 7 TINFO: Starting test 8
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10

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

[Kernel-packages] [Bug 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4 focal

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

Title:
  memcg_stat_rss from controllers in ubuntu_ltp failed

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

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

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

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

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

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

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

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

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: aws

-- 
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 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4 focal

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

Title:
  crypto_user02 in crypto from ubuntu_ltp failed

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

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1829989] Re: memcg_use_hierarchy from controllers test suite in LTP failed

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4 aws focal

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

Title:
  memcg_use_hierarchy from controllers test suite in LTP failed

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

Bug description:
  startup='Wed May 22 05:59:07 2019'
  memcg_use_hierarchy_test 1 TINFO: Starting test 1
  sh: echo: I/O error
  memcg_use_hierarchy_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 1 TPASS: process 31577 is killed
  memcg_use_hierarchy_test 2 TINFO: Starting test 2
  sh: echo: I/O error
  memcg_use_hierarchy_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 2 TFAIL: echo 1 > memory.use_hierarchy passed 
unexpectedly
  memcg_use_hierarchy_test 3 TINFO: Starting test 3
  sh: echo: I/O error
  memcg_use_hierarchy_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 3 TPASS: echo 0 > subgroup/memory.use_hierarchy 
failed as expected
  tag=memcg_use_hierarchy stime=1558504747 dur=1 exit=exited stat=1 core=no 
cu=5 cs=5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:33:33 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/1829989/+subscriptions

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


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

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4 focal

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

Title:
  getaddrinfo_01 from ipv6_lib test suite in LTP failed

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

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

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

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

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


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

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4 focal

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

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

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

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

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

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

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

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

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

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

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

-- 

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

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4 aws

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

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

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

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

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

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

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

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

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

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4 aws

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

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

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

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

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

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

   HINT: You _MAY_ be missing kernel fixes, see:

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

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

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

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

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

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


[Kernel-packages] [Bug 1891421] Re: kci_test_encap_fou() in rtnetlink.sh from kselftests/net failed with "FAIL: can't add fou port 7777, skipping test"

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: 5.4 aws focal

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

Title:
  kci_test_encap_fou() in rtnetlink.sh from kselftests/net failed with
  "FAIL: can't add fou port , skipping test"

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

Bug description:
  The kci_test_encap_fou() from kci_test_encap() in rtnetlink.sh of 
kselftests/net will fail with non-zero return value, and print:
    "FAIL: can't add fou port , skipping test"

  How to reproduce this:
   devdummy="test-dummy0"
   testns="testns"
   ip netns add "$testns"
   ip netns exec "$testns" ip link set lo up
   ip netns exec "$testns" ip link add name "$devdummy" type dummy
   ip netns exec "$testns" ip link set "$devdummy" up
   ip netns exec "$testns" ip fou add port  ipproto 47
  RTNETLINK answers: No such file or directory
  Error talking to the kernel

  This is not a regression, it's the real test result after bug 1890136
  has been fixed.

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

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


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

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: aws

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

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

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

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

  psock_snd.sh output:

  16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
  16:28:31 DEBUG| [stdout] # dgram
  16:28:31 DEBUG| [stdout] # tx: 128
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # dgram bind
  16:28:31 DEBUG| [stdout] # tx: 128
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw bind
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw qdisc bypass
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw vlan
  16:28:31 DEBUG| [stdout] # tx: 146
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw vnet hdr
  16:28:31 DEBUG| [stdout] # tx: 152
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw csum_off
  16:28:31 DEBUG| [stdout] # tx: 152
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
  16:28:31 DEBUG| [stdout] # raw min size
  16:28:31 DEBUG| [stdout] # tx: 42
  16:28:31 DEBUG| [stdout] # rx: 0
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw mtu size
  16:28:31 DEBUG| [stdout] # tx: 1514
  16:28:31 DEBUG| [stdout] # rx: 1472
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:32 DEBUG| [stdout] # dgram mtu size
  16:28:32 DEBUG| [stdout] # tx: 1500
  16:28:32 DEBUG| [stdout] # rx: 1472
  16:28:32 DEBUG| [stdout] # OK
  16:28:32 DEBUG| [stdout] # 
  16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails)
  16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive)
  16:28:32 DEBUG| [stdout] # tx: 14
  16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable
  16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL)
  16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
  16:28:32 DEBUG| [stdout] # raw gso min size
  16:28:32 DEBUG| [stdout] # tx: 1525
  16:28:32 DEBUG| [stdout] # rx: 1473
  16:28:32 DEBUG| [stdout] # OK
  16:28:32 DEBUG| [stdout] # 
  16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails)
  16:28:32 DEBUG| [stdout] # tx: 1524
  16:28:32 DEBUG| [stdout] # rx: 1472
  16:28:32 DEBUG| [stdout] # OK
  16:28:32 DEBUG| [stdout] # 
  16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # exit=1

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

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1851619] Re: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags added: focal

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

Title:
  test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP
  5.3

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

Bug description:
  The test_blackhole_dev from net in ubuntu_kernel_selftests failed on
  B-GCP 5.3 (5.3.0-1007.7~18.04.1-gcp)

   # selftests: net: test_blackhole_dev.sh
   # test_blackhole_dev: [FAIL]
   not ok 13 selftests: net: test_blackhole_dev.sh

  Need to run this manually to see what's going on there.

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

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


[Kernel-packages] [Bug 1805806] Re: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64

2020-10-07 Thread Kelsey Margarete Skunberg
** Tags removed: sru-20200106
** Tags added: sru-2020010

** Tags added: aws focal

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

Title:
  test_maps in ubuntu_bpf failed with "Failed sockmap unexpected
  timeout" on D ARM64

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix

Bug description:
  This issue can be found on 2 different ARM64 node, TunderX Cavium node
  "starmie" and Moonshot "ms10-34-mcdivittB0-kernel"

  Running test_maps bpf test..
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Failed sockmap unexpected timeout

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: User 

[Kernel-packages] [Bug 1883261] Re: [linux-azure] Two Fixes For kdump Over Network

2020-10-07 Thread Kelsey Margarete Skunberg
** Description changed:

- 
  [Impact]
  
  Microsoft would like to request two kdump related fixes in all releases
  supported on Azure.  The two commits are:
  
  c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
  83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release 
resource properly")
  
  These are in the virtual PCI driver for Hyper-V.  The customer visible
  symptom is that the network is not functional in the kdump kernel, so
  the dump file must be stored on the local disk and cannot be written
  over the network.
  
  The problem only occurs when Accelerated Networking is enabled.  It’s a
  relatively obscure scenario, which is why the problem has not surfaced
  before now.  But we have an important customer who wants the “dump-file-
  over-the-network” functionality to work.
  
  [Test Case]
  
  - Apply requested patches and boot into updated kernel
  - Verify Accelerated Networking is enabled
  - Set up kdump
- - configure kdump to use SSH 
+ - configure kdump to use SSH
  - Test the crash dump mechanism and verify the kernel crash dump appears on 
the selected remote server
  
  Further details for setting up kdump through testing can be found here:
  https://ubuntu.com/server/docs/kernel-crash-dump
  
- 
  [Regression Potential]
  
+ Patches are only targeted to azure kernels.
  
- Build & boot tested. Verified kdump works as intended over SSH after patches 
are applied. 
+ Patches are desgiend to release allocated resources remaining after
+ error cases in hv_pci_probe() or PCI devices not being shut down
+ properly. if those resources are still not correctly released, then
+ entering D0 state in kdump kernel could continue to fail.
+ 
+ Potential for finding regression with freeing resources or still failing to 
enter D0 state in the kdump kernel even after all resources have been
+ released.
+ 
+ Build & boot tested. Verified kdump works as intended over SSH after
+ patches are applied.
  
  Both 5.4 and 4.15 test kernels were sent to Microsoft. Both kernels
  signed off on and verified to resolve problem.

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

Title:
  [linux-azure] Two Fixes For kdump Over Network

Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Bionic:
  New
Status in linux-azure source package in Focal:
  New

Bug description:
  [Impact]

  Microsoft would like to request two kdump related fixes in all
  releases supported on Azure.  The two commits are:

  c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
  83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release 
resource properly")

  These are in the virtual PCI driver for Hyper-V.  The customer visible
  symptom is that the network is not functional in the kdump kernel, so
  the dump file must be stored on the local disk and cannot be written
  over the network.

  The problem only occurs when Accelerated Networking is enabled.  It’s
  a relatively obscure scenario, which is why the problem has not
  surfaced before now.  But we have an important customer who wants the
  “dump-file-over-the-network” functionality to work.

  [Test Case]

  - Apply requested patches and boot into updated kernel
  - Verify Accelerated Networking is enabled
  - Set up kdump
  - configure kdump to use SSH
  - Test the crash dump mechanism and verify the kernel crash dump appears on 
the selected remote server

  Further details for setting up kdump through testing can be found here:
  https://ubuntu.com/server/docs/kernel-crash-dump

  [Regression Potential]

  Patches are only targeted to azure kernels.

  Patches are desgiend to release allocated resources remaining after
  error cases in hv_pci_probe() or PCI devices not being shut down
  properly. if those resources are still not correctly released, then
  entering D0 state in kdump kernel could continue to fail.

  Potential for finding regression with freeing resources or still failing to 
enter D0 state in the kdump kernel even after all resources have been
  released.

  Build & boot tested. Verified kdump works as intended over SSH after
  patches are applied.

  Both 5.4 and 4.15 test kernels were sent to Microsoft. Both kernels
  signed off on and verified to resolve problem.

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

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


[Kernel-packages] [Bug 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome

2020-10-07 Thread Mike Gao
Hi,

The wifi disconnect happened again today.

I dmesg'ed while it happened. attached below

[249806.930668] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[249807.047016] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[249807.112858] iwlwifi :00:14.3: FW already configured (0) - re-configuring
[249807.122092] iwlwifi :00:14.3: BIOS contains WGDS but no WRDS
[256815.224281] iwlwifi :00:14.3: expected hw-decrypted unicast frame for 
station
[256815.224291] iwlwifi :00:14.3: expected hw-decrypted unicast frame for 
station
[256815.224296] iwlwifi :00:14.3: expected hw-decrypted unicast frame for 
station
[256815.224303] iwlwifi :00:14.3: expected hw-decrypted unicast frame for 
station
[256815.224308] iwlwifi :00:14.3: expected hw-decrypted unicast frame for 
station
[256815.224325] iwlwifi :00:14.3: expected hw-decrypted unicast frame for 
station
[279334.498057] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[279334.707102] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[279334.791802] iwlwifi :00:14.3: FW already configured (0) - re-configuring
[279334.807193] iwlwifi :00:14.3: BIOS contains WGDS but no WRDS
[332511.549652] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[332511.665100] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[332511.731404] iwlwifi :00:14.3: FW already configured (0) - re-configuring
[332511.743198] iwlwifi :00:14.3: BIOS contains WGDS but no WRDS
[345594.975773] iwlwifi :00:14.3: expected hw-decrypted unicast frame for 
station
[345594.975810] iwlwifi :00:14.3: expected hw-decrypted unicast frame for 
station
[345594.975938] iwlwifi :00:14.3: expected hw-decrypted unicast frame for 
station
[345594.976045] iwlwifi :00:14.3: expected hw-decrypted unicast frame for 
station
[345594.976224] iwlwifi :00:14.3: expected hw-decrypted unicast frame for 
station
[345594.976285] iwlwifi :00:14.3: expected hw-decrypted unicast frame for 
station

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

Title:
  Internet disconnected unexpectly + Xorg freeze while watching html5
  video in Chrome

Status in linux package in Ubuntu:
  In Progress

Bug description:
  A few issues:

  1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1,
  the system sometimes gets disconnected with the network and I get the
  following error in syslog:

  iwlwifi: BIOS contains WGDS but no WRDS

  It is unclear if this is the cause of the problem, but this is likely
  related to kernel.

  2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will
  sometimes cause xorg freeze. The exact cause is unknown. (Mouse,
  control all freeze for 5-10 seconds)

  3) After Wake up from sleep got the following error on screen

  sof-audio-pci error: no reply expected, received 0x0
  iwlwifi: BIOS contains WGDS but no WRDS

  4) After wake up from a long sleep session, sometimes chrome will not
  render web page correctly or even freeze. It is unclear if its a
  Chrome problem, or a Nvidia problem, or a Kernel Problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-47-generic 5.4.0-47.51
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gao1931 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 13 09:14:36 2020
  InstallationDate: Installed on 2020-08-25 (19 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Inspiron 7591
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-47-generic N/A
   linux-backports-modules-5.4.0-47-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0JKGD4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7591
  dmi.product.sku: 0923
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867

To manage notifications about this 

[Kernel-packages] [Bug 1893817] Re: aws: enable PCI write-combine for arm64

2020-10-07 Thread Kamal Mostafa
** Changed in: linux-aws (Ubuntu Bionic)
   Status: Won't Fix => In Progress

** Changed in: linux-aws (Ubuntu Focal)
   Status: Won't Fix => In Progress

** Changed in: linux-aws (Ubuntu Groovy)
   Status: Won't Fix => In Progress

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

Title:
  aws: enable PCI write-combine for arm64

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress
Status in linux-aws source package in Focal:
  In Progress
Status in linux-aws source package in Groovy:
  In Progress

Bug description:
  To improve PCI performance on certain arm64 AWS instance types, enable
  arch_can_pci_mmap_wc() via the patch:

  From: Clint Sbisa 
  Subject: [PATCH] arm64: Enable PCI write-combine resources under sysfs

  https://lore.kernel.org/linux-
  pci/20200831151827.pumm2p54fyj7f...@amazon.com/

  --

  [Impact]

   * AWS requires PCI-write-combine be enabled for arm64 via this one-
  line patch, to effect a significant performance improvement on certain
  AWS arm64 instance types.

   * After considerable discussion, upstream indicates that this patch
  will be accepted into mainline[0] once additional documentation
  details get added to the commit description.

   * Applying this patch to linux-aws affects only AWS arm64 instance
  types.

  [Test Case]

   * Has been performance-tested by AWS; smoke-tested by me.

  [Regression Potential]

   * Low.

  [0] https://lore.kernel.org/linux-
  pci/20200917140116.ga4...@e121166-lin.cambridge.arm.com/

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

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


[Kernel-packages] [Bug 1888779] Re: Can't boot with Linux 5.4.0.*

2020-10-07 Thread andrybak
** Description changed:

  When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked
- 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40
- and 5.4.0.38).
+ 5.4.0.42, 5.4.0-48 and two uncertain previous versions, something like
+ 5.4.0.40 and 5.4.0.38).
  
  The laptop stays at a black screen with the following printed
  (disclaimer: typed manually from a low quality photo of the screen---
  typos and mistakes expected):
  
  [   69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
t
  ype=Physical Layer, (Receiver ID)
  [   69.258377] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mas
  k=0001/2000
  [   69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [   69.254733] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mask=0001/2000
  [   69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP
  
- 
- See attachments for good quality photo of the screen.
+ See jpg attachments for photos of the screen.
  
  Notes
  -
  Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text 
as above is shown for a brief moment.
  
  Minimum attachment
  --
  Output of "sudo lspci -vnvn" is attached.
  
  $ cat /proc/version_signature
  Ubuntu 5.3.0-51.44-generic 5.3.18
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrei 2258 F pulseaudio
   /dev/snd/controlC1:  andrei 2258 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: KDE neon 20.04
  HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab
  InstallationDate: Installed on 2017-12-26 (940 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.4
  dmi.board.name: 0DRPKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

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

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

Title:
  Can't boot with Linux 5.4.0.*

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked
  5.4.0.42, 5.4.0-48 and two uncertain previous versions, something like
  5.4.0.40 and 5.4.0.38).

  The laptop stays at a black screen with the following printed
  (disclaimer: typed manually from a low quality photo of the screen---
  typos and mistakes expected):

  [   69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
t
  ype=Physical Layer, (Receiver ID)
  [   69.258377] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mas
  k=0001/2000
  [   69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [   69.254733] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mask=0001/2000
  [   69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP

  See jpg attachments for photos of the screen.

  Notes
  -
  Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text 
as above is shown for a brief moment.

  Minimum attachment
  --
  Output of "sudo lspci -vnvn" is attached.

  $ 

[Kernel-packages] [Bug 1893817] Re: aws: enable PCI write-combine for arm64

2020-10-07 Thread Kamal Mostafa
Upstream resolution: https://lore.kernel.org/linux-
pci/20200917140116.ga4...@e121166-lin.cambridge.arm.com/

TL;dr "If that's the case we can go ahead and merge this patch with a
reworded commit log [...]  Clint, please reword the commit and resend,
not sure we can hit v5.10 but we shall try."

** Description changed:

- To improve PCI performance on arm64 AWS instances, enable
+ To improve PCI performance on certain arm64 AWS instance types, enable
  arch_can_pci_mmap_wc() via the patch:
  
- From: Clint Sbisa 
- Subject: [PATCH] arm64: Enable PCI write-combine resources under sysfs
+ From: Clint Sbisa 
+ Subject: [PATCH] arm64: Enable PCI write-combine resources under sysfs
  
- https://lore.kernel.org/linux-
+ https://lore.kernel.org/linux-
  pci/20200831151827.pumm2p54fyj7f...@amazon.com/
+ 
+ --
+ 
+ [Impact]
+ 
+  * AWS requires PCI-write-combine be enabled for arm64 via this one-line
+ patch, to effect a significant performance improvement on certain AWS
+ arm64 instance types.
+ 
+  * After considerable discussion, upstream indicates that this patch
+ will be accepted into mainline[0] once additional documentation details
+ get added to the commit description.
+ 
+  * Applying this patch to linux-aws affects only AWS arm64 instance
+ types.
+ 
+ [Test Case]
+ 
+  * Has been performance-tested by AWS; smoke-tested by me.
+ 
+ [Regression Potential]
+ 
+  * Low.
+ 
+ [0] https://lore.kernel.org/linux-
+ pci/20200917140116.ga4...@e121166-lin.cambridge.arm.com/

** Changed in: linux-aws (Ubuntu)
   Importance: Medium => High

** Changed in: linux-aws (Ubuntu Bionic)
   Importance: Medium => High

** Changed in: linux-aws (Ubuntu Groovy)
   Importance: Medium => High

** Changed in: linux-aws (Ubuntu Focal)
   Importance: Medium => High

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

Title:
  aws: enable PCI write-combine for arm64

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-aws source package in Bionic:
  Won't Fix
Status in linux-aws source package in Focal:
  Won't Fix
Status in linux-aws source package in Groovy:
  Won't Fix

Bug description:
  To improve PCI performance on certain arm64 AWS instance types, enable
  arch_can_pci_mmap_wc() via the patch:

  From: Clint Sbisa 
  Subject: [PATCH] arm64: Enable PCI write-combine resources under sysfs

  https://lore.kernel.org/linux-
  pci/20200831151827.pumm2p54fyj7f...@amazon.com/

  --

  [Impact]

   * AWS requires PCI-write-combine be enabled for arm64 via this one-
  line patch, to effect a significant performance improvement on certain
  AWS arm64 instance types.

   * After considerable discussion, upstream indicates that this patch
  will be accepted into mainline[0] once additional documentation
  details get added to the commit description.

   * Applying this patch to linux-aws affects only AWS arm64 instance
  types.

  [Test Case]

   * Has been performance-tested by AWS; smoke-tested by me.

  [Regression Potential]

   * Low.

  [0] https://lore.kernel.org/linux-
  pci/20200917140116.ga4...@e121166-lin.cambridge.arm.com/

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

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


[Kernel-packages] [Bug 1898781] Re: AWS: enable FPGA support in amd64 AWS kernels

2020-10-07 Thread Kamal Mostafa
** Description changed:

  CONFIG_FPGA needs to be enabled in linux-aws amd64 kernels (thereby
  supplying the fpga-mgr module), to support the AWS F1 instance type.
  
  Delivering the fpga-mgr module via the 'linux-modules-extras' package is
  acceptable.
  
  This config change only needs to be specifically applied to linux-
  aws/focal, since:
  
    linux-aws/bionic (aws-5.4) will pick it up from focal;
    linux-aws-groovy already has it enabled;
    linux-aws-xenial cannot support F1 anyway.
+ 
+ --
+ 
+ [Impact]
+ 
+  * Since fpga-mgr is inadvertently omitted from linux-aws, use of the F1
+ instance type requires the user to manually install linux-virtual or
+ linux-generic, which is an annoyance.
+ 
+  * This patch just enables the module in linux-aws as we do for other
+ kernels.
+ 
+  * Fwiw, fpga-mgr is actually (needlessly) already enabled for linux-
+ aws/arm64 but disabled for linux-aws/amd64 (where its needed for F1).
+ 
+ [Test Case]
+ 
+  * Install the linux-modules-extras package; modprobe fpga-mgr.
+ 
+ [Regression Potential]
+ 
+  * None.

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

Title:
  AWS: enable FPGA support in amd64 AWS kernels

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

Bug description:
  CONFIG_FPGA needs to be enabled in linux-aws amd64 kernels (thereby
  supplying the fpga-mgr module), to support the AWS F1 instance type.

  Delivering the fpga-mgr module via the 'linux-modules-extras' package
  is acceptable.

  This config change only needs to be specifically applied to linux-
  aws/focal, since:

    linux-aws/bionic (aws-5.4) will pick it up from focal;
    linux-aws-groovy already has it enabled;
    linux-aws-xenial cannot support F1 anyway.

  --

  [Impact]

   * Since fpga-mgr is inadvertently omitted from linux-aws, use of the
  F1 instance type requires the user to manually install linux-virtual
  or linux-generic, which is an annoyance.

   * This patch just enables the module in linux-aws as we do for other
  kernels.

   * Fwiw, fpga-mgr is actually (needlessly) already enabled for linux-
  aws/arm64 but disabled for linux-aws/amd64 (where its needed for F1).

  [Test Case]

   * Install the linux-modules-extras package; modprobe fpga-mgr.

  [Regression Potential]

   * None.

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

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


[Kernel-packages] [Bug 1760087] Re: net test in ubuntu_kernel_selftest failed on linux-kvm

2020-10-07 Thread Sean Feole
** Tags added: sru-20200921

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

Title:
  net test in ubuntu_kernel_selftest failed on linux-kvm

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

Bug description:
  Steps:
1. Deploy a KVM node with Xenial, install linux-kvm on it.
2. git clone --depth 1 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial linux
3. Run the "net" sub set in the kernel_selftest

  Result:
* test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory
* test_bpf: [FAIL]
* selftests: test_bpf.sh [FAIL]

  Output:
  $ sudo make -C linux/tools/testing/selftests/net all run_tests
  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
  make: Nothing to be done for 'all'.
  
  running socket test
  
  [PASS]
  selftests: run_netsocktests [PASS]
  
  running psock_fanout test
  
  test: control single socket
  test: control multiple sockets
  test: datapath 0x0
  info: count=0,0, expect=0,0
  info: count=15,5, expect=15,5
  info: count=20,5, expect=20,5
  test: datapath 0x1000
  info: count=0,0, expect=0,0
  info: count=15,5, expect=15,5
  info: count=20,15, expect=20,15
  test: datapath 0x1
  info: count=0,0, expect=0,0
  info: count=10,10, expect=10,10
  info: count=18,17, expect=18,17
  test: datapath 0x3
  info: count=0,0, expect=0,0
  info: count=15,5, expect=15,5
  info: count=20,15, expect=20,15
  test: datapath 0x6
  info: count=0,0, expect=0,0
  info: count=5,15, expect=15,5
  info: count=20,15, expect=15,20
  test: datapath 0x7
  bpf: Function not implemented
  bpf verifier:
  ���ߟ
  [FAIL]
  
  running psock_tpacket test
  
  test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory
  [FAIL]
  selftests: run_afpackettests [PASS]
  test_bpf: [FAIL]
  selftests: test_bpf.sh [FAIL]
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 12:12:46 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1893956] Re: Intel x710 LOMs do not work on Focal

2020-10-07 Thread Jeff Lane
Hi... Verification done. Thanks


** Tags removed: blocks-hwcert-server verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  Intel x710 LOMs do not work on Focal

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

Bug description:
  [IMPACT]
  The Intel x710-TM4 is one of the latest 10GbE controllers from intel using 
the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 
2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver, 
and hwinfo does show both sides of the card but the kernel only sees the two 
SFP+ ports and cannot address or use the two copper ports.

  These devices have up to 4 ports, but only two seem to work and this
  has been seen on at least two different systems using LOMs based on
  this.

  This is currently blocking certification for one of our hardware
  partners.

  [FIX]
  This list of Patches enables the latest X710 controller fully:

  * 3df5b9a6a9ec i40e: enable X710 support
  * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices

  These are all clean cherry picks from 5.5 into 5.4

  My tree with these can be found here:
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom

  [TESTCASE]

  i40e should load successfully, all ports on Carlsville x710 LOM should
  be visible, configurable, and can pass traffic at full speed.

  Test kernels have been verified by the vendor reporting the issue that
  all network ports on the LOM are accessible and pass traffic at
  expected speeds.

  [REGRESSION RISK]
  Possible problem could be if the LED patch causes LEDs to not function 
correctly (or not at all) but the risk for this is pretty low.

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

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


[Kernel-packages] [Bug 1888779] Re: Can't boot with Linux 5.4.0.*

2020-10-07 Thread andrybak
Added the kernel parameters to grub:

$ grep 'debug initcall_debug earlycon=efifb' /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash debug initcall_debug 
earlycon=efifb"

$ sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/99_breeze-grub.cfg'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found theme: /boot/grub/themes/breeze/theme.txt
Found linux image: /boot/vmlinuz-5.4.0-48-generic
Found initrd image: /boot/initrd.img-5.4.0-48-generic
Found linux image: /boot/vmlinuz-5.4.0-47-generic
Found initrd image: /boot/initrd.img-5.4.0-47-generic
Found linux image: /boot/vmlinuz-5.4.0-45-generic
Found initrd image: /boot/initrd.img-5.4.0-45-generic
Found linux image: /boot/vmlinuz-5.4.0-42-generic
Found initrd image: /boot/initrd.img-5.4.0-42-generic
Found linux image: /boot/vmlinuz-5.4.0-40-generic
Found initrd image: /boot/initrd.img-5.4.0-40-generic
Found linux image: /boot/vmlinuz-5.3.0-51-generic
Found initrd image: /boot/initrd.img-5.3.0-51-generic
Adding boot menu entry for UEFI Firmware Settings
done


I've rebooted without choosing the kernel, so "5.4.0-48" was chosen.
Attached file is what could be seen when the booting hanged.

** Attachment added: "Screen, when booting hangs. With kernel parameters "debug 
initcall_debug earlycon=efifb""
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+attachment/5419084/+files/linux-5.4.0-48-kernel-debug-output-1.jpg

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

Title:
  Can't boot with Linux 5.4.0.*

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked
  5.4.0.42 and two uncertain previous versions, something like 5.4.0.40
  and 5.4.0.38).

  The laptop stays at a black screen with the following printed
  (disclaimer: typed manually from a low quality photo of the screen---
  typos and mistakes expected):

  [   69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
t
  ype=Physical Layer, (Receiver ID)
  [   69.258377] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mas
  k=0001/2000
  [   69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [   69.254733] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mask=0001/2000
  [   69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP

  
  See attachments for good quality photo of the screen.

  Notes
  -
  Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text 
as above is shown for a brief moment.

  Minimum attachment
  --
  Output of "sudo lspci -vnvn" is attached.

  $ cat /proc/version_signature
  Ubuntu 5.3.0-51.44-generic 5.3.18
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrei 2258 F pulseaudio
   /dev/snd/controlC1:  andrei 2258 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: KDE neon 20.04
  HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab
  InstallationDate: Installed on 2017-12-26 (940 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.4
  dmi.board.name: 0DRPKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  

[Kernel-packages] [Bug 1898909] Re: Installing hwe linux-tools does not provide /usr/bin wrappers

2020-10-07 Thread dann frazier
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Installing hwe linux-tools does not provide /usr/bin wrappers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a test script that requires /usr/bin/cpupower. Before calling
  it, I 'apt install linux-tools-$(uname -r)' to make sure it is
  available. For GA kernels, this works fine as there is a dependency
  chain on linux-tools-common which provides them. For HWE (tested on
  bionic), this does not work because linux-tools-5.4.0-48-generic
  doesn't depend on linux-tools-common. There is a linux-hwe-5.4-tools-
  common package, but it is empty, and also not a dependency of linux-
  tools-5.4.0-48-generic.

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

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


[Kernel-packages] [Bug 1898908] Re: dock not recognized once reconnected

2020-10-07 Thread Paul White
Changing status to 'Confirmed' as requested in comment #2.

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1898786] Re: Issue with bcache bch_mca_scan causing huge IO wait

2020-10-07 Thread Mauricio Faria de Oliveira
Hi Benjamin,

Thanks for the detailed report.

Does this system show signs of memory pressure?

bch_mca_scan() is part of bcache's memory shrinker, and thus should be
called when the system is trying to release memory from its several
caches.

Also, the bucket lock usage is widespread in bcache (from a quick grep;
and more used on writes, I'd imagine) thus if bch_mca_scan() is waiting
a lot on it, ie, showing lock contention, it would seem like the IO load
is indeed significant, as you mentioned.

Do you know the IO load profile, or could reproduce the issue with the
fio tool?

If we can reproduce this, there _might_ be some heuristics to consider
to use non-blocking trylock instead of blocking lock, and bail out/don't
wait if the lock is taken and it doesn't seem worth it. (but that would
be a development item, not a proper "bug" fix :)

cheers,
Mauricio

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

Title:
  Issue with bcache bch_mca_scan causing huge IO wait

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

Bug description:
  Hello,

  In short, we faced an issue with a huge IO wait on a bionic Ubuntu 
4.15.0-118.119-generic kernel.
  This is the full list of process and the kernel function they were stuck in 
[0].

  The main issue can probably be summarized by this perf reports
  * first identify that the cpu are stuck in idle because of something[1]
  * second, see what kernel function seems to stuck the process kswapd0 and 
kswapd1 [2].

  We could see that this seems to be the mutex_lock in the bch_mca_scan
  function [3].

  After running the command:

   | sudo bash -c "echo 1 > /sys/fs/bcache/f1a1e8cb-3e6b-40ea-852e-
  583c48d0c2b8/internal/btree_shrinker_disabled"

  The server started to respond normally and the IO wait dropped significantly
  [0]: https://pastebin.canonical.com/p/wYYKwHdRXk/
  [1]: https://pastebin.canonical.com/p/n2Tw57QyBC/
  [2]: https://pastebin.canonical.com/p/3QqFTfdHhX/
  [3]: 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/drivers/md/bcache/btree.c?h=Ubuntu-4.15.0-118.119#n674

  
  $ cat /proc/version_signature
  Ubuntu 4.15.0-118.119-generic 4.15.18

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-118-generic 4.15.0-118.119
  ProcVersionSignature: User Name 4.15.0-118.119-generic 4.15.18
  Uname: Linux 4.15.0-118-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 10:04 seq
   crw-rw 1 root audio 116, 33 Sep 29 10:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct  6 20:36:18 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL380 G7
  PciMultimedia:

  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic 
root=UUID=c6ad1629-a506-4043-a339-6d57f0708d12 ro console=ttyS1,115200 nosplash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-118-generic N/A
   linux-backports-modules-4.15.0-118-generic  N/A
   linux-firmware  1.173.18
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-09-27 (375 days ago)
  dmi.bios.date: 05/05/2011
  dmi.bios.vendor: HP
  dmi.bios.version: P67
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP67:bd05/05/2011:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL380 G7
  dmi.sys.vendor: HP

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1898908] Re: dock not recognized once reconnected

2020-10-07 Thread udippel
apport information

** Tags added: apport-collected

** Description changed:

  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.9
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  udippel1576 F pulseaudio
+  /dev/snd/controlC0:  udippel1576 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
+ InstallationDate: Installed on 2019-03-14 (573 days ago)
+ InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ MachineType: LENOVO 20CHS1KL00
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-48-generic N/A
+  linux-backports-modules-5.4.0-48-generic  N/A
+  linux-firmware1.187.3
+ Tags:  focal
+ Uname: Linux 5.4.0-48-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 03/24/2020
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N17ETB2W (2.12 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20CHS1KL00
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0E50510 WIN
+ dmi.chassis.asset.tag: BT-56-001476
+ dmi.chassis.type: 11
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
+ dmi.product.family: ThinkPad Helix 2nd
+ dmi.product.name: 20CHS1KL00
+ dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
+ dmi.product.version: ThinkPad Helix 2nd
+ dmi.sys.vendor: LENOVO

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad 

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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

2020-10-07 Thread udippel
apport information

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1576 F pulseaudio
   /dev/snd/controlC0:  udippel1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=9eb1d50f-cb20-4f4a-a8e4-a40efb1886da
  InstallationDate: Installed on 2019-03-14 (573 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS1KL00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=UUID=c447507e-03aa-44a0-bb04-99c05ae1354b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS1KL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: BT-56-001476
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS1KL00:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS1KL00:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS1KL00
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1898912] [NEW] ath3k: probe of 2-1.3:1.0 failed with error -110

2020-10-07 Thread navycat
Public bug reported:

Bluetooth AR3011 doesn't work in 20.10 but works in 20.04

dmesg.log
[   10.300282] Bluetooth: Can't change to loading configuration err
[   10.300332] ath3k: probe of 2-1.3:1.0 failed with error -110
[   10.300424] usbcore: registered new interface driver ath3k


lsusb | grep Blue
0cf3:3002 Qualcomm Atheros Communications AR3011 Bluetooth

blueman-manager
error: No adapter(s) found

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-20-generic 5.8.0-20.21
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  navycat1983 F pulseaudio
 /dev/snd/controlC0:  navycat1983 F pulseaudio
 /dev/snd/controlC1:  navycat1983 F pulseaudio
CasperMD5CheckResult: skip
Date: Wed Oct  7 20:08:25 2020
InstallationDate: Installed on 2020-10-07 (0 days ago)
InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
IwConfig:
 lono wireless extensions.
 
 eno1  no wireless extensions.
MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
ProcEnviron:
 LANGUAGE=ru
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed 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.
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-20-generic N/A
 linux-backports-modules-5.8.0-20-generic  N/A
 linux-firmware1.190
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2018
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 150-SE-E789
dmi.board.vendor: EVGA
dmi.board.version: Patsburg
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
dmi.product.family: X86 AT
dmi.product.name: MODEL_NAME
dmi.product.sku: PROJECT_SUB_TAG
dmi.product.version: BASE_BOARD_VERSION
dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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


** Tags: amd64 apport-bug 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/1898912

Title:
  ath3k: probe of 2-1.3:1.0 failed with error -110

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth AR3011 doesn't work in 20.10 but works in 20.04

  dmesg.log
  [   10.300282] Bluetooth: Can't change to loading configuration err
  [   10.300332] ath3k: probe of 2-1.3:1.0 failed with error -110
  [   10.300424] usbcore: registered new interface driver ath3k

  
  lsusb | grep Blue
  0cf3:3002 Qualcomm Atheros Communications AR3011 Bluetooth

  blueman-manager
  error: No adapter(s) found

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-20-generic 5.8.0-20.21
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat1983 F pulseaudio
   /dev/snd/controlC0:  navycat1983 F pulseaudio
   /dev/snd/controlC1:  navycat1983 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Oct  7 20:08:25 2020
  InstallationDate: Installed on 2020-10-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcEnviron:
   LANGUAGE=ru
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.ass

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

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

apport-collect 1898909

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

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

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

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

** Tags added: focal

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

Title:
  Installing hwe linux-tools does not provide /usr/bin wrappers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a test script that requires /usr/bin/cpupower. Before calling
  it, I 'apt install linux-tools-$(uname -r)' to make sure it is
  available. For GA kernels, this works fine as there is a dependency
  chain on linux-tools-common which provides them. For HWE (tested on
  bionic), this does not work because linux-tools-5.4.0-48-generic
  doesn't depend on linux-tools-common. There is a linux-hwe-5.4-tools-
  common package, but it is empty, and also not a dependency of linux-
  tools-5.4.0-48-generic.

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

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


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

2020-10-07 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  ath3k: probe of 2-1.3:1.0 failed with error -110

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth AR3011 doesn't work in 20.10 but works in 20.04

  dmesg.log
  [   10.300282] Bluetooth: Can't change to loading configuration err
  [   10.300332] ath3k: probe of 2-1.3:1.0 failed with error -110
  [   10.300424] usbcore: registered new interface driver ath3k

  
  lsusb | grep Blue
  0cf3:3002 Qualcomm Atheros Communications AR3011 Bluetooth

  blueman-manager
  error: No adapter(s) found

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-20-generic 5.8.0-20.21
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat1983 F pulseaudio
   /dev/snd/controlC0:  navycat1983 F pulseaudio
   /dev/snd/controlC1:  navycat1983 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Oct  7 20:08:25 2020
  InstallationDate: Installed on 2020-10-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcEnviron:
   LANGUAGE=ru
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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

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


[Kernel-packages] [Bug 1898909] [NEW] Installing hwe linux-tools does not provide /usr/bin wrappers

2020-10-07 Thread dann frazier
Public bug reported:

I have a test script that requires /usr/bin/cpupower. Before calling it,
I 'apt install linux-tools-$(uname -r)' to make sure it is available.
For GA kernels, this works fine as there is a dependency chain on linux-
tools-common which provides them. For HWE (tested on bionic), this does
not work because linux-tools-5.4.0-48-generic doesn't depend on linux-
tools-common. There is a linux-hwe-5.4-tools-common package, but it is
empty, and also not a dependency of linux-tools-5.4.0-48-generic.

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

Title:
  Installing hwe linux-tools does not provide /usr/bin wrappers

Status in linux package in Ubuntu:
  New

Bug description:
  I have a test script that requires /usr/bin/cpupower. Before calling
  it, I 'apt install linux-tools-$(uname -r)' to make sure it is
  available. For GA kernels, this works fine as there is a dependency
  chain on linux-tools-common which provides them. For HWE (tested on
  bionic), this does not work because linux-tools-5.4.0-48-generic
  doesn't depend on linux-tools-common. There is a linux-hwe-5.4-tools-
  common package, but it is empty, and also not a dependency of linux-
  tools-5.4.0-48-generic.

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

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


[Kernel-packages] [Bug 1888779] Re: Can't boot with Linux 5.4.0.*

2020-10-07 Thread andrybak
> But could you try booting with following kernel parameters?
> 
>   debug initcall_debug earlycon=efifb
> 
> The screen may scroll much slower than usual but it's normal. Take a picture 
> and attach here if any last word of the kernel dumped.

Sure, I'll do it today or tomorrow, as time permits.

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

Title:
  Can't boot with Linux 5.4.0.*

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked
  5.4.0.42 and two uncertain previous versions, something like 5.4.0.40
  and 5.4.0.38).

  The laptop stays at a black screen with the following printed
  (disclaimer: typed manually from a low quality photo of the screen---
  typos and mistakes expected):

  [   69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
t
  ype=Physical Layer, (Receiver ID)
  [   69.258377] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mas
  k=0001/2000
  [   69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [   69.254733] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mask=0001/2000
  [   69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP

  
  See attachments for good quality photo of the screen.

  Notes
  -
  Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text 
as above is shown for a brief moment.

  Minimum attachment
  --
  Output of "sudo lspci -vnvn" is attached.

  $ cat /proc/version_signature
  Ubuntu 5.3.0-51.44-generic 5.3.18
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrei 2258 F pulseaudio
   /dev/snd/controlC1:  andrei 2258 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: KDE neon 20.04
  HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab
  InstallationDate: Installed on 2017-12-26 (940 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.4
  dmi.board.name: 0DRPKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1888779] Re: Can't boot with Linux 5.4.0.*

2020-10-07 Thread andrybak
Sorry, here's the image I meant.

** Attachment added: "Clear image of the message, when the booting process 
hangs."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+attachment/5419010/+files/IMG_20200929_234229.jpg

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

Title:
  Can't boot with Linux 5.4.0.*

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked
  5.4.0.42 and two uncertain previous versions, something like 5.4.0.40
  and 5.4.0.38).

  The laptop stays at a black screen with the following printed
  (disclaimer: typed manually from a low quality photo of the screen---
  typos and mistakes expected):

  [   69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
t
  ype=Physical Layer, (Receiver ID)
  [   69.258377] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mas
  k=0001/2000
  [   69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [   69.254733] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mask=0001/2000
  [   69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP

  
  See attachments for good quality photo of the screen.

  Notes
  -
  Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text 
as above is shown for a brief moment.

  Minimum attachment
  --
  Output of "sudo lspci -vnvn" is attached.

  $ cat /proc/version_signature
  Ubuntu 5.3.0-51.44-generic 5.3.18
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrei 2258 F pulseaudio
   /dev/snd/controlC1:  andrei 2258 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: KDE neon 20.04
  HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab
  InstallationDate: Installed on 2017-12-26 (940 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.4
  dmi.board.name: 0DRPKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1898903] Re: *-tools-common packages descriptions have typo "PGKVER"

2020-10-07 Thread dann frazier
** Changed in: linux (Ubuntu Groovy)
   Status: Confirmed => In Progress

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

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

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

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

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

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

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

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

Title:
  *-tools-common packages descriptions have typo "PGKVER"

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  $ apt show linux-tools-common
  Description: Linux kernel version specific tools for version 4.15.0
   This package provides the architecture independent parts for kernel
   version locked tools (such as perf and x86_energy_perf_policy) for
   version PGKVER.
   ^^

  Seems to be true for all versions/flavors.

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

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


[Kernel-packages] [Bug 1816658] Re: Right click on touch screens not supposed to be supported?

2020-10-07 Thread udippel
I wonder if I should set this bug to 'solved', since in 20.04, I
encountered a solution that works at least rudimentary. (Right lower
corner is unhandy, two finger conflicts with scrolling.)

Nevertheless thumbs up!! because it works basically; and allows me to
actually start removing the tablet part from my convertible. Thanks a
bunch!

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

Title:
  Right click on touch screens not supposed to be supported?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  So it seems. If not, I'd consider this a bug, rather than a RFE. 10
  years ago we were told that KDE 3.5 had to go, and Plasma had to come
  to support such screens.

  I searched Dr. Google and I searched in here, and didn't find a bug report, 
but a number of posts that this would not be working. Now I finally have a 
decent machine, run Kubuntu 18.04, and have so far not been able to set this 
functionality up. 
  Under System Settings it doesn't show up as input device, though it is a 
wacom device on a Lenovo machine. 

  It is a double boot machine and kind of seems to get me back on Windows after 
some 20 years of absence, because I love the touch screen, including the 
Thinkpad pen. The pen also works, but also doesn't effect any right click. I am 
fully agreeable with the behaviour of the context menu popping up from a longer 
touch of a screen target.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  udippel1593 F pulseaudio
   /dev/snd/controlC1:  udippel1593 F pulseaudio
   /dev/snd/controlC0:  udippel1593 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (4 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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


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

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

apport-collect 1898908

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

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

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

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

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.

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

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


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

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

apport-collect 1898505

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

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

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

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

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

Title:
  weird screen display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  After Resuming my system after sleep mode,display shows overlapping of 
multiple pages.Initially it shows black screen after that when I try to switch 
to different tab it shows partial display of previous tabs as well.
  This issue is also happening with Slack and other software as well.

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

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


[Kernel-packages] [Bug 1898908] Re: dock not recognized once reconnected

2020-10-07 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

This bug did not have a package associated with it, which is important
for ensuring that it gets looked at by the proper developers. You can
learn more about finding the right package at
https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this
bug as a bug in 'linux' due to the hardware issues that you are
experiencing.

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://help.ubuntu.com/community/ReportingBugs.

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

** Tags added: focal

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

Title:
  dock not recognized once reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
  However, I plug it back into the keyboard dock, this dock is not recognized. 
So neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.

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

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


[Kernel-packages] [Bug 1883261] Re: [linux-azure] Two Fixes For kdump Over Network

2020-10-07 Thread Kelsey Margarete Skunberg
** Description changed:

+ 
+ [Impact]
+ 
  Microsoft would like to request two kdump related fixes in all releases
  supported on Azure.  The two commits are:
  
  c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
  83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release 
resource properly")
  
  These are in the virtual PCI driver for Hyper-V.  The customer visible
  symptom is that the network is not functional in the kdump kernel, so
  the dump file must be stored on the local disk and cannot be written
  over the network.
  
  The problem only occurs when Accelerated Networking is enabled.  It’s a
  relatively obscure scenario, which is why the problem has not surfaced
  before now.  But we have an important customer who wants the “dump-file-
  over-the-network” functionality to work.
+ 
+ [Test Case]
+ 
+ - Apply requested patches and boot into updated kernel
+ - Verify Accelerated Networking is enabled
+ - Set up kdump
+ - configure kdump to use SSH 
+ - Test the crash dump mechanism and verify the kernel crash dump appears on 
the selected remote server
+ 
+ Further details for setting up kdump through testing can be found here:
+ https://ubuntu.com/server/docs/kernel-crash-dump
+ 
+ 
+ [Regression Potential]
+ 
+ 
+ Build & boot tested. Verified kdump works as intended over SSH after patches 
are applied. 
+ 
+ Both 5.4 and 4.15 test kernels were sent to Microsoft. Both kernels
+ signed off on and verified to resolve problem.

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

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

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

Title:
  [linux-azure] Two Fixes For kdump Over Network

Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Bionic:
  New
Status in linux-azure source package in Focal:
  New

Bug description:
  
  [Impact]

  Microsoft would like to request two kdump related fixes in all
  releases supported on Azure.  The two commits are:

  c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
  83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release 
resource properly")

  These are in the virtual PCI driver for Hyper-V.  The customer visible
  symptom is that the network is not functional in the kdump kernel, so
  the dump file must be stored on the local disk and cannot be written
  over the network.

  The problem only occurs when Accelerated Networking is enabled.  It’s
  a relatively obscure scenario, which is why the problem has not
  surfaced before now.  But we have an important customer who wants the
  “dump-file-over-the-network” functionality to work.

  [Test Case]

  - Apply requested patches and boot into updated kernel
  - Verify Accelerated Networking is enabled
  - Set up kdump
  - configure kdump to use SSH 
  - Test the crash dump mechanism and verify the kernel crash dump appears on 
the selected remote server

  Further details for setting up kdump through testing can be found here:
  https://ubuntu.com/server/docs/kernel-crash-dump

  
  [Regression Potential]

  
  Build & boot tested. Verified kdump works as intended over SSH after patches 
are applied. 

  Both 5.4 and 4.15 test kernels were sent to Microsoft. Both kernels
  signed off on and verified to resolve problem.

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

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


[Kernel-packages] [Bug 1898505] Re: weird screen display

2020-10-07 Thread Paul White
According to
https://wiki.ubuntu.com/Bugs/FindRightPackage#Suspend_and_Hibernate this
bug report should initially be filed against the kernel package. So
reassigning.

@aradhana, please provide the appropriate information when requested
otherwise this bug report will expire due to insufficient information
being supplied to enable your issue to be resolved.

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

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

Title:
  weird screen display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  After Resuming my system after sleep mode,display shows overlapping of 
multiple pages.Initially it shows black screen after that when I try to switch 
to different tab it shows partial display of previous tabs as well.
  This issue is also happening with Slack and other software as well.

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

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


[Kernel-packages] [Bug 1898908] [NEW] dock not recognized once reconnected

2020-10-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

With my lenovo Helix 2, and in 20.04, when I remove the tablet part (it is a 
convertible), control is properly passed to the tablet part. 
However, I plug it back into the keyboard dock, this dock is not recognized. So 
neither keys nor touchpad get re-activated. Logout-Login doesn't solve the 
problem. Only a full reboot makes the keyboard and built-in touchpad come back.

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

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

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


[Kernel-packages] [Bug 1898505] [NEW] weird screen display

2020-10-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hi,
After Resuming my system after sleep mode,display shows overlapping of multiple 
pages.Initially it shows black screen after that when I try to switch to 
different tab it shows partial display of previous tabs as well.
This issue is also happening with Slack and other software as well.

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

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

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


[Kernel-packages] [Bug 1898903] Re: *-tools-common packages descriptions have typo "PGKVER"

2020-10-07 Thread dann frazier
** Changed in: linux (Ubuntu Groovy)
   Status: Incomplete => Confirmed

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

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

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

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

Title:
  *-tools-common packages descriptions have typo "PGKVER"

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  $ apt show linux-tools-common
  Description: Linux kernel version specific tools for version 4.15.0
   This package provides the architecture independent parts for kernel
   version locked tools (such as perf and x86_energy_perf_policy) for
   version PGKVER.
   ^^

  Seems to be true for all versions/flavors.

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

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


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

2020-10-07 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Ubuntu slow boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My PC takes about 2 minutes till Desktop, it's just slow. I am
  attaching logs in hope of seeing if there is a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-lowlatency 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60
  Uname: Linux 5.4.0-48-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lyubo  2186 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Oct  7 17:00:19 2020
  InstallationDate: Installed on 2020-02-08 (242 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 1bbb:0195 T & A Mobile Phones Mobilebroadband
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash 
resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality 
init=/lib/systemd/systemd-bootchart vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-lowlatency N/A
   linux-backports-modules-5.4.0-48-lowlatency  N/A
   linux-firmware   1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-20 (169 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742

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

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


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

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

apport-collect 1898903

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

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

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

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

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

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

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

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

Title:
  *-tools-common packages descriptions have typo "PGKVER"

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Groovy:
  Incomplete

Bug description:
  $ apt show linux-tools-common
  Description: Linux kernel version specific tools for version 4.15.0
   This package provides the architecture independent parts for kernel
   version locked tools (such as perf and x86_energy_perf_policy) for
   version PGKVER.
   ^^

  Seems to be true for all versions/flavors.

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

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


[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

2020-10-07 Thread Mark Voorberg
I can confirm that installing the 5.8.14 kernel works on the Thinkbook
14.

Find the mailine kernels here:

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

Download these files:

linux-headers-5.8.14-050814_5.8.14-_all.deb
linux-headers-5.8.14-050814-generic_5.8.14-_amd64.deb
linux-image-unsigned-5.8.14-050814-generic_5.8.14-_amd64.deb
linux-modules-5.8.14-050814-generic_5.8.14-_amd64.deb

Copy them all to an empty folder and run:

sudo dpkg -i *.deb

After installation, reboot & enjoy!
-Thanks all

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

Title:
  Lenovo ThinkBook 14-IML Touchpad not showing up in
  /proc/bus/input/devices

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Fix Released
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  == SRU Justification ==
  [Impact]
  Touchpad on sereval Lenovo ThinkBook doesn't work.

  [Fix]
  Maintain method calling ordering by calling _REG before issuing _STA, as
  ACPI spec suggested, for I2C ACPI devices.

  [Test]
  Positive feedback from several users.

  [Regression Potential]
  If there are some systems that rely on the wrong calling ordering then
  there's a regression risk. However it's rather unlikely.

  == Original Bug Report ==
  This is happening on a ThinkBook 14 IML 20RV.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1848 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 20 11:10:52 2019
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20RV
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/10/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CJCN21WW
  dmi.board.name: LVA/LVAB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr:
  dmi.product.family: ThinkBook 14-IML
  dmi.product.name: 20RV
  dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML
  dmi.product.version: Lenovo ThinkBook 14-IML
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1898903] [NEW] *-tools-common packages descriptions have typo "PGKVER"

2020-10-07 Thread dann frazier
Public bug reported:

$ apt show linux-tools-common
Description: Linux kernel version specific tools for version 4.15.0
 This package provides the architecture independent parts for kernel
 version locked tools (such as perf and x86_energy_perf_policy) for
 version PGKVER.
 ^^

Seems to be true for all versions/flavors.

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

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

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

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

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

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

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

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

** Also affects: linux (Ubuntu Bionic)
   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/1898903

Title:
  *-tools-common packages descriptions have typo "PGKVER"

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Groovy:
  New

Bug description:
  $ apt show linux-tools-common
  Description: Linux kernel version specific tools for version 4.15.0
   This package provides the architecture independent parts for kernel
   version locked tools (such as perf and x86_energy_perf_policy) for
   version PGKVER.
   ^^

  Seems to be true for all versions/flavors.

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

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


[Kernel-packages] [Bug 1898878] Re: Ubuntu slow boot

2020-10-07 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Ubuntu slow boot

Status in linux package in Ubuntu:
  New

Bug description:
  My PC takes about 2 minutes till Desktop, it's just slow. I am
  attaching logs in hope of seeing if there is a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-lowlatency 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60
  Uname: Linux 5.4.0-48-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lyubo  2186 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Oct  7 17:00:19 2020
  InstallationDate: Installed on 2020-02-08 (242 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 1bbb:0195 T & A Mobile Phones Mobilebroadband
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash 
resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality 
init=/lib/systemd/systemd-bootchart vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-lowlatency N/A
   linux-backports-modules-5.4.0-48-lowlatency  N/A
   linux-firmware   1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-20 (169 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742

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

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


[Kernel-packages] [Bug 1898878] [NEW] Ubuntu slow boot

2020-10-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

My PC takes about 2 minutes till Desktop, it's just slow. I am attaching
logs in hope of seeing if there is a bug.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-lowlatency 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60
Uname: Linux 5.4.0-48-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lyubo  2186 F pulseaudio
CasperMD5CheckResult: skip
Date: Wed Oct  7 17:00:19 2020
InstallationDate: Installed on 2020-02-08 (242 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
 Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
 Bus 001 Device 002: ID 1bbb:0195 T & A Mobile Phones Mobilebroadband
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire A515-51G
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash 
resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality 
init=/lib/systemd/systemd-bootchart vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-48-lowlatency N/A
 linux-backports-modules-5.4.0-48-lowlatency  N/A
 linux-firmware   1.187.3
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-04-20 (169 days ago)
dmi.bios.date: 01/03/2019
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.02
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Charmander_KL
dmi.board.vendor: KBL
dmi.board.version: V2.02
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.02
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
dmi.product.family: Aspire 5
dmi.product.name: Aspire A515-51G
dmi.product.sku: 
dmi.product.version: V2.02
dmi.sys.vendor: Acer
mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742

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


** Tags: amd64 apport-bug focal
-- 
Ubuntu slow boot
https://bugs.launchpad.net/bugs/1898878
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-10-07 Thread Azizkhan
After trying building kernel 5.8.14 with patches getting error:
  LD [M]  drivers/iio/pressure/st_pressure.o
  GEN .version
  CHK include/generated/compile.h
  LD  vmlinux.o
  MODPOST vmlinux.symvers
  MODINFO modules.builtin.modinfo
  GEN modules.builtin
BTF: .tmp_vmlinux.btf: pahole (pahole) is not available
Failed to generate BTF for vmlinux
Try to disable CONFIG_DEBUG_INFO_BTF
make[3]: *** [Makefile:1135: vmlinux] Error 1
make[2]: *** [debian/rules:6: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
make[1]: *** [scripts/Makefile.package:77: deb-pkg] Error 2
make: *** [Makefile:1491: deb-pkg] Error 2

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  

[Kernel-packages] [Bug 1897501] Re: HP Zbook Studio G7 boots into corrupted screen with PSR featured panel

2020-10-07 Thread Ian
** 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-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1897501

Title:
  HP Zbook Studio G7 boots into corrupted screen with PSR featured panel

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  Sreen divided into half after installing Focal 5.4.0-48-generic under
  Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
  Graphics Mode. Screenshot attached as
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
  .

  With some more investigatin, https://git.launchpad.net/~ubuntu-
  kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782
  ("UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms")
  for bug 1849947 is the root cause. This was landed to all Ubuntu
  kernels and Ubuntu only for kernel versions 5.0 and up till v5.9
  unstable currently.

  It seems this panel must have PSR enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 964 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Sep 28 01:50:54 2020
  InstallationDate: Installed on 2020-09-22 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
  MachineType: HP HP ZBook Studio G7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: HP
  dmi.bios.version: S91 Ver. 85.28.01
  dmi.board.name: 8736
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.32.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Studio G7
  dmi.sys.vendor: HP

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

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


  1   2   >