[Kernel-packages] [Bug 1845863] Re: vma05 in mm from ubuntu_ltp failed on B-hwe-edge 5.3

[Po-Hsu Lin]

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

** Tags added: oracle

** Tags added: sru-20191021

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

Title:
  vma05 in mm from ubuntu_ltp failed on B-hwe-edge 5.3

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

Bug description:
  Test failed with:
 tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4

  Need to check if it has something to do with AppArmor

   startup='Fri Sep 20 16:48:02 2019'
   vma05 1 TINFO: timeout per run is 0h 5m 0s
   vma05 1 TFAIL: [vsyscall] reporting wrong
   vma05 1 TPASS: [vdso] backtrace complete
   vma05 2 TINFO: AppArmor enabled, this may affect test results
   vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root) 
   vma05 2 TINFO: loaded AppArmor profiles: none

   Summary:
   passed 1
   failed 1
   skipped 0
   warnings 0

  
   tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4
   startup='Fri Sep 20 16:48:02 2019'
   vma05 1 TINFO: timeout per run is 0h 5m 0s
   vma05 1 TFAIL: [vsyscall] reporting wrong
   vma05 1 TPASS: [vdso] backtrace complete
   vma05 2 TINFO: AppArmor enabled, this may affect test results
   vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root) 
   vma05 2 TINFO: loaded AppArmor profiles: none

   Summary:
   passed 1
   failed 1
   skipped 0
   warnings 0

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

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

[Kernel-packages] [Bug 1842850] Re: NULL pointer dereference in kvm_mmu_flush_or_zap

[Fabian Zimmermann]

We had the issue 2 times within ~3 weeks, so we moved the system out of
production, updated every firmware possible, started loadtesting - but
are unable to enforce it.

We now moved the system back to production so see if the issue happens
again (~2 weeks ago).

I will report as soon as we have the issue again.

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

Title:
  NULL pointer dereference in kvm_mmu_flush_or_zap

Status in linux package in Ubuntu:
  Expired

Bug description:
  tonight one of our systems run into the following panic

  --
  kernel NULL pointer dereference at 
  kernel: [2468259.002689] IP: kvm_mmu_flush_or_zap+0x5/0x40 [kvm]
  kernel: [2468259.007758] PGD 0 P4D 0 
  kernel: [2468259.010483] Oops:  [#1] SMP PTI
  kernel: [2468259.014161] Modules linked in: vhost_net vhost tap xt_nat 
xt_REDIRECT nf_nat_redirect ip6table_mangle xt_mark xt_connmark xt_multiport 
xt_set ip_set_hash_net ip_set xt_CT xt_mac veth vxlan ip6_udp_tunnel udp_tunnel 
ip6table_raw xt_physdev xt_comment xt_CHECKSUM xt_tcpudp iptable_mangle 
iptable_raw ebtable_filter ebtables nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo br_netfilter bridge aufs rbd libceph binfmt_misc 8021q garp mrp stp 
llc bonding openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 rdma_ucm(OE) 
ib_ucm(OE) nf_defrag_ipv6 ib_ipoib(OE) ip6table_filter ib_umad(OE) xt_conntrack 
mlx5_fpga_tools(OE) mlx5_ib(OE) ib_uverbs(OE) iptable_filter mlx4_ib(OE) 
mlx4_en(OE) mlx4_core(OE) ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_addrtype 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack
  kernel: [2468259.085884]  ip_tables ipmi_ssif intel_rapl skx_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helper dell_smbios dcdbas cryptd intel_cstate 
dell_wmi_descriptor wmi_bmof intel_rapl_perf mei_me mei lpc_ich shpchp ipmi_si 
ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid rdma_cm(OE) iw_cm(OE) 
ib_cm(OE) ib_core(OE) iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip6_tables x_tables autofs4 mgag200 i2c_algo_bit ttm mlx5_core(OE) mlxfw(OE) 
devlink drm_kms_helper syscopyarea sysfillrect bnx2x mlx_compat(OE) sysimgblt 
ptp fb_sys_fops pps_core mdio drm libcrc32c ahci libahci wmi
  kernel: [2468259.148257] CPU: 21 PID: 3455197 Comm: CPU 11/KVM Tainted: G 
  OE4.15.0-55-generic #60~16.04.2-Ubuntu
  kernel: [2468259.158712] Hardware name: Dell Inc. PowerEdge R640/0PHYDR, BIOS 
2.2.10 05/15/2019
  kernel: [2468259.166510] RIP: 0010:kvm_mmu_flush_or_zap+0x5/0x40 [kvm]
  kernel: [2468259.172097] RSP: 0018:ad129f5b3ac8 EFLAGS: 00010246
  kernel: [2468259.177514] RAX:  RBX: 93dcbb5df5a8 RCX: 

  kernel: [2468259.184840] RDX:  RSI:  RDI: 
940b7ff38000
  kernel: [2468259.192168] RBP: ad129f5b3b30 R08: 0001 R09: 

  kernel: [2468259.199495] R10: 0001 R11: 0781 R12: 
940b7ff38000
  kernel: [2468259.206820] R13:  R14:  R15: 
00802800
  kernel: [2468259.214151] FS:  7f6de8ff9700() 
GS:9411ff28() knlGS:964c1f4c
  kernel: [2468259.222431] CS:  0010 DS:  ES:  CR0: 80050033
  kernel: [2468259.228369] CR2:  CR3: 00b54b6f8002 CR4: 
007626e0
  kernel: [2468259.235694] DR0:  DR1:  DR2: 

  kernel: [2468259.243018] DR3:  DR6: fffe0ff0 DR7: 
0400
  kernel: [2468259.250348] PKRU: 5554
  kernel: [2468259.253245] Call Trace:
  kernel: [2468259.255910]  ? kvm_mmu_get_page+0x29a/0x6b0 [kvm]
  kernel: [2468259.260814]  __direct_map.part.124+0xf5/0x220 [kvm]
  kernel: [2468259.265901]  tdp_page_fault+0x264/0x290 [kvm]
  kernel: [2468259.270462]  kvm_mmu_page_fault+0x62/0x170 [kvm]
  kernel: [2468259.275278]  handle_ept_violation+0xae/0x140 [kvm_intel]
  kernel: [2468259.280781]  vmx_handle_exit+0xb3/0xcd0 [kvm_intel]
  kernel: [2468259.285867]  ? vmx_vcpu_run+0x41d/0x600 [kvm_intel]
  kernel: [2468259.290960]  vcpu_enter_guest+0x451/0x1280 [kvm]
  kernel: [2468259.295774]  ? vmx_sync_pir_to_irr+0x39/0x70 [kvm_intel]
  kernel: [2468259.301307]  kvm_arch_vcpu_ioctl_run+0x270/0x3d0 [kvm]
  kernel: [2468259.306652]  ? kvm_arch_vcpu_ioctl_run+0x270/0x3d0 [kvm]
  kernel: [2468259.312163]  kvm_vcpu_ioctl+0x33a/0x610 [kvm]
  kernel: [2468259.317432]  ? do_futex+0x10f/0x500
  kernel: [2468259.321830]  do_vfs_ioctl+0xa4/0x600
  kernel: [2468259.326244]  ? SyS_futex+0x7f/0x180
  kernel: [2468259.330523]  SyS_ioctl+0x79/0x90
  kernel: [2468259.334561]  do_syscall_64+0x73/0x130
  kernel: [2468259.338992]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  kernel: [2468259.344817] 

[Kernel-packages] [Bug 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850483
  packages:
lrm: linux-restricted-modules-oracle-5.3
main: linux-oracle-5.3
meta: linux-meta-oracle-5.3
signed: linux-signed-oracle-5.3
  phase: Testing
  phase-changed: Thursday, 07. November 2019 18:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   regression-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850483
  packages:
lrm: linux-restricted-modules-oracle-5.3
main: linux-oracle-5.3
meta: linux-meta-oracle-5.3
signed: linux-signed-oracle-5.3
  phase: Testing
  phase-changed: Thursday, 07. November 2019 18:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851351/+subscriptions

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

[Kernel-packages] [Bug 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker

[Po-Hsu Lin]

5.3.0-1005.5~18.04.1 - oracle
Regression test CMPL, RTB.

Issue to note in oracle (amd64):
  ubuntu_kernel_selftests - test_bpf in net (bug 1812189) test_blackhole_dev in 
net (bug 1851619) trace_printk in ftrace (bug 1830084)
  ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) apic-split timeouted 
(bug 1821390) ept (bug 1824228) hyperv_stimer (bug 1827982) hyperv_synic (bug 
1827980) pcid (bug 1827979) port80 (bug 1748105) vmx (bug 1821394)
  ubunut_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) vma05 (bug 1845863) 
memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) 
memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) 
getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ltp_acpi (bug 1830676)
  ubuntu_lttng_smoke_test - module failed to build on B-5.3 (bug 1844764)
  ubuntu_qrt_kernel_security - test_140_kernel_modules_not_tainted (bug 1850888)
  ubuntu_sysdig_smoke_test - module failed to build on B-5.3 (bug 1844766)

Skipped / blacklisted:
 * libhugetlbfs
 * ubuntu_seccomp

* Note the ubuntu_kernel_selftests must be reviewed on the jenkins
directly

** Changed in: kernel-sru-workflow/regression-testing
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850483
  packages:
lrm: linux-restricted-modules-oracle-5.3
main: linux-oracle-5.3
meta: linux-meta-oracle-5.3
signed: linux-signed-oracle-5.3
  phase: Testing
  phase-changed: Thursday, 07. November 2019 18:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851351/+subscriptions

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

[Kernel-packages] [Bug 1851987] Re: Long boot times, ACPI error messages in dmesg

[Abdelrahman saber]

** Summary changed:

- ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
+ Long boot times, ACPI error messages in dmesg

** Description changed:

  I have a lenovo legion Y540 15IRH with nvidia 1660 ti and LNVNB161216
  mother board and when i type (dmesg) command i get this
- 
  
  [0.212539] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.212546] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.212548] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.212597] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.212601] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.212603] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.212604] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.212607] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.212608] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.215043] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.215047] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.215049] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.215050] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.215053] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.215054] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.217473] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.217476] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.217478] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.217480] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.217482] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.217483] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.219901] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219905] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219906] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.219908] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219910] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219912] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.222324] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.222327] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.222329] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.224748] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.224752] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.224753] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.224755] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.224757] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.224759] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.227173] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS07._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.227176] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.227178] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.229595] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS08._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.229599] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.229600] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.232020] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS09._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.232023] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [

Re: [Kernel-packages] [Bug 1849720] Re: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)

[Christian Ehrhardt ]

On Tue, Nov 12, 2019 at 5:35 AM Zach Graceffa
<1849...@bugs.launchpad.net> wrote:
>
> @Christian - 5.4-rc7 worked for both e1000e and virtio NICs. No crash as
> of about 15 minutes.

Great, thanks Zach for the check!

@kernel-team, that means there likely is something in 5.3 -> 5.4 that
you could identify and backport.
As I said before, you might want to provide bisecting builds for this
either for the 5.2->5.3 breakage or the possible 5.3->5.4 fix.

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

Title:
  KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  In Progress

Bug description:
  After upgrading to Ubuntu 19.10 I noticed that all of my Windows
  Servers VMs would cause a hard crash on the Host OS shortly after
  starting up the VM.  I tracked it down to the Guest OS attempting to
  use the Network Connection, and if I disabled the virtual NIC for the
  VM, everything runs OK (albeit without a working network connection
  for the Guest OS).  Note that I'm just using the built in virtual
  network called "default" that get's installed by default and uses NAT
  forwarding.

  I believe the problem is related to AppArmor, as I noticed some errors
  present in various log files.

  Unfortunately, due to a time critical project I had to roll back to
  Ubuntu 19.04 and didn't capture any of the log files.  I did, however,
  find another user on Reddit with the exact same problems that I
  encountered and he agreed to let me post the log files.

  Here are what are think are the relevant pieces from the log files:

  ===

  Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM
  Oct 22 22:59:23 brian-pc kernel: [   67.001284] device virbr0-nic left 
promiscuous mode
  Oct 22 22:59:23 brian-pc kernel: [   67.001298] virbr0: port 1(virbr0-nic) 
entered disabled state
  Oct 22 22:59:23 brian-pc NetworkManager[3557]:   [1571799563.3862] 
device (virbr0-nic): released from master device virbr0
  Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer 
relevant for mDNS.
  Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on 
interface virbr0.IPv4 with address 192.168.122.1.
  Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 
192.168.122.1 on virbr0.
  Oct 22 22:59:23 brian-pc NetworkManager[3557]:   [1571799563.6859] 
device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', 
sys-iface-state: 'removed')
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: 
service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 
pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
  Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection 
(0x55ccfb376e50), has been already deallocated — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 
0x55ccfb8d15f0 ==
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0   55ccfbc736c0 i   
resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1   55ccfbc73628 i   
resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2   55ccfbc73588 i   
resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3   55ccfbc734f0 i   
resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4   55ccfbc73430 i   
self-hosted:979 (7f522262dee0 @ 440)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: 
connection.get_setting_ip4_config is not a 
function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9
  Oct 22 22:59:23 brian-pc 

[Kernel-packages] [Bug 1852015] Re: System froze after resume from suspend

[Po-Hsu Lin]

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

** This bug has been marked a duplicate of bug 1852014
   System froze after resume from suspend

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

Title:
  System froze after resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was resuming from suspend and suffering from a non-responsive
  touchpad as described in [1] so I reconnected the mouse driver using

   echo -n "none" | sudo tee /sys/devices/platform/i8042/serio1/drvctl;
  sleep 1; echo -n "reconnect" | sudo tee
  /sys/devices/platform/i8042/serio1/drvctl

  
  several times until the mouse worked again. I then switched to Firefox and 
switched between tabs using a keyboard shortcut when suddenly the system froze 
completely. I couldn't even switch to a VT using CTRL-ALT-Fx. Using the 
MagicSysReg keys I could make force the laptop to reboot.

  
  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-21-generic 5.3.0-21.22
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnns   2715 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Nov 10 20:34:26 2019
  HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327
  InstallationDate: Installed on 2018-08-05 (462 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KGS5DU00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
crashkernel=512M-:192M crashkernel=512M-:192M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-21-generic N/A
   linux-backports-modules-5.3.0-21-generic  N/A
   linux-firmware1.183.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (23 days ago)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS5DU00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS5DU00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1239459]

[josephhummel007]

https://gamense.com/divinity-original-sin-2-builds-classes-
skills/">Divinity: Original Sin 2 Builds: combine the right skills
to make the perfect build for your character. Race: Lizard. Primary
Stat: Intelligence. Race: Undead. Primary Stat: Intelligence. Race:
Dwarf. Primary Stat: Intelligence. Race: Human. Primary Stat: Finesse.
Race: Elf. Primary Stat: Finesse. Race: Human.

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

Title:
  1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few
  seconds

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  With the new 3.11.0-12-generic kernel, wifi has problems to connect with many 
errors like these:
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: 
rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrea 1791 F pulseaudio
  Date: Sun Oct 13 23:45:04 2013
  HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15
  InstallationDate: Installed on 2013-10-12 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. X200CA
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200CA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1840543] Re: hid-generic 0005:0A5C:4503.0004: unknown main item tag 0x0

[Kai-Heng Feng]

Does it have any functional impact?

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

Title:
  hid-generic 0005:0A5C:4503.0004: unknown main item tag 0x0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg:
  [  271.473901] hid-generic 0005:0A5C:4503.0004: unknown main item tag 0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-10-generic 5.2.0-10.11
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3039 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   3039 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 17 10:40:06 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (257 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.
   
   enx000ec6c8dd33  no wireless extensions.
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-10-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-10-generic N/A
   linux-backports-modules-5.2.0-10-generic  N/A
   linux-firmware1.181
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (257 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1850239] Re: Repeated Ubuntu internal errors. Greyed out WiFi

[Kai-Heng Feng]

Doesn't seem to be a kernel bug.

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

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

Title:
  Repeated Ubuntu internal errors. Greyed out WiFi

Status in Ubuntu MATE:
  Confirmed

Bug description:
  Repeated notifications of internal errors in Ubuntu MATE 17.10. Lost
  WiFi connection and when I tried to reconnect, the WiFi menu item
  grayed out. Had to reboot to get WiFi back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-19-generic 5.3.0-19.20
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2762 F pulseaudio
   /dev/snd/controlC0:  robert 2762 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Oct 28 21:23:37 2019
  InstallationDate: Installed on 2018-12-16 (316 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1849141] Re: (Lenovo S130-11IGM) No touchpad after update to 18.04 4.15.0-65

[Kai-Heng Feng]

[   10.976257] i2c_hid i2c-SYNA3269:00: failed to reset device.

Can you please attach dmesg under 4.15.0-20?

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

Title:
  (Lenovo S130-11IGM) No touchpad after update to 18.04 4.15.0-65

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop works fine out of the box with 18.04  4.15.0-20. After the software 
update to 4.15.0-65, the touchpad is no longer detected. Cannot use 19.04 as 
seems to be a problem with emmc support 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883).
  Currently dropped back to 4.15.0-20.

  Followed the advice of installing synaptics, then evdev drivers but
  still same issue. Touchpad works fine in 4.15.0-20 using libinput.

  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-65-generic.
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  1276 F lxpanel
    james  1336 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xa131 irq 132'
     Mixer name : 'Realtek ALC269VC'
     Components : 'HDA:10ec0269,17aa380f,00100203 
HDA:8086280d,80860101,0010'
     Controls  : 58
     Simple ctrls  : 16
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-16 (4 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5627 Realtek Semiconductor Corp.
   Bus 001 Device 003: ID 0bda:c024 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81J1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic 
root=UUID=253cd622-8008-48b8-84eb-ce104896999e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-65-generic N/A
   linux-backports-modules-4.15.0-65-generic  N/A
   linux-firmware 1.173.9
  Tags:  bionic
  Uname: Linux 4.15.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HCN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32802WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad S130-11IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM:
  dmi.product.family: ideapad S130-11IGM
  dmi.product.name: 81J1
  dmi.product.version: Lenovo ideapad S130-11IGM
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Alkis Georgopoulos]

** No longer affects: epoptes (Ubuntu)

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04

[Kai-Heng Feng]

Would it be possible for you to do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the 
regression.

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

Title:
  (Lenovo S130-11IGM) emmc not working in 19.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and I'll 
happily get any other requested logging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1434 F pulseaudio
  CasperVersion: 1.405
  DistroRelease: Ubuntu 19.04
  IwConfig:
   enp0s21f0u1  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81J1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  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.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HCN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32802WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad S130-11IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM:
  dmi.product.family: ideapad S130-11IGM
  dmi.product.name: 81J1
  dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM
  dmi.product.version: Lenovo ideapad S130-11IGM
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc7/

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

Title:
  [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and
  55-75 Hz monitor.

  Booting Xubuntu 19.10 live iso with safe graphics options did give a
  stable desktop display, but

  xubuntu@xubuntu:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080 77.00* 
  xubuntu@xubuntu:~$ 

  The monitor is only supposed to have a maximum vertical refresh rate
  of 75 Hz. Xrandr reports 77 Hz as the only choice.  The monitor
  reports 60 Hz, not that I trust the monitor.

  Swapping monitors and running many reboots the situation seems to
  be...

  Old versions of Ubuntu (Bionic and Dingo) can handle the hardware.
  Standard boot sometimes gives a blank screen.  
  Standard boot sometimes gives a badly pixelated display 
  (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it).  
  Connecting a 144 Hz monitor convinces something (the firmware?) 
  that fast refreshes are OK on a slow monitor, or at least it fails to 
  reread and abide by the slow monitor's limitations when swapping back.
  Something, I don't know what, convinces the computer to run the display 
  at 60 Hz, sometimes. 

  The motherboard has three video ports; DP, HDMI and VGA (using an onboard 
  DP? to VGA converter chip).  The fast monitor has DP, HDMI and VGA ports, 
  but I only experimented with the DP connection.  The slow monitor has VGA and 
  DVI-D ports.  I experimented with VGA to VGA and HDMI via a passive adapter 
  to DVI.  When running in the badly pixelated mode xorg seems to think that 
  the VGA port is "DP-1".

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.427
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Oct 20 00:17:34 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash nomodeset ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Oct 19 23:52:52 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 

[Kernel-packages] [Bug 1842850] Re: NULL pointer dereference in kvm_mmu_flush_or_zap

[Kai-Heng Feng]

Does this issue still happen on an up-to-date kernel?

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

Title:
  NULL pointer dereference in kvm_mmu_flush_or_zap

Status in linux package in Ubuntu:
  Expired

Bug description:
  tonight one of our systems run into the following panic

  --
  kernel NULL pointer dereference at 
  kernel: [2468259.002689] IP: kvm_mmu_flush_or_zap+0x5/0x40 [kvm]
  kernel: [2468259.007758] PGD 0 P4D 0 
  kernel: [2468259.010483] Oops:  [#1] SMP PTI
  kernel: [2468259.014161] Modules linked in: vhost_net vhost tap xt_nat 
xt_REDIRECT nf_nat_redirect ip6table_mangle xt_mark xt_connmark xt_multiport 
xt_set ip_set_hash_net ip_set xt_CT xt_mac veth vxlan ip6_udp_tunnel udp_tunnel 
ip6table_raw xt_physdev xt_comment xt_CHECKSUM xt_tcpudp iptable_mangle 
iptable_raw ebtable_filter ebtables nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo br_netfilter bridge aufs rbd libceph binfmt_misc 8021q garp mrp stp 
llc bonding openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 rdma_ucm(OE) 
ib_ucm(OE) nf_defrag_ipv6 ib_ipoib(OE) ip6table_filter ib_umad(OE) xt_conntrack 
mlx5_fpga_tools(OE) mlx5_ib(OE) ib_uverbs(OE) iptable_filter mlx4_ib(OE) 
mlx4_en(OE) mlx4_core(OE) ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_addrtype 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack
  kernel: [2468259.085884]  ip_tables ipmi_ssif intel_rapl skx_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helper dell_smbios dcdbas cryptd intel_cstate 
dell_wmi_descriptor wmi_bmof intel_rapl_perf mei_me mei lpc_ich shpchp ipmi_si 
ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid rdma_cm(OE) iw_cm(OE) 
ib_cm(OE) ib_core(OE) iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip6_tables x_tables autofs4 mgag200 i2c_algo_bit ttm mlx5_core(OE) mlxfw(OE) 
devlink drm_kms_helper syscopyarea sysfillrect bnx2x mlx_compat(OE) sysimgblt 
ptp fb_sys_fops pps_core mdio drm libcrc32c ahci libahci wmi
  kernel: [2468259.148257] CPU: 21 PID: 3455197 Comm: CPU 11/KVM Tainted: G 
  OE4.15.0-55-generic #60~16.04.2-Ubuntu
  kernel: [2468259.158712] Hardware name: Dell Inc. PowerEdge R640/0PHYDR, BIOS 
2.2.10 05/15/2019
  kernel: [2468259.166510] RIP: 0010:kvm_mmu_flush_or_zap+0x5/0x40 [kvm]
  kernel: [2468259.172097] RSP: 0018:ad129f5b3ac8 EFLAGS: 00010246
  kernel: [2468259.177514] RAX:  RBX: 93dcbb5df5a8 RCX: 

  kernel: [2468259.184840] RDX:  RSI:  RDI: 
940b7ff38000
  kernel: [2468259.192168] RBP: ad129f5b3b30 R08: 0001 R09: 

  kernel: [2468259.199495] R10: 0001 R11: 0781 R12: 
940b7ff38000
  kernel: [2468259.206820] R13:  R14:  R15: 
00802800
  kernel: [2468259.214151] FS:  7f6de8ff9700() 
GS:9411ff28() knlGS:964c1f4c
  kernel: [2468259.222431] CS:  0010 DS:  ES:  CR0: 80050033
  kernel: [2468259.228369] CR2:  CR3: 00b54b6f8002 CR4: 
007626e0
  kernel: [2468259.235694] DR0:  DR1:  DR2: 

  kernel: [2468259.243018] DR3:  DR6: fffe0ff0 DR7: 
0400
  kernel: [2468259.250348] PKRU: 5554
  kernel: [2468259.253245] Call Trace:
  kernel: [2468259.255910]  ? kvm_mmu_get_page+0x29a/0x6b0 [kvm]
  kernel: [2468259.260814]  __direct_map.part.124+0xf5/0x220 [kvm]
  kernel: [2468259.265901]  tdp_page_fault+0x264/0x290 [kvm]
  kernel: [2468259.270462]  kvm_mmu_page_fault+0x62/0x170 [kvm]
  kernel: [2468259.275278]  handle_ept_violation+0xae/0x140 [kvm_intel]
  kernel: [2468259.280781]  vmx_handle_exit+0xb3/0xcd0 [kvm_intel]
  kernel: [2468259.285867]  ? vmx_vcpu_run+0x41d/0x600 [kvm_intel]
  kernel: [2468259.290960]  vcpu_enter_guest+0x451/0x1280 [kvm]
  kernel: [2468259.295774]  ? vmx_sync_pir_to_irr+0x39/0x70 [kvm_intel]
  kernel: [2468259.301307]  kvm_arch_vcpu_ioctl_run+0x270/0x3d0 [kvm]
  kernel: [2468259.306652]  ? kvm_arch_vcpu_ioctl_run+0x270/0x3d0 [kvm]
  kernel: [2468259.312163]  kvm_vcpu_ioctl+0x33a/0x610 [kvm]
  kernel: [2468259.317432]  ? do_futex+0x10f/0x500
  kernel: [2468259.321830]  do_vfs_ioctl+0xa4/0x600
  kernel: [2468259.326244]  ? SyS_futex+0x7f/0x180
  kernel: [2468259.330523]  SyS_ioctl+0x79/0x90
  kernel: [2468259.334561]  do_syscall_64+0x73/0x130
  kernel: [2468259.338992]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  kernel: [2468259.344817] RIP: 0033:0x7f6e379b2f47
  kernel: [2468259.349187] RSP: 002b:7f6de8ff88f8 EFLAGS: 0246 
ORIG_RAX: 0010
  kernel: [2468259.357529] RAX: ffda RBX: ae80 RCX: 
7f6e379b2f47
  kernel: [2468259.365415] RDX: 

[Kernel-packages] [Bug 1840438] Re: linux-image-4.4.0-159-generic BUG on bcache

[Kai-Heng Feng]

Does it still happen on an up-to-date kernel?

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

Title:
  linux-image-4.4.0-159-generic BUG on bcache

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL 
pointer dereference" with bcache module
  the kernel never boots then.
  blacklisting the bcache module resolves the problem.
  For more strings please see attached image

  
  Ubuntu 4.4.0-159.187-generic 4.4.185
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 16 13:18 seq
   crw-rw 1 root audio 116, 33 Aug 16 13:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42
  InstallationDate: Installed on 2016-06-08 (1163 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant SE316M1
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic 
root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 
modprobe.blacklist=bcache
  ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-159-generic N/A
   linux-backports-modules-4.4.0-159-generic  N/A
   linux-firmware 1.157.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-159-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 07/02/2013
  dmi.bios.vendor: HP
  dmi.bios.version: R02
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant SE316M1
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1840498] Re: WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568 ieee80211_rx_napi+0x2e6/0x580 [mac80211]

[Kai-Heng Feng]

Does it have any functionality impact?

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

Title:
  WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568
  ieee80211_rx_napi+0x2e6/0x580 [mac80211]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg:
  [ 4249.706469] [ cut here ]
  [ 4249.706474] Rate marked as an HT rate but passed status->rate_idx is not 
an MCS index [0-76]: 127 (0x7f)
  [ 4249.706596] WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568 
ieee80211_rx_napi+0x2e6/0x580 [mac80211]
  [ 4249.706597] Modules linked in: snd_seq_dummy ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs rfcomm hidp pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) ccm cmac bnep snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio arc4 nls_iso8859_1 
mei_hdcp snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl 
snd_soc_skl_ipc x86_pkg_temp_thermal intel_powerclamp snd_soc_sst_ipc coretemp 
snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi kvm_intel snd_soc_core 
kvm snd_compress irqbypass ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul snd_pcm crc32_pclmul 
ghash_clmulni_intel uvcvideo videobuf2_vmalloc videobuf2_memops ath9k_htc 
videobuf2_v4l2 ath9k_common videobuf2_common ath9k_hw videodev ath media 
snd_seq_midi mac80211 aesni_intel snd_seq_midi_event snd_rawmidi joydev 
cfg80211 aes_x86_64 btusb crypto_simd btrtl cryptd glue_helper btbcm snd_seq 
btintel intel_cstate input_leds i915 bluetooth snd_seq_device
  [ 4249.706657]  intel_rapl_perf snd_timer ecdh_generic ecc hp_wmi 
drm_kms_helper snd serio_raw hid_sensor_accel_3d drm hid_sensor_magn_3d 
hid_sensor_gyro_3d hid_sensor_incl_3d hid_sensor_rotation spi_pxa2xx_platform 
hid_sensor_trigger industrialio_triggered_buffer kfifo_buf 
hid_sensor_iio_common mei_me dw_dmac i2c_algo_bit idma64 
intel_xhci_usb_role_switch soundcore dw_dmac_core 8250_dw wmi_bmof mei 
hid_multitouch virt_dma processor_thermal_device fb_sys_fops 
intel_wmi_thunderbolt industrialio intel_pch_thermal roles intel_soc_dts_iosf 
syscopyarea sysfillrect sysimgblt int3403_thermal int340x_thermal_zone 
soc_button_array intel_vbtn sparse_keymap hp_accel int3400_thermal 
acpi_thermal_rel hp_wireless lis3lv02d input_polldev acpi_pad mac_hid 
sch_fq_codel parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 
btrfs xor zstd_compress raid6_pq libcrc32c hid_sensor_custom hid_sensor_hub 
intel_ishtp_loader intel_ishtp_hid hid_generic psmouse intel_ish_ipc ahci 
intel_ishtp i2c_i801 sdhci_pci
  [ 4249.706714]  libahci cqhci intel_lpss_pci sdhci i2c_hid intel_lpss wmi hid 
video pinctrl_sunrisepoint pinctrl_intel
  [ 4249.706730] CPU: 4 PID: 0 Comm: swapper/4 Tainted: G   OE 
5.2.0-10-generic #11-Ubuntu
  [ 4249.706732] Hardware name: HP HP Pavilion x360 Convertible 14-cd0xxx/8486, 
BIOS F.34 04/29/2019
  [ 4249.706785] RIP: 0010:ieee80211_rx_napi+0x2e6/0x580 [mac80211]
  [ 4249.706792] Code: 42 18 0f 8d 76 cc 04 00 48 8b 42 08 48 8d 0c 49 48 8d 14 
88 e9 fb fd ff ff 0f b6 f1 48 c7 c7 c8 4f 11 c1 89 f2 e8 16 de 3d ee <0f> 0b 4c 
89 e7 e8 a0 98 c1 ee eb a4 80 f9 0b 0f 86 5e 01 00 00 80
  [ 4249.706794] RSP: 0018:b16b01aa0dd8 EFLAGS: 00010286
  [ 4249.706798] RAX:  RBX: 89061a9b47a0 RCX: 
0006
  [ 4249.706800] RDX: 0007 RSI: 0086 RDI: 
890625d17440
  [ 4249.706802] RBP: b16b01aa0e68 R08: 03fb R09: 
0004
  [ 4249.706804] R10:  R11: 0001 R12: 
89060ba6ef00
  [ 4249.706805] R13:  R14:  R15: 
0292
  [ 4249.706808] FS:  () GS:890625d0() 
knlGS:
  [ 4249.706811] CS:  0010 DS:  ES:  CR0: 80050033
  [ 4249.706813] CR2: 152dba73 CR3: 000316c0a001 CR4: 
003606e0
  [ 4249.706815] Call Trace:
  [ 4249.706819]  
  [ 4249.706831]  ? ath9k_rx_prepare.isra.0+0x242/0x290 [ath9k_htc]
  [ 4249.706841]  ath9k_rx_tasklet+0x106/0x1c0 [ath9k_htc]
  [ 4249.706852]  tasklet_action_common.isra.0+0x60/0x110
  [ 4249.706858]  tasklet_action+0x22/0x30
  [ 4249.706866]  __do_softirq+0xe1/0x2f4
  [ 4249.706872]  irq_exit+0xb6/0xc0
  [ 4249.706878]  do_IRQ+0x86/0xe0
  [ 4249.706883]  common_interrupt+0xf/0xf
  [ 4249.706885]  
  [ 4249.706893] RIP: 0010:cpuidle_enter_state+0xc5/0x420
  [ 4249.706897] Code: ff e8 0f 3c 84 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 
f6 c4 02 0f 85 3d 03 00 00 31 ff e8 c2 90 8a ff fb 66 0f 1f 44 00 00 <45> 85 ed 
0f 89 d1 01 00 00 41 c7 44 24 10 00 00 00 00 48 83 c4 18
  [ 4249.706899] RSP: 0018:b16b019afe38 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 4249.706902] RAX: 890625d2b2c0 RBX: b0b57b60 RCX: 
001f
  [ 4249.706904] RDX:  RSI: 471c71c7 

[Kernel-packages] [Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud

[Nobuto Murata]

I'm just not sure how it can be merged to focal so raised a question:
https://lists.ubuntu.com/archives/kernel-team/2019-November/105393.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/1848481

Title:
  cloudimg: no iavf/i40evf module so no network available with SR-IOV
  enabled cloud

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in livecd-rootfs source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in livecd-rootfs source package in Disco:
  New
Status in linux source package in Eoan:
  Fix Committed
Status in livecd-rootfs source package in Eoan:
  New
Status in linux source package in Focal:
  In Progress
Status in livecd-rootfs source package in Focal:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact]
  Intel's VF drivers such as igbvf and ixgbevf are already available in
  generic. It makes sense to add i40evf especially for SR-IOV enabled clouds 
with Intel X710/XXV710/XL710.

  [Fix]
  Add i40evf to linux-modules package

  [Test]
  Extract linux-modules to check if i40evf is there

  [Regression Potential]
  Low   

  = original bug description =
  For example with bionic, i40evf module is in 
linux-modules-extra-4.15*-generic. However, cloudimg doesn't have 
linux-modules-extra seeded:

  $ curl -s 
http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest
 | grep linux-
  linux-base  4.5ubuntu1
  linux-headers-4.15.0-65 4.15.0-65.74
  linux-headers-4.15.0-65-generic 4.15.0-65.74
  linux-headers-generic   4.15.0.65.67
  linux-headers-virtual   4.15.0.65.67
  linux-image-4.15.0-65-generic   4.15.0-65.74
  linux-image-virtual 4.15.0.65.67
  linux-modules-4.15.0-65-generic 4.15.0-65.74
  linux-virtual   4.15.0.65.67

  We don't need the whole linux-modules-extra because the size is not
  small, but we need some VF drivers in cloud guest image embedded for
  SR-IOV enabled cloud including OpenStack. Otherwise, the guest is
  unusable with no network device.

  $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size
  Installed-Size: 171 MB

  $ du -h 
/lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko
  148K
/lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: livecd-rootfs (not installed)
  ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Thu Oct 17 10:48:41 2019
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: livecd-rootfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1845677] Re: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen

[Hui Wang]

About the hdmi audio on the dock, with the current kernel, it can't
work. And Intel is working on it, kernel patches are ready, but they
need to modify the ucm. After they finish them, we will integrate them
into the ubuntu linux.

Please wait for 1 month or about 2 months.

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

Title:
  volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1
  Carbon 7th gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo ThinkPad X1 Carbon 7th generation using the built-in
  speakers, the volume is either off or on, there's no gradation in
  volume when I move the slider up or down.

  If I enable Over-Amplification than there's gradation in volume when I
  turn the volume up past 100%, but not for 0-100%.

  This problem does not occur with a headset plugged into the 3.5mm
  jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-12-generic 5.3.0-12.13
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik3746 F pulseaudio
   /dev/snd/pcmC0D0p:   jik3746 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 11:07:44 2019
  InstallationDate: Installed on 2019-09-12 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-12-generic N/A
   linux-backports-modules-5.3.0-12-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1813620] Re: Xorg indefinitely hangs in kernelspace at least 2-3 times a day

[Kai-Heng Feng]

Please test drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip

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

Title:
  Xorg indefinitely hangs in kernelspace at least 2-3 times a day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The graphical environment seems to hang when scrolling web pages in
  Firefox. Can't reliably reproduce during every scrolling, but it has
  happened at least 5 times in the past 7 days. Happens in Kubuntu VM-s
  running under KVM and QEMU (3.1.0) on multiple host machines.

  This issue only started to happen sometime this month. First these
  VM-s were running 18.04 so I was hoping that updating them to 18.10
  would help, but it didn't. I'm guessing that some kernel update for
  both bionic and cosmic causes this.

  Since this bug causes the graphical environment to become totally
  unresponsive, this has already already cost me some lost data, but
  very fortunately not much.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jotik  1962 F pulseaudio
  Date: Mon Jan 28 18:09:57 2019
  HibernationDevice: RESUME=UUID=9dfc65ab-a122-4254-8806-a580fea3c953
  InstallationDate: Installed on 2015-10-18 (1197 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=78ee528a-a065-4522-b2ca-a1959850a740 ro console=ttyS0 verbose
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2019-01-20 (7 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.11.0-20180624_124920-prayer
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.3
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.11.0-20180624_124920-prayer:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.3:cvnQEMU:ct1:cvrpc-i440fx-2.3:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.3
  dmi.sys.vendor: QEMU
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2015-10-18 (1387 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: linux (not installed)
  Tags:  disco
  Uname: Linux 5.2.0-050200rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to disco on 2019-04-16 (112 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1849720] Re: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)

[Zach Graceffa]

@Christian - 5.4-rc7 worked for both e1000e and virtio NICs. No crash as
of about 15 minutes.

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

Title:
  KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  In Progress

Bug description:
  After upgrading to Ubuntu 19.10 I noticed that all of my Windows
  Servers VMs would cause a hard crash on the Host OS shortly after
  starting up the VM.  I tracked it down to the Guest OS attempting to
  use the Network Connection, and if I disabled the virtual NIC for the
  VM, everything runs OK (albeit without a working network connection
  for the Guest OS).  Note that I'm just using the built in virtual
  network called "default" that get's installed by default and uses NAT
  forwarding.

  I believe the problem is related to AppArmor, as I noticed some errors
  present in various log files.

  Unfortunately, due to a time critical project I had to roll back to
  Ubuntu 19.04 and didn't capture any of the log files.  I did, however,
  find another user on Reddit with the exact same problems that I
  encountered and he agreed to let me post the log files.

  Here are what are think are the relevant pieces from the log files:

  ===

  Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM
  Oct 22 22:59:23 brian-pc kernel: [   67.001284] device virbr0-nic left 
promiscuous mode
  Oct 22 22:59:23 brian-pc kernel: [   67.001298] virbr0: port 1(virbr0-nic) 
entered disabled state
  Oct 22 22:59:23 brian-pc NetworkManager[3557]:   [1571799563.3862] 
device (virbr0-nic): released from master device virbr0
  Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer 
relevant for mDNS.
  Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on 
interface virbr0.IPv4 with address 192.168.122.1.
  Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 
192.168.122.1 on virbr0.
  Oct 22 22:59:23 brian-pc NetworkManager[3557]:   [1571799563.6859] 
device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', 
sys-iface-state: 'removed')
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: 
service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 
pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
  Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection 
(0x55ccfb376e50), has been already deallocated — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 
0x55ccfb8d15f0 ==
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0   55ccfbc736c0 i   
resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1   55ccfbc73628 i   
resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2   55ccfbc73588 i   
resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3   55ccfbc734f0 i   
resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4   55ccfbc73430 i   
self-hosted:979 (7f522262dee0 @ 440)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: 
connection.get_setting_ip4_config is not a 
function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: 
connectionSettings is 
null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9
  Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: 
connectionSettings is 
null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9
  Oct 22 22:59:23 brian-pc dbus-daemon[1610]: 

[Kernel-packages] [Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud

[Nobuto Murata]

** Changed in: linux (Ubuntu Disco)
 Assignee: gerald.yang (gerald-yang-tw) => Nobuto Murata (nobuto)

** Changed in: linux (Ubuntu Eoan)
 Assignee: gerald.yang (gerald-yang-tw) => Nobuto Murata (nobuto)

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

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

Title:
  cloudimg: no iavf/i40evf module so no network available with SR-IOV
  enabled cloud

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in livecd-rootfs source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in livecd-rootfs source package in Disco:
  New
Status in linux source package in Eoan:
  Fix Committed
Status in livecd-rootfs source package in Eoan:
  New
Status in linux source package in Focal:
  In Progress
Status in livecd-rootfs source package in Focal:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact]
  Intel's VF drivers such as igbvf and ixgbevf are already available in
  generic. It makes sense to add i40evf especially for SR-IOV enabled clouds 
with Intel X710/XXV710/XL710.

  [Fix]
  Add i40evf to linux-modules package

  [Test]
  Extract linux-modules to check if i40evf is there

  [Regression Potential]
  Low   

  = original bug description =
  For example with bionic, i40evf module is in 
linux-modules-extra-4.15*-generic. However, cloudimg doesn't have 
linux-modules-extra seeded:

  $ curl -s 
http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest
 | grep linux-
  linux-base  4.5ubuntu1
  linux-headers-4.15.0-65 4.15.0-65.74
  linux-headers-4.15.0-65-generic 4.15.0-65.74
  linux-headers-generic   4.15.0.65.67
  linux-headers-virtual   4.15.0.65.67
  linux-image-4.15.0-65-generic   4.15.0-65.74
  linux-image-virtual 4.15.0.65.67
  linux-modules-4.15.0-65-generic 4.15.0-65.74
  linux-virtual   4.15.0.65.67

  We don't need the whole linux-modules-extra because the size is not
  small, but we need some VF drivers in cloud guest image embedded for
  SR-IOV enabled cloud including OpenStack. Otherwise, the guest is
  unusable with no network device.

  $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size
  Installed-Size: 171 MB

  $ du -h 
/lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko
  148K
/lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: livecd-rootfs (not installed)
  ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Thu Oct 17 10:48:41 2019
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: livecd-rootfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1846016] Re: Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD GEO_TX_POWER_LIMIT

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   Status: Invalid => Fix Committed

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

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

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

Title:
  Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD
  GEO_TX_POWER_LIMIT

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Confirmed
Status in linux-oem-osp1 source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Confirmed
Status in linux-oem-osp1 source package in Eoan:
  Confirmed

Bug description:
  I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since
  yesterday.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-firmware 1.182
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 30 20:57:08 2019
  Dependencies:

  InstallationDate: Installed on 2019-07-23 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago)

  --
  Also found on Ubuntu-certified HP EliteDesk 800 G3 DM.

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

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

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

[Khaled El Mously]

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

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

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

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

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact] 
  TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.

  [Fix]
  Disable HPET on affected SoC generations, currently happens to CFL and
  ICL.
   
  [Test]
  I can confirm disabling HPET can avoid this issue.

  [Regression Potential]
  Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
  harmless to disable HPET on these platforms.

  === Original Bug Report ===
  This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

    [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
    [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

    [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
    [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
    [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
    [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
    [ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

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

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

[Kernel-packages] [Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud

[Khaled El Mously]

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

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

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

Title:
  cloudimg: no iavf/i40evf module so no network available with SR-IOV
  enabled cloud

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in livecd-rootfs source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in livecd-rootfs source package in Disco:
  New
Status in linux source package in Eoan:
  Fix Committed
Status in livecd-rootfs source package in Eoan:
  New
Status in linux source package in Focal:
  Fix Committed
Status in livecd-rootfs source package in Focal:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact]
  Intel's VF drivers such as igbvf and ixgbevf are already available in
  generic. It makes sense to add i40evf especially for SR-IOV enabled clouds 
with Intel X710/XXV710/XL710.

  [Fix]
  Add i40evf to linux-modules package

  [Test]
  Extract linux-modules to check if i40evf is there

  [Regression Potential]
  Low   

  = original bug description =
  For example with bionic, i40evf module is in 
linux-modules-extra-4.15*-generic. However, cloudimg doesn't have 
linux-modules-extra seeded:

  $ curl -s 
http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest
 | grep linux-
  linux-base  4.5ubuntu1
  linux-headers-4.15.0-65 4.15.0-65.74
  linux-headers-4.15.0-65-generic 4.15.0-65.74
  linux-headers-generic   4.15.0.65.67
  linux-headers-virtual   4.15.0.65.67
  linux-image-4.15.0-65-generic   4.15.0-65.74
  linux-image-virtual 4.15.0.65.67
  linux-modules-4.15.0-65-generic 4.15.0-65.74
  linux-virtual   4.15.0.65.67

  We don't need the whole linux-modules-extra because the size is not
  small, but we need some VF drivers in cloud guest image embedded for
  SR-IOV enabled cloud including OpenStack. Otherwise, the guest is
  unusable with no network device.

  $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size
  Installed-Size: 171 MB

  $ du -h 
/lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko
  148K
/lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: livecd-rootfs (not installed)
  ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Thu Oct 17 10:48:41 2019
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: livecd-rootfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1851876] Re: Bionic update: upstream stable patchset 2019-11-08

[Khaled El Mously]

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

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

Title:
  Bionic update: upstream stable patchset 2019-11-08

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2019-11-08

Ported from the following upstream stable releases:
v4.14.151, v4.19.81

     from git://git.kernel.org/

  scsi: ufs: skip shutdown if hba is not powered
  scsi: megaraid: disable device when probe failed after enabled device
  scsi: qla2xxx: Fix unbound sleep in fcport delete path.
  ARM: OMAP2+: Fix missing reset done flag for am3 and am43
  ieee802154: ca8210: prevent memory leak
  ARM: dts: am4372: Set memory bandwidth limit for DISPC
  net: dsa: qca8k: Use up to 7 ports for all operations
  MIPS: dts: ar9331: fix interrupt-controller size
  xen/efi: Set nonblocking callbacks
  nl80211: fix null pointer dereference
  mac80211: fix txq null pointer dereference
  mips: Loongson: Fix the link time qualifier of 'serial_exit()'
  net: hisilicon: Fix usage of uninitialized variable in function 
mdio_sc_cfg_reg_write()
  namespace: fix namespace.pl script to support relative paths
  Revert "drm/radeon: Fix EEH during kexec"
  ocfs2: fix panic due to ocfs2_wq is null
  ipv4: Return -ENETUNREACH if we can't create route but saddr is valid
  net: bcmgenet: Fix RGMII_MODE_EN value for GENET v1/2/3
  net: bcmgenet: Set phydev->dev_flags only for internal PHYs
  net: i82596: fix dma_alloc_attr for sni_82596
  net: stmmac: disable/enable ptp_ref_clk in suspend/resume flow
  sctp: change sctp_prot .no_autobind with true
  net: avoid potential infinite loop in tc_ctl_action()
  memfd: Fix locking when tagging pins
  USB: legousbtower: fix memleak on disconnect
  ALSA: hda/realtek - Add support for ALC711
  usb: udc: lpc32xx: fix bad bit shift operation
  USB: serial: ti_usb_3410_5052: fix port-close races
  USB: ldusb: fix memleak on disconnect
  USB: usblp: fix use-after-free on disconnect
  USB: ldusb: fix read info leaks
  arm64: v8.4: Support for new floating point multiplication instructions
  arm64: Documentation: cpu-feature-registers: Remove RES0 fields
  arm64: Expose Arm v8.4 features
  arm64: move SCTLR_EL{1,2} assertions to 
  arm64: add PSR_AA32_* definitions
  arm64: Introduce sysreg_clear_set()
  arm64: capabilities: Update prototype for enable call back
  arm64: capabilities: Move errata work around check on boot CPU
  arm64: capabilities: Move errata processing code
  arm64: capabilities: Prepare for fine grained capabilities
  arm64: capabilities: Add flags to handle the conflicts on late CPU
  arm64: capabilities: Unify the verification
  arm64: capabilities: Filter the entries based on a given mask
  arm64: capabilities: Prepare for grouping features and errata work arounds
  arm64: capabilities: Split the processing of errata work arounds
  arm64: capabilities: Allow features based on local CPU scope
  arm64: capabilities: Group handling of features and errata workarounds
  arm64: capabilities: Introduce weak features based on local CPU
  arm64: capabilities: Restrict KPTI detection to boot-time CPUs
  arm64: capabilities: Add support for features enabled early
  arm64: capabilities: Change scope of VHE to Boot CPU feature
  arm64: capabilities: Clean up midr range helpers
  arm64: Add helpers for checking CPU MIDR against a range
  arm64: Add MIDR encoding for Arm Cortex-A55 and Cortex-A35
  arm64: capabilities: Add support for checks based on a list of MIDRs
  arm64: KVM: Use SMCCC_ARCH_WORKAROUND_1 for Falkor BP hardening
  arm64: don't zero DIT on signal return
  arm64: Get rid of __smccc_workaround_1_hvc_*
  arm64: cpufeature: Detect SSBS and advertise to userspace
  arm64: ssbd: Add support for PSTATE.SSBS rather than trapping to EL3
  KVM: arm64: Set SCTLR_EL2.DSSBS if SSBD is forcefully disabled and !vhe
  arm64: fix SSBS sanitization
  arm64: Add sysfs vulnerability show for spectre-v1
  arm64: add sysfs vulnerability show for meltdown
  arm64: enable generic CPU vulnerabilites support
  arm64: Always enable ssb vulnerability detection
  arm64: Provide a command line to disable spectre_v2 mitigation
  arm64: Advertise mitigation of Spectre-v2, or lack thereof
  arm64: Always enable spectre-v2 vulnerability detection
  arm64: 

[Kernel-packages] [Bug 1851550] Re: Eoan update: 5.3.9 upstream stable release

[Khaled El Mously]

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

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

Title:
  Eoan update: 5.3.9 upstream stable release

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

Bug description:
  SRU Justification

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

  * io_uring: fix up O_NONBLOCK handling for sockets
  * dm snapshot: introduce account_start_copy() and account_end_copy()
  * dm snapshot: rework COW throttling to fix deadlock
  * Btrfs: fix inode cache block reserve leak on failure to allocate data space
  * btrfs: qgroup: Always free PREALLOC META reserve in 
btrfs_delalloc_release_extents()
  * iio: adc: meson_saradc: Fix memory allocation order
  * iio: fix center temperature of bmc150-accel-core
  * libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature
  * perf tests: Avoid raising SEGV using an obvious NULL dereference
  * perf map: Fix overlapped map handling
  * perf script brstackinsn: Fix recovery from LBR/binary mismatch
  * perf jevents: Fix period for Intel fixed counters
  * perf tools: Propagate get_cpuid() error
  * perf annotate: Propagate perf_env__arch() error
  * perf annotate: Fix the signedness of failure returns
  * perf annotate: Propagate the symbol__annotate() error return
  * perf annotate: Fix arch specific ->init() failure errors
  * perf annotate: Return appropriate error code for allocation failures
  * perf annotate: Don't return -1 for error when doing BPF disassembly
  * staging: rtl8188eu: fix null dereference when kzalloc fails
  * RDMA/siw: Fix serialization issue in write_space()
  * RDMA/hfi1: Prevent memory leak in sdma_init
  * RDMA/iw_cxgb4: fix SRQ access from dump_qp()
  * RDMA/iwcm: Fix a lock inversion issue
  * HID: hyperv: Use in-place iterator API in the channel callback
  * kselftest: exclude failed TARGETS from runlist
  * selftests/kselftest/runner.sh: Add 45 second timeout per test
  * nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request
  * arm64: cpufeature: Effectively expose FRINT capability to userspace
  * arm64: Fix incorrect irqflag restore for priority masking for compat
  * arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 #1542419
  * tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()'
  * tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()'
  * serial/sifive: select SERIAL_EARLYCON
  * tty: n_hdlc: fix build on SPARC
  * misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach
  * RDMA/core: Fix an error handling path in 'res_get_common_doit()'
  * RDMA/cm: Fix memory leak in cm_add/remove_one
  * RDMA/nldev: Reshuffle the code to avoid need to rebind QP in error path
  * RDMA/mlx5: Do not allow rereg of a ODP MR
  * RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu
  * RDMA/mlx5: Add missing synchronize_srcu() for MW cases
  * gpio: max77620: Use correct unit for debounce times
  * fs: cifs: mute -Wunused-const-variable message
  * arm64: vdso32: Fix broken compat vDSO build warnings
  * arm64: vdso32: Detect binutils support for dmb ishld
  * serial: mctrl_gpio: Check for NULL pointer
  * serial: 8250_omap: Fix gpio check for auto RTS/CTS
  * arm64: Default to building compat vDSO with clang when CONFIG_CC_IS_CLANG
  * arm64: vdso32: Don't use KBUILD_CPPFLAGS unconditionally
  * efi/cper: Fix endianness of PCIe class code
  * efi/x86: Do not clean dummy variable in kexec path
  * MIPS: include: Mark __cmpxchg as __always_inline
  * riscv: avoid kernel hangs when trapped in BUG()
  * riscv: avoid sending a SIGTRAP to a user thread trapped in WARN()
  * riscv: Correct the handling of unexpected ebreak in do_trap_break()
  * x86/xen: Return from panic notifier
  * ocfs2: clear zero in unaligned direct IO
  * fs: ocfs2: fix possible null-pointer dereferences in 
ocfs2_xa_prepare_entry()
  * fs: ocfs2: fix a possible null-pointer dereference in 
ocfs2_write_end_nolock()
  * fs: ocfs2: fix a possible null-pointer dereference in 
ocfs2_info_scan_inode_alloc()
  * btrfs: silence maybe-uninitialized warning in clone_range
  * arm64: armv8_deprecated: Checking return value for memory allocation
  * x86/cpu: Add Comet Lake to the Intel CPU models header
  * sched/fair: Scale bandwidth quota and period without losing quota/period 
ratio precision
  * sched/vtime: Fix guest/system mis-accounting on task switch
  * perf/core: Rework memory 

[Kernel-packages] [Bug 1852110] Re: Xenial update: 4.4.200 upstream stable release

[Khaled El Mously]

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

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

Title:
  Xenial update: 4.4.200 upstream stable release

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

Bug description:
  SRU Justification

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

  * kbuild: add -fcf-protection=none when using retpoline flags
  * regulator: ti-abb: Fix timeout in ti_abb_wait_txdone/ti_abb_clear_all_txdone
  * regulator: pfuze100-regulator: Variable "val" in pfuze100_regulator_probe() 
could be uninitialized
  * ASoc: rockchip: i2s: Fix RPM imbalance
  * ARM: dts: logicpd-torpedo-som: Remove twl_keypad
  * ARM: mm: fix alignment handler faults under memory pressure
  * scsi: sni_53c710: fix compilation error
  * scsi: fix kconfig dependency warning related to 53C700_LE_ON_BE
  * perf kmem: Fix memory leak in compact_gfp_flags()
  * scsi: target: core: Do not overwrite CDB byte 1
  * of: unittest: fix memory leak in unittest_data_add
  * MIPS: bmips: mark exception vectors as char arrays
  * cifs: Fix cifsInodeInfo lock_sem deadlock when reconnect occurs
  * dccp: do not leak jiffies on the wire
  * net: fix sk_page_frag() recursion from memory reclaim
  * net: hisilicon: Fix ping latency when deal with high throughput
  * UBUNTU: SAUCE: Revert "net: Zeroing the structure ethtool_wolinfo in 
ethtool_get_wol()"
  * net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol()
  * net: add READ_ONCE() annotation in __skb_wait_for_more_packets()
  * vxlan: check tun_info options_len properly
  * net/mlx4_core: Dynamically set guaranteed amount of counters per VF
  * inet: stop leaking jiffies on the wire
  * net/flow_dissector: switch to siphash
  * dmaengine: qcom: bam_dma: Fix resource leak
  * ARM: 8051/1: put_user: fix possible data corruption in put_user
  * ARM: 8478/2: arm/arm64: add arm-smccc
  * ARM: 8479/2: add implementation for arm-smccc
  * ARM: 8480/2: arm64: add implementation for arm-smccc
  * ARM: 8481/2: drivers: psci: replace psci firmware calls
  * ARM: uaccess: remove put_user() code duplication
  * ARM: Move system register accessors to asm/cp15.h
  * arm/arm64: KVM: Advertise SMCCC v1.1
  * arm64: KVM: Report SMCCC_ARCH_WORKAROUND_1 BP hardening support
  * firmware/psci: Expose PSCI conduit
  * firmware/psci: Expose SMCCC version through psci_ops
  * arm/arm64: smccc: Make function identifiers an unsigned quantity
  * arm/arm64: smccc: Implement SMCCC v1.1 inline primitive
  * arm/arm64: smccc: Add SMCCC-specific return codes
  * arm/arm64: smccc-1.1: Make return values unsigned long
  * arm/arm64: smccc-1.1: Handle function result as parameters
  * ARM: add more CPU part numbers for Cortex and Brahma B15 CPUs
  * ARM: bugs: prepare processor bug infrastructure
  * ARM: bugs: hook processor bug checking into SMP and suspend paths
  * ARM: bugs: add support for per-processor bug checking
  * ARM: spectre: add Kconfig symbol for CPUs vulnerable to Spectre
  * ARM: spectre-v2: harden branch predictor on context switches
  * ARM: spectre-v2: add Cortex A8 and A15 validation of the IBE bit
  * ARM: spectre-v2: harden user aborts in kernel space
  * ARM: spectre-v2: add firmware based hardening
  * ARM: spectre-v2: warn about incorrect context switching functions
  * ARM: spectre-v1: add speculation barrier (csdb) macros
  * ARM: spectre-v1: add array_index_mask_nospec() implementation
  * ARM: spectre-v1: fix syscall entry
  * ARM: signal: copy registers using __copy_from_user()
  * ARM: vfp: use __copy_from_user() when restoring VFP state
  * ARM: oabi-compat: copy semops using __copy_from_user()
  * ARM: use __inttype() in get_user()
  * ARM: spectre-v1: use get_user() for __get_user()
  * ARM: spectre-v1: mitigate user accesses
  * ARM: 8789/1: signal: copy registers using __copy_to_user()
  * ARM: 8791/1: vfp: use __copy_to_user() when saving VFP state
  * ARM: 8792/1: oabi-compat: copy oabi events using __copy_to_user()
  * ARM: 8793/1: signal: replace __put_user_error with __put_user
  * ARM: 8794/1: uaccess: Prevent speculative use of the current addr_limit
  * ARM: 8795/1: spectre-v1.1: use put_user() for __put_user()
  * ARM: 8796/1: spectre-v1,v1.1: provide helpers for address sanitization
  * ARM: 8810/1: vfp: Fix wrong assignement to ufp_exc
  * ARM: make lookup_processor_type() non-__init
  * ARM: split out processor lookup
  * ARM: clean up per-processor 

[Kernel-packages] [Bug 1852111] Re: Eoan update: 5.3.10 upstream stable release

[Khaled El Mously]

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

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

Title:
  Eoan update: 5.3.10 upstream stable release

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

Bug description:
  SRU Justification

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

  * regulator: of: fix suspend-min/max-voltage parsing
  * ASoC: samsung: arndale: Add missing OF node dereferencing
  * ASoC: wm8994: Do not register inapplicable controls for WM1811
  * regulator: da9062: fix suspend_enable/disable preparation
  * ASoC: topology: Fix a signedness bug in soc_tplg_dapm_widget_create()
  * arm64: dts: allwinner: a64: pine64-plus: Add PHY regulator delay
  * arm64: dts: allwinner: a64: Drop PMU node
  * arm64: dts: allwinner: a64: sopine-baseboard: Add PHY regulator delay
  * arm64: dts: Fix gpio to pinmux mapping
  * regulator: ti-abb: Fix timeout in ti_abb_wait_txdone/ti_abb_clear_all_txdone
  * pinctrl: intel: Allocate IRQ chip dynamic
  * ASoC: SOF: loader: fix kernel oops on firmware boot failure
  * ASoC: SOF: topology: fix parse fail issue for byte/bool tuple types
  * ASoC: SOF: Intel: hda: fix warnings during FW load
  * ASoC: SOF: Intel: initialise and verify FW crash dump data.
  * ASoC: SOF: Intel: hda: Disable DMI L1 entry during capture
  * ASoC: rt5682: add NULL handler to set_jack function
  * ASoC: intel: sof_rt5682: add remove function to disable jack
  * ASoC: intel: bytcr_rt5651: add null check to support_button_press
  * regulator: pfuze100-regulator: Variable "val" in pfuze100_regulator_probe() 
could be uninitialized
  * ASoC: wm_adsp: Don't generate kcontrols without READ flags
  * ASoc: rockchip: i2s: Fix RPM imbalance
  * arm64: dts: rockchip: fix Rockpro64 RK808 interrupt line
  * ARM: dts: logicpd-torpedo-som: Remove twl_keypad
  * arm64: dts: rockchip: fix RockPro64 vdd-log regulator settings
  * arm64: dts: rockchip: fix RockPro64 sdhci settings
  * pinctrl: ns2: Fix off by one bugs in ns2_pinmux_enable()
  * pinctrl: stmfx: fix null pointer on remove
  * arm64: dts: zii-ultra: fix ARM regulator states
  * ARM: dts: am3874-iceboard: Fix 'i2c-mux-idle-disconnect' usage
  * ASoC: msm8916-wcd-digital: add missing MIX2 path for RX1/2
  * ASoC: simple_card_utils.h: Fix potential multiple redefinition error
  * ARM: dts: Use level interrupt for omap4 & 5 wlcore
  * ARM: mm: fix alignment handler faults under memory pressure
  * scsi: qla2xxx: fix a potential NULL pointer dereference
  * scsi: scsi_dh_alua: handle RTPG sense code correctly during state 
transitions
  * scsi: sni_53c710: fix compilation error
  * scsi: fix kconfig dependency warning related to 53C700_LE_ON_BE
  * ARM: 8908/1: add __always_inline to functions called from __get_user_check()
  * ARM: 8914/1: NOMMU: Fix exc_ret for XIP
  * arm64: dts: rockchip: fix RockPro64 sdmmc settings
  * arm64: dts: rockchip: Fix usb-c on Hugsun X99 TV Box
  * arm64: dts: lx2160a: Correct CPU core idle state name
  * ARM: dts: imx6q-logicpd: Re-Enable SNVS power key
  * ARM: dts: vf610-zii-scu4-aib: Specify 'i2c-mux-idle-disconnect'
  * ARM: dts: imx7s: Correct GPT's ipg clock source
  * arm64: dts: imx8mq: Use correct clock for usdhc's ipg clk
  * arm64: dts: imx8mm: Use correct clock for usdhc's ipg clk
  * perf tools: Fix resource leak of closedir() on the error paths
  * perf c2c: Fix memory leak in build_cl_output()
  * 8250-men-mcb: fix error checking when get_num_ports returns -ENODEV
  * perf kmem: Fix memory leak in compact_gfp_flags()
  * ARM: davinci: dm365: Fix McBSP dma_slave_map entry
  * drm/amdgpu: fix potential VM faults
  * drm/amdgpu: fix error handling in amdgpu_bo_list_create
  * scsi: target: core: Do not overwrite CDB byte 1
  * scsi: hpsa: add missing hunks in reset-patch
  * ASoC: Intel: sof-rt5682: add a check for devm_clk_get
  * ASoC: SOF: control: return true when kcontrol values change
  * tracing: Fix "gfp_t" format for synthetic events
  * ARM: dts: bcm2837-rpi-cm3: Avoid leds-gpio probing issue
  * i2c: aspeed: fix master pending state handling
  * drm/komeda: Don't flush inactive pipes
  * ARM: 8926/1: v7m: remove register save to stack before svc
  * selftests: kvm: vmx_set_nested_state_test: don't check for VMX support twice
  * selftests: kvm: fix sync_regs_test with newer gccs
  * ALSA: hda: Add Tigerlake/Jasperlake PCI ID
  * of: unittest: fix memory leak in unittest_data_add
  * MIPS: bmips: mark 

[Kernel-packages] [Bug 1846016] Re: Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD GEO_TX_POWER_LIMIT

[You-Sheng Yang]

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD
  GEO_TX_POWER_LIMIT

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  In Progress
Status in linux-oem source package in Disco:
  Confirmed
Status in linux-oem-osp1 source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-oem source package in Eoan:
  Confirmed
Status in linux-oem-osp1 source package in Eoan:
  Confirmed

Bug description:
  I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since
  yesterday.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-firmware 1.182
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 30 20:57:08 2019
  Dependencies:

  InstallationDate: Installed on 2019-07-23 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago)

  --
  Also found on Ubuntu-certified HP EliteDesk 800 G3 DM.

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

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

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

[Tomoki Kosugi]

Same problem. I use laptop PC, Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz, GPU 
GeForce GTX 1080 * 2.
DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS".
Linux kernel version is  "Linux anomalydetect 4.15.0-66-generic".

I tried "cpupower" that controls CPU clock frequency.
cf. https://wiki.archlinux.org/index.php/CPU_frequency_scaling

# cpupower frequency-set -u clock_freq

I tried the above with "clock_freq" set to "3GHz". (My CPU default max
frequency is "4.5GHz")

Then, "cpupower" was able to keep CPU temperature lowly without slowing down in 
my application!!
What do you think about this solution?

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  

Re: [Kernel-packages] [Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)

[Sumneet Kaur Bamrah]

Hey Kai,

Long time, hope things are going well!

Ubuntu 18.04.2 LTS has been updated automatically to Ubuntu 18.04.3 LTS
recently. Unfortunately, unable to use Wifi. The error detected is - 'No
Wifi Adapter found'.

Please guide.

Sumneet

On Thu, Jul 18, 2019 at 1:14 PM Sumneet Kaur Bamrah 
wrote:

> Thanks for sharing Kai! It seems fuzzy. Understanding how it taints a
> kernel is challenging.
>
> On Wed, Jul 17, 2019 at 7:50 PM Kai-Heng Feng 
> wrote:
>
>> https://unix.stackexchange.com/questions/208638/linux-kernel-meaning-of-
>> source-tree-in-tree-and-out-of-tree
>> 
>>
>> A quick search Google shows many results.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1831710
>>
>> Title:
>>   Touchpad not working (Lenevo Ideapad 330 series)
>>
>> Status in linux package in Ubuntu:
>>   Confirmed
>>
>> Bug description:
>>   The touch pad has not been used since the purchase of the product.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 18.04
>>   Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1
>>   ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
>>   Uname: Linux 4.18.0-21-generic x86_64
>>   ApportVersion: 2.20.9-0ubuntu7.6
>>   Architecture: amd64
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Wed Jun  5 13:41:22 2019
>>   InstallationDate: Installed on 2019-06-05 (0 days ago)
>>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
>> (20190210)
>>   SourcePackage: linux-signed-hwe
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   ---
>>   ProblemType: Bug
>>   ApportVersion: 2.20.9-0ubuntu7.6
>>   Architecture: amd64
>>   AudioDevicesInUse:
>>USERPID ACCESS COMMAND
>>/dev/snd/controlC1:  athena 1232 F pulseaudio
>>/dev/snd/pcmC1D0p:   athena 1232 F...m pulseaudio
>>/dev/snd/controlC0:  athena 1232 F pulseaudio
>>   CurrentDesktop: ubuntu:GNOME
>>   DistroRelease: Ubuntu 18.04
>>   InstallationDate: Installed on 2019-06-05 (1 days ago)
>>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
>> (20190210)
>>   MachineType: LENOVO 81D2
>>   Package: linux (not installed)
>>   ProcFB: 0 amdgpudrmfb
>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic
>> root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1
>>   ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
>>   RelatedPackageVersions:
>>linux-restricted-modules-4.18.0-21-generic N/A
>>linux-backports-modules-4.18.0-21-generic  N/A
>>linux-firmware 1.173.6
>>   Tags:  bionic
>>   Uname: Linux 4.18.0-21-generic x86_64
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>>   _MarkForUpload: True
>>   dmi.bios.date: 12/10/2018
>>   dmi.bios.vendor: LENOVO
>>   dmi.bios.version: 7VCN46WW
>>   dmi.board.asset.tag: NO Asset Tag
>>   dmi.board.name: LNVNB161216
>>   dmi.board.vendor: LENOVO
>>   dmi.board.version: NO DPK
>>   dmi.chassis.asset.tag: NO Asset Tag
>>   dmi.chassis.type: 10
>>   dmi.chassis.vendor: LENOVO
>>   dmi.chassis.version: Lenovo ideapad 330-15ARR
>>   dmi.modalias:
>> dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:
>>   dmi.product.family: ideapad 330-15ARR
>>   dmi.product.name: 81D2
>>   dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR
>>   dmi.product.version: Lenovo ideapad 330-15ARR
>>   dmi.sys.vendor: LENOVO
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831710/+subscriptions
>>
>
>
> --
> Thanks and Regards,
> Sumneet Kaur Bamrah
>
>

-- 
Thanks and Regards,
Sumneet Kaur Bamrah

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

Title:
  Touchpad not working (Lenevo Ideapad 330 series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad has not been used since the purchase of the product.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  5 13:41:22 2019
  InstallationDate: Installed on 2019-06-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 

[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.

[Russell Neches]

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

I was hoping a firmware update would solve the problem, but now it is
significantly worse. The crashes happen so frequently that the machine
locks up for a minute or two. Even the capslock light on the keyboard
becomes unresponsive. This usually happens just after boot or coming out
of suspend, but not always.

$ uname -a
Linux evenedric 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

$ fwupdmgr get-devices 
20FBCTO1WW System Firmware
  DeviceId: [redacted]
  Guid: [redacted]
  Plugin:   uefi
  Flags:
internal|updatable|require-ac|supported|registered|needs-reboot
  Version:  0.1.42
  VersionLowest:0.1.31
  VersionFormat:triplet
  Icon: computer
  Created:  2019-11-12

UEFI Device Firmware
  DeviceId: [redacted]
  Guid: [redacted]
  Plugin:   uefi
  Flags:
internal|updatable|require-ac|supported|registered|needs-reboot
  Version:  184.65.3590
  VersionLowest:0.0.1
  VersionFormat:triplet
  Icon: audio-card
  Created:  2019-11-12

UEFI Device Firmware
  DeviceId: [redacted]
  Guid: [redacted]
  Plugin:   uefi
  Flags:
internal|updatable|require-ac|supported|registered|needs-reboot
  Version:  0.1.12
  VersionLowest:0.0.1
  VersionFormat:triplet
  Icon: audio-card
  Created:  2019-11-12
  UpdateState:  success

$ iw reg get
global
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)

phy#0 (self-managed)
country 00: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, 
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, 
NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5290 - 5310 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5310 - 5330 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5490 - 5510 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5510 - 5530 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5530 - 5550 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5550 - 5570 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5570 - 5590 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5590 - 5610 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5610 - 5630 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5630 - 5650 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5650 - 5670 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5670 - 5690 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5690 - 5710 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5710 - 5730 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5735 - 5755 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5755 - 5775 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5775 - 5795 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5795 - 5815 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5815 - 5835 @ 20), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, PASSIVE-SCAN



[  439.402427] [ cut here ]
[  

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

[Ubuntu Kernel Bot]

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

apport-collect 1851149

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

Title:
  I just installed ubuntu 18.04 lts and don't install grub

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just installed ubuntu 18.04 lts and don't install grub

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.14.12
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  3 18:31:33 2019
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
  ProcEnviron:
   LANGUAGE=it_IT.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: grub-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1851149] Re: I just installed ubuntu 18.04 lts and don't install grub

[Sebastien Bacher]

The log suggests the kernel hints to a firmware bug. What sort of
machine is that? Did you check if there is maybe some bios update
available?

Nov  3 17:30:23 ubuntu kernel: [ 1133.860243] [ cut here 
]
Nov  3 17:30:23 ubuntu kernel: [ 1133.860247] [Firmware Bug]: Page fault caused 
by firmware at PA: 0x66d491d0
Nov  3 17:30:23 ubuntu kernel: [ 1133.860260] WARNING: CPU: 1 PID: 246 at 
/build/linux-hwe-zHO4ZF/linux-hwe-5.0.0/arch/x86/platform/efi/quirks.c:735 

** Package changed: grub-installer (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/1851149

Title:
  I just installed ubuntu 18.04 lts and don't install grub

Status in linux package in Ubuntu:
  New

Bug description:
  I just installed ubuntu 18.04 lts and don't install grub

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.14.12
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  3 18:31:33 2019
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
  ProcEnviron:
   LANGUAGE=it_IT.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: grub-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1851149] [NEW] I just installed ubuntu 18.04 lts and don't install grub

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I just installed ubuntu 18.04 lts and don't install grub

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  3 18:31:33 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 LANGUAGE=it_IT.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu
-- 
I just installed ubuntu 18.04 lts and don't install grub
https://bugs.launchpad.net/bugs/1851149
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 1848831] Re: Intel WiFi AX200 firmware loading error resulting in no wifi

[Launchpad Bug Tracker]

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

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

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

Title:
  Intel WiFi AX200 firmware loading error resulting in no wifi

Status in Gaming Edition:
  Unknown
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC

  uname -a
  Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  The card is detected OK as dmesg shows, however the card's firmware
  fails immediately after loading (see dmesg output below) and wifi
  doesn't work at all. Big disappointment since the AX200 chip was
  supposed to be supported on 19.10.

  Ubuntu includes two ax200 firmware versions, version 48 loads by
  default in my system (and fails). I tried version 46 (by renaming the
  version 48 file) and it failed in the exact same manner

  $ ls /lib/firmware/iwlwifi-cc-*
  /lib/firmware/iwlwifi-cc-a0-46.ucode  /lib/firmware/iwlwifi-cc-a0-48.ucode

  
  The card's Bluetooth functionality is also detected and it works fine. It's 
just the wifi FW loading what seems broken in ubuntu's 5.3 kernel.

  $ rfkill list
  0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no



  ~$ dmesg | grep iwl
  [   12.312443] iwlwifi :01:00.0: enabling device ( -> 0002)
  [   12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
  [   12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM
  [   12.321102] iwlwifi :01:00.0: Found debug configuration: 0
  [   12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
  [   12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, 
REV=0x340
  [   12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM
  [   12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware 
monitor.
  [   13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired.
  [   13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414910] iwlwifi :01:00.0: Status: 0x, count: 6
  [   13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0
  [   13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [   13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0
  [   13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1
  [   13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2
  [   13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1
  [   13.414917] iwlwifi :01:00.0: 0x1000 | data2
  [   13.414917] iwlwifi :01:00.0: 0xF000 | data3
  [   13.414918] iwlwifi :01:00.0: 0x | beacon time
  [   13.414919] iwlwifi :01:00.0: 0x795F | tsf low
  [   13.414919] iwlwifi :01:00.0: 0x | tsf hi
  [   13.414920] iwlwifi :01:00.0: 0x | time gp1
  [   13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2
  [   13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type
  [   13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major
  [   13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor
  [   13.414923] iwlwifi :01:00.0: 0x0340 | hw version
  [   13.414924] iwlwifi :01:00.0: 0x18C89000 | board version
  [   13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd
  [   13.414925] iwlwifi :01:00.0: 0x0002 | isr0
  [   13.414926] iwlwifi :01:00.0: 0x | isr1
  [   13.414926] iwlwifi :01:00.0: 0x08F2 | isr2
  [   13.414927] iwlwifi :01:00.0: 0x00CC | isr3
  [   13.414928] iwlwifi :01:00.0: 0x | isr4
  [   13.414928] iwlwifi :01:00.0: 0x | last cmd Id
  [   13.414929] iwlwifi :01:00.0: 0x004F3DB0 | wait_event
  [   13.414930] iwlwifi :01:00.0: 0x | l2p_control
  [   13.414930] iwlwifi :01:00.0: 0x0020 | l2p_duration
  [   13.414931] iwlwifi :01:00.0: 0x | l2p_mhvalid
  [   13.414932] iwlwifi :01:00.0: 0x | l2p_addr_match
  [   13.414932] iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel
  [   13.414933] iwlwifi :01:00.0: 0x | timestamp
  [   13.414934] iwlwifi :01:00.0: 0xF81C | flow_handler
  [   13.414974] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414975] iwlwifi :01:00.0: Status: 0x, count: 7
  [   13.414976] iwlwifi :01:00.0: 0x201000A3 | ADVANCED_SYSASSERT
  [   13.414976] iwlwifi :01:00.0: 0x | umac branchlink1
  [   13.414977] iwlwifi :01:00.0: 0xC008CC3C | umac branchlink2
  [   13.414978] iwlwifi :01:00.0: 0xC0087660 | 

[Kernel-packages] [Bug 1852110] Re: Xenial update: 4.4.200 upstream stable release

[Connor Kuehl]

** Description changed:

  SRU Justification
  
  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:
  
  * kbuild: add -fcf-protection=none when using retpoline flags
  * regulator: ti-abb: Fix timeout in ti_abb_wait_txdone/ti_abb_clear_all_txdone
  * regulator: pfuze100-regulator: Variable "val" in pfuze100_regulator_probe() 
could be uninitialized
  * ASoc: rockchip: i2s: Fix RPM imbalance
  * ARM: dts: logicpd-torpedo-som: Remove twl_keypad
  * ARM: mm: fix alignment handler faults under memory pressure
  * scsi: sni_53c710: fix compilation error
  * scsi: fix kconfig dependency warning related to 53C700_LE_ON_BE
  * perf kmem: Fix memory leak in compact_gfp_flags()
  * scsi: target: core: Do not overwrite CDB byte 1
  * of: unittest: fix memory leak in unittest_data_add
  * MIPS: bmips: mark exception vectors as char arrays
  * cifs: Fix cifsInodeInfo lock_sem deadlock when reconnect occurs
  * dccp: do not leak jiffies on the wire
  * net: fix sk_page_frag() recursion from memory reclaim
  * net: hisilicon: Fix ping latency when deal with high throughput
- * Revert "net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol()"
+ * UBUNTU: SAUCE: Revert "net: Zeroing the structure ethtool_wolinfo in 
ethtool_get_wol()"
  * net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol()
  * net: add READ_ONCE() annotation in __skb_wait_for_more_packets()
  * vxlan: check tun_info options_len properly
  * net/mlx4_core: Dynamically set guaranteed amount of counters per VF
  * inet: stop leaking jiffies on the wire
  * net/flow_dissector: switch to siphash
  * dmaengine: qcom: bam_dma: Fix resource leak
  * ARM: 8051/1: put_user: fix possible data corruption in put_user
  * ARM: 8478/2: arm/arm64: add arm-smccc
  * ARM: 8479/2: add implementation for arm-smccc
  * ARM: 8480/2: arm64: add implementation for arm-smccc
  * ARM: 8481/2: drivers: psci: replace psci firmware calls
  * ARM: uaccess: remove put_user() code duplication
  * ARM: Move system register accessors to asm/cp15.h
  * arm/arm64: KVM: Advertise SMCCC v1.1
  * arm64: KVM: Report SMCCC_ARCH_WORKAROUND_1 BP hardening support
  * firmware/psci: Expose PSCI conduit
  * firmware/psci: Expose SMCCC version through psci_ops
  * arm/arm64: smccc: Make function identifiers an unsigned quantity
  * arm/arm64: smccc: Implement SMCCC v1.1 inline primitive
  * arm/arm64: smccc: Add SMCCC-specific return codes
  * arm/arm64: smccc-1.1: Make return values unsigned long
  * arm/arm64: smccc-1.1: Handle function result as parameters
  * ARM: add more CPU part numbers for Cortex and Brahma B15 CPUs
  * ARM: bugs: prepare processor bug infrastructure
  * ARM: bugs: hook processor bug checking into SMP and suspend paths
  * ARM: bugs: add support for per-processor bug checking
  * ARM: spectre: add Kconfig symbol for CPUs vulnerable to Spectre
  * ARM: spectre-v2: harden branch predictor on context switches
  * ARM: spectre-v2: add Cortex A8 and A15 validation of the IBE bit
  * ARM: spectre-v2: harden user aborts in kernel space
  * ARM: spectre-v2: add firmware based hardening
  * ARM: spectre-v2: warn about incorrect context switching functions
  * ARM: spectre-v1: add speculation barrier (csdb) macros
  * ARM: spectre-v1: add array_index_mask_nospec() implementation
  * ARM: spectre-v1: fix syscall entry
  * ARM: signal: copy registers using __copy_from_user()
  * ARM: vfp: use __copy_from_user() when restoring VFP state
  * ARM: oabi-compat: copy semops using __copy_from_user()
  * ARM: use __inttype() in get_user()
  * ARM: spectre-v1: use get_user() for __get_user()
  * ARM: spectre-v1: mitigate user accesses
  * ARM: 8789/1: signal: copy registers using __copy_to_user()
  * ARM: 8791/1: vfp: use __copy_to_user() when saving VFP state
  * ARM: 8792/1: oabi-compat: copy oabi events using __copy_to_user()
  * ARM: 8793/1: signal: replace __put_user_error with __put_user
  * ARM: 8794/1: uaccess: Prevent speculative use of the current addr_limit
  * ARM: 8795/1: spectre-v1.1: use put_user() for __put_user()
  * ARM: 8796/1: spectre-v1,v1.1: provide helpers for address sanitization
  * ARM: 8810/1: vfp: Fix wrong assignement to ufp_exc
  * ARM: make lookup_processor_type() non-__init
  * ARM: split out processor lookup
  * ARM: clean up per-processor check_bugs method call
  * ARM: add PROC_VTABLE and PROC_TABLE macros
  * ARM: spectre-v2: per-CPU vtables to work around big.Little systems
  * ARM: ensure that processor vtables is not lost after boot
  * ARM: fix the cockup in the previous patch
  * alarmtimer: Change remaining ENOTSUPP to EOPNOTSUPP
  * fs/dcache: move 

Re: [Kernel-packages] [Bug 1852005] Re: IR connection off

[Adib ALAOUI]

Bonjour Sébastien,


Au vu du patronyme nous continuerons en français.


Merci pour votre aide.

En fait j'ai résolu depuis mon appel le problème: en repérant dans les
forums l'application Solaar qui prend en charge les périphériques
Logitech.

Après installation du paquet, mon clavier K400 est de nouveau reconnu
(heureusement j'avais gardé un vieux clavier filaire usb ainsi qu'une
souris usb)

Bien à vous.




Adib ALAOUI
Courriel : adib.ala...@netcourrier.com

Fixes +33(0)9 50 03 21 60 / +33(0)5 56 03 21 60
Mob. +33(0)7 81 76 58 34



De : Sebastien Bacher 
À : adib.ala...@netcourrier.com
Sujet : [Bug 1852005] Re: IR connection off
Date : 11/11/2019 21:13:06 Europe/Paris

Thank you for your bug report. Could you give details on the hardware
you are using? Is there any OS handling of the communication between the
dongle and the keyboard? It looks like it could rather be an hardware
issue... (did you check the keyboard batteries?)

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

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

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1852005

Title:
IR connection off

Status in linux package in Ubuntu:
Incomplete

Bug description:
IR connection between keyboard and IR usb dongle don't work after
update from 19.04 to 19.10 version.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sun Nov 10 17:45:17 2019
DistUpgraded: 2019-11-09 21:16:11,874 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. 2nd Generation Core Processor Family 
Integrated Graphics Controller [19da:a166]
InstallationDate: Installed on 2017-07-09 (854 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: MotherBoard By ZOTAC MotherBoard H67ITX-C-E
ProcEnviron:
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=13b961a4-dd4b-4d07-b797-e439cb398142 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-11-09 (0 days ago)
dmi.bios.date: 04/13/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A166P033
dmi.board.asset.tag: NA
dmi.board.name: H67ITX-C-E
dmi.board.vendor: ZOTAC
dmi.board.version: 05
dmi.chassis.asset.tag: NA
dmi.chassis.type: 3
dmi.chassis.vendor: NA
dmi.chassis.version: NA
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA166P033:bd04/13/2012:svnMotherBoardByZOTAC:pnMotherBoardH67ITX-C-E:pvrMotherBoard05:rvnZOTAC:rnH67ITX-C-E:rvr05:cvnNA:ct3:cvrNA:
dmi.product.family: NA
dmi.product.name: MotherBoard H67ITX-C-E
dmi.product.sku: NA
dmi.product.version: MotherBoard 05
dmi.sys.vendor: MotherBoard By ZOTAC
version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Mon Sep 24 00:15:10 2018
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: modeset

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

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

Title:
  IR connection off

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  IR connection between keyboard and IR usb dongle don't work after
  update from 19.04 to 19.10 version.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 

[Kernel-packages] [Bug 1851715] Re: Screen brightness adjustment delay

[Sebastien Bacher]

** Package changed: xorg (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/1851715

Title:
  Screen brightness adjustment delay

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Every time I adjust my laptop's screen brightness using the dedicated
  brightness keys, there is a substantial delay between when I press the
  button and the screen adjusts. Sometimes it even "twitches" and
  decreasing the brightness by tapping the button two times will quickly
  drop the brightness all the way to the lowest setting after the delay
  takes place. I've noticed the issue in the default Ubuntu session and
  in my current vanilla gnome-session. It also doesn't matter which
  extensions I have installed. The keys work flawlessly in Windows so it
  isn't a hardware issue. I have been meaning to report this for a while
  and have just never gotten around to it until just now.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Nov  7 14:37:43 2019
  DistUpgraded: 2019-10-21 20:16:37,104 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
 Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX150] [19e5:3e04]
  InstallationDate: Installed on 2019-09-08 (59 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HD Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HUAWEI MACH-WX9
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=75fe2138-1abd-47b2-a73f-83280ff782ff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (16 days ago)
  dmi.bios.date: 03/15/2019
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.28
  dmi.board.name: MACH-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M14
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9-PCB:rvrM14:cvnHUAWEI:ct10:cvrM14:
  dmi.product.family: MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C128
  dmi.product.version: M14
  dmi.sys.vendor: HUAWEI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Screen brightness adjustment delay

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Every time I adjust my laptop's screen brightness using the dedicated
  brightness keys, there is a substantial delay between when I press the
  button and the screen adjusts. Sometimes it even "twitches" and
  decreasing the brightness by tapping the button two times will quickly
  drop the brightness all the way to the lowest setting after the delay
  takes place. I've noticed the issue in the default Ubuntu session and
  in my current vanilla gnome-session. It also doesn't matter which
  extensions I have installed. The keys work flawlessly in Windows so it
  isn't a hardware issue. I have been meaning to report this for a while
  and have just never gotten around to it until just now.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Nov  7 14:37:43 2019
  DistUpgraded: 2019-10-21 20:16:37,104 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
 Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX150] [19e5:3e04]
  InstallationDate: Installed on 2019-09-08 (59 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HD Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HUAWEI MACH-WX9
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=75fe2138-1abd-47b2-a73f-83280ff782ff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (16 days ago)
  dmi.bios.date: 03/15/2019
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.28
  dmi.board.name: MACH-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M14
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9-PCB:rvrM14:cvnHUAWEI:ct10:cvrM14:
  dmi.product.family: MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C128
  dmi.product.version: M14
  dmi.sys.vendor: HUAWEI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1852111] Re: Eoan update: 5.3.10 upstream stable release

[Connor Kuehl]

This patch was replaced with the version from the upstream Linux stable
branch:

- net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol()

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ * regulator: of: fix suspend-min/max-voltage parsing
+ * ASoC: samsung: arndale: Add missing OF node dereferencing
+ * ASoC: wm8994: Do not register inapplicable controls for WM1811
+ * regulator: da9062: fix suspend_enable/disable preparation
+ * ASoC: topology: Fix a signedness bug in soc_tplg_dapm_widget_create()
+ * arm64: dts: allwinner: a64: pine64-plus: Add PHY regulator delay
+ * arm64: dts: allwinner: a64: Drop PMU node
+ * arm64: dts: allwinner: a64: sopine-baseboard: Add PHY regulator delay
+ * arm64: dts: Fix gpio to pinmux mapping
+ * regulator: ti-abb: Fix timeout in ti_abb_wait_txdone/ti_abb_clear_all_txdone
+ * pinctrl: intel: Allocate IRQ chip dynamic
+ * ASoC: SOF: loader: fix kernel oops on firmware boot failure
+ * ASoC: SOF: topology: fix parse fail issue for byte/bool tuple types
+ * ASoC: SOF: Intel: hda: fix warnings during FW load
+ * ASoC: SOF: Intel: initialise and verify FW crash dump data.
+ * ASoC: SOF: Intel: hda: Disable DMI L1 entry during capture
+ * ASoC: rt5682: add NULL handler to set_jack function
+ * ASoC: intel: sof_rt5682: add remove function to disable jack
+ * ASoC: intel: bytcr_rt5651: add null check to support_button_press
+ * regulator: pfuze100-regulator: Variable "val" in pfuze100_regulator_probe() 
could be uninitialized
+ * ASoC: wm_adsp: Don't generate kcontrols without READ flags
+ * ASoc: rockchip: i2s: Fix RPM imbalance
+ * arm64: dts: rockchip: fix Rockpro64 RK808 interrupt line
+ * ARM: dts: logicpd-torpedo-som: Remove twl_keypad
+ * arm64: dts: rockchip: fix RockPro64 vdd-log regulator settings
+ * arm64: dts: rockchip: fix RockPro64 sdhci settings
+ * pinctrl: ns2: Fix off by one bugs in ns2_pinmux_enable()
+ * pinctrl: stmfx: fix null pointer on remove
+ * arm64: dts: zii-ultra: fix ARM regulator states
+ * ARM: dts: am3874-iceboard: Fix 'i2c-mux-idle-disconnect' usage
+ * ASoC: msm8916-wcd-digital: add missing MIX2 path for RX1/2
+ * ASoC: simple_card_utils.h: Fix potential multiple redefinition error
+ * ARM: dts: Use level interrupt for omap4 & 5 wlcore
+ * ARM: mm: fix alignment handler faults under memory pressure
+ * scsi: qla2xxx: fix a potential NULL pointer dereference
+ * scsi: scsi_dh_alua: handle RTPG sense code correctly during state 
transitions
+ * scsi: sni_53c710: fix compilation error
+ * scsi: fix kconfig dependency warning related to 53C700_LE_ON_BE
+ * ARM: 8908/1: add __always_inline to functions called from __get_user_check()
+ * ARM: 8914/1: NOMMU: Fix exc_ret for XIP
+ * arm64: dts: rockchip: fix RockPro64 sdmmc settings
+ * arm64: dts: rockchip: Fix usb-c on Hugsun X99 TV Box
+ * arm64: dts: lx2160a: Correct CPU core idle state name
+ * ARM: dts: imx6q-logicpd: Re-Enable SNVS power key
+ * ARM: dts: vf610-zii-scu4-aib: Specify 'i2c-mux-idle-disconnect'
+ * ARM: dts: imx7s: Correct GPT's ipg clock source
+ * arm64: dts: imx8mq: Use correct clock for usdhc's ipg clk
+ * arm64: dts: imx8mm: Use correct clock for usdhc's ipg clk
+ * perf tools: Fix resource leak of closedir() on the error paths
+ * perf c2c: Fix memory leak in build_cl_output()
+ * 8250-men-mcb: fix error checking when get_num_ports returns -ENODEV
+ * perf kmem: Fix memory leak in compact_gfp_flags()
+ * ARM: davinci: dm365: Fix McBSP dma_slave_map entry
+ * drm/amdgpu: fix potential VM faults
+ * drm/amdgpu: fix error handling in amdgpu_bo_list_create
+ * scsi: target: core: Do not overwrite CDB byte 1
+ * scsi: hpsa: add missing hunks in reset-patch
+ * ASoC: Intel: sof-rt5682: add a check for devm_clk_get
+ * ASoC: SOF: control: return true when kcontrol values change
+ * tracing: Fix "gfp_t" format for synthetic events
+ * ARM: dts: bcm2837-rpi-cm3: Avoid leds-gpio probing issue
+ * i2c: aspeed: fix master pending state handling
+ * drm/komeda: Don't flush inactive pipes
+ * ARM: 8926/1: v7m: remove register save to stack before svc
+ * selftests: kvm: 

[Kernel-packages] [Bug 1828597] Re: KDump boot fails with nr_cpus=1

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  KDump boot fails with nr_cpus=1

Status in The Ubuntu-power-systems project:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released
Status in kexec-tools source package in Cosmic:
  Invalid
Status in kexec-tools source package in Disco:
  Invalid
Status in linux source package in Disco:
  Invalid
Status in makedumpfile source package in Disco:
  Fix Released
Status in kexec-tools source package in Eoan:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The kdump kernel will crash during its boot if booted on a CPU other than 0.

  [Test case]
  Trigger a crash using taskset -c X, where X is not 0 and is a present CPU. 
Check that the dump is successful.

  echo c | sudo taskset -c 1 tee /proc/sysrq-trigger

  [Regression potential]
  This will cause more memory to be used by the dump kernel, which may cause 
OOMs during the dump. The fix is restricted to ppc64el.

  == Comment: #0 - Hari Krishna Bathini  - 2019-05-10 06:38:21 ==

  ---Problem Description---
  kdump boots fails in some environments when nr_cpus=1 is passed

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. configure kdump
  2. trigger crash on non-boot cpu

  Expected result:
  Capture dump and reboot

  Actual result:
  Hang in early kdump boot process after crash

  Userspace tool common name: kdump-tools

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 ==
  Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though
  this change never made it upstream as maintainer has a few apprehensions..

  With 4.18 kernels, this change is dropped on Ubuntu kernels too.
  With nr_cpus=1 support in kernel, kdump-tools was also updated to
  use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad
  bug 1568952). This kdump-tools change has to be reverted to make
  it consist with the kernel change. Note that "nr_cpus=1 change had
  a issues in kdump guest environment even with "nr_cpus=1" support
  for kdump in kernel. So, even not withstanding the kernel revert, it is
  better to default to "maxcpus=1" on all kernel versions. So, please
  revert the kdump-tools fix that went in with launchpad bug 1568952

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

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

[Kernel-packages] [Bug 1852110] Re: Xenial update: 4.4.200 upstream stable release

[Connor Kuehl]

This patch was replaced with the version from the upstream Linux stable
branch:

- net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol()

This patch required backporting:

- ARM: 8480/2: arm64: add implementation for arm-smccc
  - I had to manually place the hunk in arch/arm64/Kconfig

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ * kbuild: add -fcf-protection=none when using retpoline flags
+ * regulator: ti-abb: Fix timeout in ti_abb_wait_txdone/ti_abb_clear_all_txdone
+ * regulator: pfuze100-regulator: Variable "val" in pfuze100_regulator_probe() 
could be uninitialized
+ * ASoc: rockchip: i2s: Fix RPM imbalance
+ * ARM: dts: logicpd-torpedo-som: Remove twl_keypad
+ * ARM: mm: fix alignment handler faults under memory pressure
+ * scsi: sni_53c710: fix compilation error
+ * scsi: fix kconfig dependency warning related to 53C700_LE_ON_BE
+ * perf kmem: Fix memory leak in compact_gfp_flags()
+ * scsi: target: core: Do not overwrite CDB byte 1
+ * of: unittest: fix memory leak in unittest_data_add
+ * MIPS: bmips: mark exception vectors as char arrays
+ * cifs: Fix cifsInodeInfo lock_sem deadlock when reconnect occurs
+ * dccp: do not leak jiffies on the wire
+ * net: fix sk_page_frag() recursion from memory reclaim
+ * net: hisilicon: Fix ping latency when deal with high throughput
+ * Revert "net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol()"
+ * net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol()
+ * net: add READ_ONCE() annotation in __skb_wait_for_more_packets()
+ * vxlan: check tun_info options_len properly
+ * net/mlx4_core: Dynamically set guaranteed amount of counters per VF
+ * inet: stop leaking jiffies on the wire
+ * net/flow_dissector: switch to siphash
+ * dmaengine: qcom: bam_dma: Fix resource leak
+ * ARM: 8051/1: put_user: fix possible data corruption in put_user
+ * ARM: 8478/2: arm/arm64: add arm-smccc
+ * ARM: 8479/2: add implementation for arm-smccc
+ * ARM: 8480/2: arm64: add implementation for arm-smccc
+ * ARM: 8481/2: drivers: psci: replace psci firmware calls
+ * ARM: uaccess: remove put_user() code duplication
+ * ARM: Move system register accessors to asm/cp15.h
+ * arm/arm64: KVM: Advertise SMCCC v1.1
+ * arm64: KVM: Report SMCCC_ARCH_WORKAROUND_1 BP hardening support
+ * firmware/psci: Expose PSCI conduit
+ * firmware/psci: Expose SMCCC version through psci_ops
+ * arm/arm64: smccc: Make function identifiers an unsigned quantity
+ * arm/arm64: smccc: Implement SMCCC v1.1 inline primitive
+ * arm/arm64: smccc: Add SMCCC-specific return codes
+ * arm/arm64: smccc-1.1: Make return values unsigned long
+ * arm/arm64: smccc-1.1: Handle function result as parameters
+ * ARM: add more CPU part numbers for Cortex and Brahma B15 CPUs
+ * ARM: bugs: prepare processor bug infrastructure
+ * ARM: bugs: hook processor bug checking into SMP and suspend paths
+ * ARM: bugs: add support for per-processor bug checking
+ * ARM: spectre: add Kconfig symbol for CPUs vulnerable to Spectre
+ * ARM: spectre-v2: harden branch predictor on context switches
+ * ARM: spectre-v2: add Cortex A8 and A15 validation of the IBE bit
+ * ARM: spectre-v2: harden user aborts in kernel space
+ * ARM: spectre-v2: add firmware based hardening
+ * ARM: spectre-v2: warn about incorrect context switching functions
+ * ARM: spectre-v1: add speculation barrier (csdb) macros
+ * ARM: spectre-v1: add array_index_mask_nospec() implementation
+ * ARM: spectre-v1: fix syscall entry
+ * ARM: signal: copy registers using __copy_from_user()
+ * ARM: vfp: use __copy_from_user() when restoring VFP state
+ * ARM: oabi-compat: copy semops using __copy_from_user()
+ * ARM: use __inttype() in get_user()
+ * ARM: spectre-v1: use get_user() for __get_user()
+ * ARM: spectre-v1: mitigate user accesses
+ * ARM: 8789/1: signal: copy registers using __copy_to_user()
+ * ARM: 8791/1: vfp: use __copy_to_user() when saving VFP state
+ * ARM: 8792/1: oabi-compat: copy oabi events using __copy_to_user()
+ * ARM: 8793/1: signal: replace __put_user_error with __put_user
+ * ARM: 8794/1: uaccess: Prevent speculative 

[Kernel-packages] [Bug 1851715] [NEW] Screen brightness adjustment delay

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Every time I adjust my laptop's screen brightness using the dedicated
brightness keys, there is a substantial delay between when I press the
button and the screen adjusts. Sometimes it even "twitches" and
decreasing the brightness by tapping the button two times will quickly
drop the brightness all the way to the lowest setting after the delay
takes place. I've noticed the issue in the default Ubuntu session and in
my current vanilla gnome-session. It also doesn't matter which
extensions I have installed. The keys work flawlessly in Windows so it
isn't a hardware issue. I have been meaning to report this for a while
and have just never gotten around to it until just now.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Thu Nov  7 14:37:43 2019
DistUpgraded: 2019-10-21 20:16:37,104 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
   Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX150] [19e5:3e04]
InstallationDate: Installed on 2019-09-08 (59 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HD Camera
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HUAWEI MACH-WX9
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=75fe2138-1abd-47b2-a73f-83280ff782ff ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-10-22 (16 days ago)
dmi.bios.date: 03/15/2019
dmi.bios.vendor: HUAWEI
dmi.bios.version: 1.28
dmi.board.name: MACH-WX9-PCB
dmi.board.vendor: HUAWEI
dmi.board.version: M14
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M14
dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9-PCB:rvrM14:cvnHUAWEI:ct10:cvrM14:
dmi.product.family: MateBook X
dmi.product.name: MACH-WX9
dmi.product.sku: C128
dmi.product.version: M14
dmi.sys.vendor: HUAWEI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan ubuntu
-- 
Screen brightness adjustment delay 
https://bugs.launchpad.net/bugs/1851715
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 1852047] Re: [Bionic][Regression] Disabling EPT results in KVM guests that won't start

[Thadeu Lima de Souza Cascardo]

Notice that I tested the fixed kernel also containig the fix for LP:
#1849576 and kvm-unit-tests did not regress nor caused any kernel oops.
Also, the guest linux kernel launched just fine.

** Description changed:

+ [Impact]
+ On CPUs with no EPT support, or when disabling kvm-intel ept support by use 
of ept=0 module parameter, users are not able to launch a linux VM.
+ 
+ [Test case]
+ # modprobe kvm-intel ept=0
+ # cat /sys/module/kvm_intel/parameters/ept
+ N
+ # qemu-system-x86_64 -enable-kvm -kernel /boot/vmlinuz-4.15.0-68-generic
+ 
+ Make sure you get console log at all. With the bug, there is not a
+ single line of output.
+ 
+ [Regression potential]
+ The fix might cause some very specific use of virtualization to fail, but no 
pratical case is known.
+ 
+ 
+ ===
+ 
  Starting with 4.15.0-68.77, currently in bionic-proposed, I can no
  longer launch VMs when I disable EPT support in the kvm_intel module.
  This works fine under 4.15.0-66.75 from bionic-security.
  
-  ubuntu@vought:~$ cat /proc/version_signature
-  Ubuntu 4.15.0-68.77-generic 4.15.18
-  ubuntu@vought:~$ sudo rmmod kvm_intel
-  ubuntu@vought:~$ sudo modprobe kvm_intel ept=0
-  ubuntu@vought:~$ cat /sys/module/kvm_intel/parameters/ept
-  N
-  ubuntu@vought:~$ virsh start --console l1
-  Domain l1 started
-  Connected to domain l1
-  Escape character is ^]
+  ubuntu@vought:~$ cat /proc/version_signature
+  Ubuntu 4.15.0-68.77-generic 4.15.18
+  ubuntu@vought:~$ sudo rmmod kvm_intel
+  ubuntu@vought:~$ sudo modprobe kvm_intel ept=0
+  ubuntu@vought:~$ cat /sys/module/kvm_intel/parameters/ept
+  N
+  ubuntu@vought:~$ virsh start --console l1
+  Domain l1 started
+  Connected to domain l1
+  Escape character is ^]
  
  Under 4.15.0-66.75, I see full console output from the guest and reach a
  login prompt. Under 4.15.0-68.77, I see no output and the VM is
  unresponsive. I see nothing of use in /var/log/libvirt/qemu/l1.log.
  
  I see this on the following system:
  
  ubuntu@vought:~$ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  96
  On-line CPU(s) list: 0-95
  Thread(s) per core:  2
  Core(s) per socket:  24
  Socket(s):   2
  NUMA node(s):2
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   85
  Model name:  Intel(R) Xeon(R) Gold 6252 CPU @ 2.10GHz
  Stepping:6
  CPU MHz: 1000.135
  CPU max MHz: 3700.
  CPU min MHz: 1000.
  BogoMIPS:4200.00
  Virtualization:  VT-x
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:1024K
  L3 cache:36608K
  NUMA node0 CPU(s):   0-23,48-71
  NUMA node1 CPU(s):   24-47,72-95
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl 
xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb cat_l3 cdp_l3 invpcid_single ssbd mba ibrs ibpb stibp 
ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 
hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx 
smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec 
xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida 
arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req pku ospke avx512_vnni 
md_clear flush_l1d arch_capabilities

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

Title:
  [Bionic][Regression] Disabling EPT results in KVM guests that won't
  start

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

Bug description:
  [Impact]
  On CPUs with no EPT support, or when disabling kvm-intel ept support by use 
of ept=0 module parameter, users are not able to launch a linux VM.

  [Test case]
  # modprobe kvm-intel ept=0
  # cat /sys/module/kvm_intel/parameters/ept
  N
  # qemu-system-x86_64 -enable-kvm -kernel /boot/vmlinuz-4.15.0-68-generic

  Make sure you get console log at all. With the bug, there is not a
  single line of output.

  [Regression potential]
  The fix might cause some very specific use of virtualization to fail, but no 
pratical case is known.

  
  ===

  Starting with 4.15.0-68.77, currently in bionic-proposed, I can no
  longer launch VMs when I disable EPT support in the kvm_intel module.
  This works fine under 4.15.0-66.75 from bionic-security.

   ubuntu@vought:~$ cat /proc/version_signature
   Ubuntu 4.15.0-68.77-generic 4.15.18

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Unable to adjust brightness of backlight

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to adjust the brightness of the backlight of my laptop
  screen either by using the slider of by changing the value in
  /sys/class/backlight/intel_backlight/brightness directly.

  I have tried changing my GRUB configuration:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
  But that did not help.

  I am using Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 14:03:33 2019
  DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-19-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1]
   NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] 
[1558:65d1]
  InstallationDate: Installed on 2019-10-09 (30 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Notebook PB50_70RF,RD,RC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago)
  dmi.bios.date: 02/01/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: PB50_70RF,RD,RC
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: PB50_70RF,RD,RC
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1851833] Re: Unable to adjust brightness of backlight

[Sebastien Bacher]

** Package changed: xorg (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/1851833

Title:
  Unable to adjust brightness of backlight

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to adjust the brightness of the backlight of my laptop
  screen either by using the slider of by changing the value in
  /sys/class/backlight/intel_backlight/brightness directly.

  I have tried changing my GRUB configuration:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
  But that did not help.

  I am using Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 14:03:33 2019
  DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-19-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1]
   NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] 
[1558:65d1]
  InstallationDate: Installed on 2019-10-09 (30 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Notebook PB50_70RF,RD,RC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago)
  dmi.bios.date: 02/01/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: PB50_70RF,RD,RC
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: PB50_70RF,RD,RC
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1851833] [NEW] Unable to adjust brightness of backlight

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I am unable to adjust the brightness of the backlight of my laptop
screen either by using the slider of by changing the value in
/sys/class/backlight/intel_backlight/brightness directly.

I have tried changing my GRUB configuration:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
But that did not help.

I am using Ubuntu 19.10

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov  8 14:03:33 2019
DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.3.0-19-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1]
 NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] [1558:65d1]
InstallationDate: Installed on 2019-10-09 (30 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Notebook PB50_70RF,RD,RC
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago)
dmi.bios.date: 02/01/2019
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.07
dmi.board.asset.tag: Tag 12345
dmi.board.name: PB50_70RF,RD,RC
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: PB50_70RF,RD,RC
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan ubuntu
-- 
Unable to adjust brightness of backlight
https://bugs.launchpad.net/bugs/1851833
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 1851956] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Initialization too slow, about 2 minutes. After is normal.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When init the grub boot, stop and wait for 2 minutes, circa...
  After this time, normal speed and OS load normally, no problem !!! Ubuntu 
Studio 18.04 LTS. Sony Vaio VPCEE45B. 
  Ubuntu Studio 20.04 (Daily) work fine, without wait 
  Thanks
  

  (My english is bad,,,sorry)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75-lowlatency 4.15.18
  Uname: Linux 4.15.0-66-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov  9 16:26:42 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation RS880M [Mobility Radeon HD 4225/4250] 
[104d:9077]
  InstallationDate: Installed on 2019-11-08 (1 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Sony Corporation VPCEE45FB
  ProcEnviron:
   LANGUAGE=pt_BR
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-lowlatency 
root=/dev/mapper/ubuntu--studio--vg-root ro locale=pt_BR quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2010
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0200Z5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0200Z5:bd12/09/2010:svnSonyCorporation:pnVPCEE45FB:pvrC8002NHR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEE45FB
  dmi.product.version: C8002NHR
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Nov  9 15:54:20 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.3
  xserver.video_driver: radeon

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

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

[Kernel-packages] [Bug 1851956] Re: Initialization too slow, about 2 minutes. After is normal.

[Sebastien Bacher]

** Package changed: xorg (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/1851956

Title:
  Initialization too slow, about 2 minutes. After is normal.

Status in linux package in Ubuntu:
  New

Bug description:
  When init the grub boot, stop and wait for 2 minutes, circa...
  After this time, normal speed and OS load normally, no problem !!! Ubuntu 
Studio 18.04 LTS. Sony Vaio VPCEE45B. 
  Ubuntu Studio 20.04 (Daily) work fine, without wait 
  Thanks
  

  (My english is bad,,,sorry)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75-lowlatency 4.15.18
  Uname: Linux 4.15.0-66-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov  9 16:26:42 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation RS880M [Mobility Radeon HD 4225/4250] 
[104d:9077]
  InstallationDate: Installed on 2019-11-08 (1 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Sony Corporation VPCEE45FB
  ProcEnviron:
   LANGUAGE=pt_BR
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-lowlatency 
root=/dev/mapper/ubuntu--studio--vg-root ro locale=pt_BR quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2010
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0200Z5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0200Z5:bd12/09/2010:svnSonyCorporation:pnVPCEE45FB:pvrC8002NHR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEE45FB
  dmi.product.version: C8002NHR
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Nov  9 15:54:20 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.3
  xserver.video_driver: radeon

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

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

[Kernel-packages] [Bug 1851956] [NEW] Initialization too slow, about 2 minutes. After is normal.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When init the grub boot, stop and wait for 2 minutes, circa...
After this time, normal speed and OS load normally, no problem !!! Ubuntu 
Studio 18.04 LTS. Sony Vaio VPCEE45B. 
Ubuntu Studio 20.04 (Daily) work fine, without wait 
Thanks


(My english is bad,,,sorry)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-66.75-lowlatency 4.15.18
Uname: Linux 4.15.0-66-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CompositorRunning: None
Date: Sat Nov  9 16:26:42 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation RS880M [Mobility Radeon HD 4225/4250] [104d:9077]
InstallationDate: Installed on 2019-11-08 (1 days ago)
InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
MachineType: Sony Corporation VPCEE45FB
ProcEnviron:
 LANGUAGE=pt_BR
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-lowlatency 
root=/dev/mapper/ubuntu--studio--vg-root ro locale=pt_BR quiet splash 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2010
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0200Z5
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0200Z5:bd12/09/2010:svnSonyCorporation:pnVPCEE45FB:pvrC8002NHR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: VPCEE45FB
dmi.product.version: C8002NHR
dmi.sys.vendor: Sony Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Nov  9 15:54:20 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.3
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug bionic ubuntu
-- 
Initialization too slow, about 2 minutes. After is normal.
https://bugs.launchpad.net/bugs/1851956
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 1852047] Re: [Bionic][Regression] Disabling EPT results in KVM guests that won't start

[Thadeu Lima de Souza Cascardo]

https://lore.kernel.org/stable/2019173757.gb11...@linux.intel.com/

Discussion about why this is causing an issue on LTS/stable kernels, but
not upstream.

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

Title:
  [Bionic][Regression] Disabling EPT results in KVM guests that won't
  start

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

Bug description:
  Starting with 4.15.0-68.77, currently in bionic-proposed, I can no
  longer launch VMs when I disable EPT support in the kvm_intel module.
  This works fine under 4.15.0-66.75 from bionic-security.

   ubuntu@vought:~$ cat /proc/version_signature
   Ubuntu 4.15.0-68.77-generic 4.15.18
   ubuntu@vought:~$ sudo rmmod kvm_intel
   ubuntu@vought:~$ sudo modprobe kvm_intel ept=0
   ubuntu@vought:~$ cat /sys/module/kvm_intel/parameters/ept
   N
   ubuntu@vought:~$ virsh start --console l1
   Domain l1 started
   Connected to domain l1
   Escape character is ^]

  Under 4.15.0-66.75, I see full console output from the guest and reach
  a login prompt. Under 4.15.0-68.77, I see no output and the VM is
  unresponsive. I see nothing of use in /var/log/libvirt/qemu/l1.log.

  I see this on the following system:

  ubuntu@vought:~$ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  96
  On-line CPU(s) list: 0-95
  Thread(s) per core:  2
  Core(s) per socket:  24
  Socket(s):   2
  NUMA node(s):2
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   85
  Model name:  Intel(R) Xeon(R) Gold 6252 CPU @ 2.10GHz
  Stepping:6
  CPU MHz: 1000.135
  CPU max MHz: 3700.
  CPU min MHz: 1000.
  BogoMIPS:4200.00
  Virtualization:  VT-x
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:1024K
  L3 cache:36608K
  NUMA node0 CPU(s):   0-23,48-71
  NUMA node1 CPU(s):   24-47,72-95
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl 
xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb cat_l3 cdp_l3 invpcid_single ssbd mba ibrs ibpb stibp 
ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 
hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx 
smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec 
xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida 
arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req pku ospke avx512_vnni 
md_clear flush_l1d arch_capabilities

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

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

[Kernel-packages] [Bug 1852005] Re: IR connection off

[Sebastien Bacher]

Thank you for your bug report. Could you give details on the hardware
you are using? Is there any OS handling of the communication between the
dongle and the keyboard? It looks like it could rather be an hardware
issue... (did you check the keyboard batteries?)

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

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

Title:
  IR connection off

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  IR connection between keyboard and IR usb dongle don't work after
  update from 19.04 to 19.10 version.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Nov 10 17:45:17 2019
  DistUpgraded: 2019-11-09 21:16:11,874 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. 2nd Generation Core Processor 
Family Integrated Graphics Controller [19da:a166]
  InstallationDate: Installed on 2017-07-09 (854 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: MotherBoard By ZOTAC MotherBoard H67ITX-C-E
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=13b961a4-dd4b-4d07-b797-e439cb398142 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-11-09 (0 days ago)
  dmi.bios.date: 04/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A166P033
  dmi.board.asset.tag: NA
  dmi.board.name: H67ITX-C-E
  dmi.board.vendor: ZOTAC
  dmi.board.version: 05
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA166P033:bd04/13/2012:svnMotherBoardByZOTAC:pnMotherBoardH67ITX-C-E:pvrMotherBoard05:rvnZOTAC:rnH67ITX-C-E:rvr05:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: MotherBoard H67ITX-C-E
  dmi.product.sku: NA
  dmi.product.version: MotherBoard 05
  dmi.sys.vendor: MotherBoard By ZOTAC
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Sep 24 00:15:10 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: modeset

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

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

[Kernel-packages] [Bug 1852005] [NEW] IR connection off

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

IR connection between keyboard and IR usb dongle don't work after update
from 19.04 to 19.10 version.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sun Nov 10 17:45:17 2019
DistUpgraded: 2019-11-09 21:16:11,874 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. 2nd Generation Core Processor 
Family Integrated Graphics Controller [19da:a166]
InstallationDate: Installed on 2017-07-09 (854 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: MotherBoard By ZOTAC MotherBoard H67ITX-C-E
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=13b961a4-dd4b-4d07-b797-e439cb398142 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-11-09 (0 days ago)
dmi.bios.date: 04/13/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A166P033
dmi.board.asset.tag: NA
dmi.board.name: H67ITX-C-E
dmi.board.vendor: ZOTAC
dmi.board.version: 05
dmi.chassis.asset.tag: NA
dmi.chassis.type: 3
dmi.chassis.vendor: NA
dmi.chassis.version: NA
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA166P033:bd04/13/2012:svnMotherBoardByZOTAC:pnMotherBoardH67ITX-C-E:pvrMotherBoard05:rvnZOTAC:rnH67ITX-C-E:rvr05:cvnNA:ct3:cvrNA:
dmi.product.family: NA
dmi.product.name: MotherBoard H67ITX-C-E
dmi.product.sku: NA
dmi.product.version: MotherBoard 05
dmi.sys.vendor: MotherBoard By ZOTAC
version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Mon Sep 24 00:15:10 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug eoan ubuntu
-- 
IR connection off
https://bugs.launchpad.net/bugs/1852005
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 1852119] [NEW] Please add zfs modules to linux-raspi2

[satmandu]

Public bug reported:

The 4gb RPI4 is more than capable of handling zfs.
( Even zfs root can be enabled manually with arm64 eoan builds using a variant 
of the steps at https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS 
. )

Currently one has to install zfs-dkms for zfs support, but ideally one
would have zfs modules come with the standard arm64 kernel so that one
does not have to recompile zfs on the pi.

Example:

uname -a
Linux rpi4 5.3.0-1011-raspi2 #12-Ubuntu SMP Fri Nov 1 09:07:06 UTC 2019 aarch64 
aarch64 aarch64 GNU/Linux
@rpi4:~$ zpool status
  pool: bpool
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(5) for details.
  scan: scrub repaired 0B in 0 days 00:00:00 with 0 errors on Mon Nov 11 
13:50:14 2019
config:

NAME  STATE 
READ WRITE CKSUM
bpool ONLINE   
0 0 0
  usb-Samsung_Flash_Drive_FIT_0309318110004882-0:0-part3  ONLINE   
0 0 0

errors: No known data errors

  pool: rpool
 state: ONLINE
  scan: scrub repaired 0B in 0 days 00:01:21 with 0 errors on Mon Nov 11 
13:51:39 2019
config:

NAMESTATE READ WRITE CKSUM
rpool   ONLINE   0 0 0
  sda4  ONLINE   0 0 0

errors: No known data errors

dkms status
zfs, 0.8.1, 5.3.0-1011-raspi2, aarch64: installed

@rpi4:~$ cat /proc/cpuinfo 
processor   : 0
BogoMIPS: 108.00
Features: fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part: 0xd08
CPU revision: 3

processor   : 1
BogoMIPS: 108.00
Features: fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part: 0xd08
CPU revision: 3

processor   : 2
BogoMIPS: 108.00
Features: fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part: 0xd08
CPU revision: 3

processor   : 3
BogoMIPS: 108.00
Features: fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part: 0xd08
CPU revision: 3

Hardware: BCM2835
Revision: c03111
Serial  : ---
Model   : Raspberry Pi 4 Model B Rev 1.1
@rpi4:~$ free -m
  totalusedfree  shared  buff/cache   available
Mem:   3791 8832612  18 2952836
Swap:  4095   04095

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

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

Title:
  Please add zfs modules to linux-raspi2

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  The 4gb RPI4 is more than capable of handling zfs.
  ( Even zfs root can be enabled manually with arm64 eoan builds using a 
variant of the steps at 
https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS . )

  Currently one has to install zfs-dkms for zfs support, but ideally one
  would have zfs modules come with the standard arm64 kernel so that one
  does not have to recompile zfs on the pi.

  Example:

  uname -a
  Linux rpi4 5.3.0-1011-raspi2 #12-Ubuntu SMP Fri Nov 1 09:07:06 UTC 2019 
aarch64 aarch64 aarch64 GNU/Linux
  @rpi4:~$ zpool status
pool: bpool
   state: ONLINE
  status: Some supported features are not enabled on the pool. The pool can
  still be used, but some features are unavailable.
  action: Enable all features using 'zpool upgrade'. Once this is done,
  the pool may no longer be accessible by software that does not support
  the features. See zpool-features(5) for details.
scan: scrub repaired 0B in 0 days 00:00:00 with 0 errors on Mon Nov 11 
13:50:14 2019
  config:

  NAME  STATE 
READ WRITE CKSUM
  bpool ONLINE  
 0 0 0
usb-Samsung_Flash_Drive_FIT_0309318110004882-0:0-part3  ONLINE  
 0 0 0

  errors: No known data errors

pool: rpool
   state: ONLINE
scan: scrub repaired 0B in 0 days 00:01:21 with 0 errors on Mon Nov 11 
13:51:39 2019
  config:

  NAMESTATE READ WRITE CKSUM
  rpool   ONLINE   0 0 0
sda4  ONLINE   0 0 0

  errors: No known data errors

  dkms status
  zfs, 0.8.1, 5.3.0-1011-raspi2, 

[Kernel-packages] [Bug 1849026] Re: trusty/linux-azure: 4.15.0-1062.67~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849027
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Testing
- phase-changed: Thursday, 24. October 2019 14:57 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:49 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1062.67~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849027
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:49 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849026/+subscriptions

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

[Kernel-packages] [Bug 1849027] Re: xenial/linux-azure: 4.15.0-1062.67 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Testing
- phase-changed: Tuesday, 22. October 2019 15:49 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  trackers:
trusty/linux-azure: bug 1849026
xenial/linux-azure-edge: bug 1849025
xenial/linux-azure/azure-kernel: bug 1849024
  variant: debs

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

Title:
  xenial/linux-azure: 4.15.0-1062.67 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  trackers:
trusty/linux-azure: bug 1849026
xenial/linux-azure-edge: bug 1849025
xenial/linux-azure/azure-kernel: bug 1849024
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849027/+subscriptions

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

[Kernel-packages] [Bug 1849031] Re: xenial/linux-gcp: 4.15.0-1048.51 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Testing
- phase-changed: Wednesday, 23. October 2019 12:41 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1849028
xenial/linux-gcp/gke-kernel: bug 1849029
  variant: debs

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

Title:
  xenial/linux-gcp: 4.15.0-1048.51 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1849028
xenial/linux-gcp/gke-kernel: bug 1849029
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849031/+subscriptions

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

[Kernel-packages] [Bug 1849023] Re: bionic/linux-fips: 4.15.0-1019.22 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Testing
- phase-changed: Thursday, 24. October 2019 20:46 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  variant: debs

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

Title:
  bionic/linux-fips: 4.15.0-1019.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849023/+subscriptions

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

[Kernel-packages] [Bug 1849033] Re: xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849854
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
- phase: Testing
- phase-changed: Tuesday, 29. October 2019 13:46 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:49 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  variant: debs

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

Title:
  xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849854
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:49 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849033/+subscriptions

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

[Kernel-packages] [Bug 1851507] Re: bionic/linux-oem: 4.15.0-1062.71 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Thursday, 07. November 2019 17:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1062.71 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Thursday, 07. November 2019 17:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851507/+subscriptions

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

[Kernel-packages] [Bug 1849014] Re: bionic/linux-aws-fips: 4.15.0-2003.3 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849016
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Testing
- phase-changed: Wednesday, 23. October 2019 11:12 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:43 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  variant: debs

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

Title:
  bionic/linux-aws-fips: 4.15.0-2003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849016
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:43 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849014/+subscriptions

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

[Kernel-packages] [Bug 1849008] Re: bionic/linux-raspi2: 4.15.0-1050.54 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Testing
- phase-changed: Tuesday, 22. October 2019 13:42 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1849007
  variant: debs

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

Title:
  bionic/linux-raspi2: 4.15.0-1050.54 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1849007
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849008/+subscriptions

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

[Kernel-packages] [Bug 1845677] Re: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen

[M]

Thanks @Hui, @Shengyao

Using 5.3.0-21-generic from proposed, the ucm config files (via
ppa:xueshengyao/dmic), and blacklisting snd_hda_intel and snd_soc_skl,
both speaker and HDMI audio out work. (related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848490)

Apologies if this is off topic for this bug report, but after the
installation of oem-dmic-sof-lp1825294, it seems that audio HDMI /
DisplayPort audio sinks (such as those connected to a dock) are no
longer discovered.  I'm not familiar with how everything is in play
here, so if more information is necessary, please just let me know if
gathering more information would be helpful.



** Attachment added: "dmsg-after-oem-dmic-sof-lp1825294lsp.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/+attachment/5304532/+files/dmsg-after-oem-dmic-sof-lp1825294lsp.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/1845677

Title:
  volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1
  Carbon 7th gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo ThinkPad X1 Carbon 7th generation using the built-in
  speakers, the volume is either off or on, there's no gradation in
  volume when I move the slider up or down.

  If I enable Over-Amplification than there's gradation in volume when I
  turn the volume up past 100%, but not for 0-100%.

  This problem does not occur with a headset plugged into the 3.5mm
  jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-12-generic 5.3.0-12.13
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik3746 F pulseaudio
   /dev/snd/pcmC0D0p:   jik3746 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 11:07:44 2019
  InstallationDate: Installed on 2019-09-12 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-12-generic N/A
   linux-backports-modules-5.3.0-12-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1849011] Re: bionic/linux-snapdragon: 4.15.0-1067.74 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Testing
- phase-changed: Wednesday, 23. October 2019 11:51 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1849010
  variant: debs

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

Title:
  bionic/linux-snapdragon: 4.15.0-1067.74 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1849010
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849011/+subscriptions

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

[Kernel-packages] [Bug 1849020] Re: bionic/linux-ibm-gt: 4.15.0-1040.42 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
- phase: Testing
- phase-changed: Thursday, 24. October 2019 12:22 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  variant: debs

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1040.42 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849020/+subscriptions

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

[Kernel-packages] [Bug 1849016] Re: bionic/linux-aws: 4.15.0-1053.55 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
- phase: Testing
- phase-changed: Tuesday, 22. October 2019 13:42 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-aws-fips: bug 1849014
bionic/linux-aws/aws-kernel: bug 1849013
xenial/linux-aws-hwe: bug 1849015
  variant: debs

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

Title:
  bionic/linux-aws: 4.15.0-1053.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-aws-fips: bug 1849014
bionic/linux-aws/aws-kernel: bug 1849013
xenial/linux-aws-hwe: bug 1849015
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849016/+subscriptions

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

[Kernel-packages] [Bug 1849019] Re: bionic/linux-kvm: 4.15.0-1049.49 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Testing
- phase-changed: Tuesday, 22. October 2019 13:43 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  variant: debs

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

Title:
  bionic/linux-kvm: 4.15.0-1049.49 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849019/+subscriptions

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

[Kernel-packages] [Bug 1849021] Re: xenial/linux-oracle: 4.15.0-1028.31~16.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849022
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Testing
- phase-changed: Wednesday, 23. October 2019 09:41 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  variant: debs

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

Title:
  xenial/linux-oracle: 4.15.0-1028.31~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849022
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849021/+subscriptions

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

[Kernel-packages] [Bug 1849022] Re: bionic/linux-oracle: 4.15.0-1028.31 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Testing
- phase-changed: Wednesday, 23. October 2019 09:41 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 18:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  trackers:
xenial/linux-oracle: bug 1849021
  variant: debs

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

Title:
  bionic/linux-oracle: 4.15.0-1028.31 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1849855
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 18:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  trackers:
xenial/linux-oracle: bug 1849021
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849022/+subscriptions

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

[Kernel-packages] [Bug 1852116] [NEW] zfs send / recv properties failing

[Geoff Nordli]

Public bug reported:

Running Ubuntu 19.10 on both the send and recv systems.

I can't send properties. If I don't include the -p switch, all is good.

If I include the -p switch it looks like it is going to work, but it
hangs like this:

sudo /usr/sbin/zfs send -vp -I tank/vm@2019-11-02_22-41-35__daily__batch1 
tank/vm@2019-11-05_18-26-01__daily__batch1 | /bin/ssh back1 sudo /usr/sbin/zfs 
recv -vu backup/vm
send from @2019-11-02_22-41-35__daily__batch1 to 
tank/vm@2019-11-05_18-24-41__daily__batch1 estimated size is 4.12G
send from @2019-11-05_18-24-41__daily__batch1 to 
tank/vm@2019-11-05_18-26-01__daily__batch1 estimated size is 2.50M
total estimated size is 4.13G
TIME SENT SNAPSHOT tank/vm@2019-11-05_18-24-41__daily__batch1
receiving incremental stream of tank/vm@2019-11-05_18-24-41__daily__batch1 into 
backup/vm@2019-11-05_18-24-41__daily__batch1
20:03:24 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
20:03:25 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
20:03:26 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
20:03:27 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
20:03:28 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
20:03:29 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
20:03:30 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1

Then I have to kill it.

Any thoughts?
thanks,
Geoff

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

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

Title:
  zfs send / recv properties failing

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Running Ubuntu 19.10 on both the send and recv systems.

  I can't send properties. If I don't include the -p switch, all is
  good.

  If I include the -p switch it looks like it is going to work, but it
  hangs like this:

  sudo /usr/sbin/zfs send -vp -I tank/vm@2019-11-02_22-41-35__daily__batch1 
tank/vm@2019-11-05_18-26-01__daily__batch1 | /bin/ssh back1 sudo /usr/sbin/zfs 
recv -vu backup/vm
  send from @2019-11-02_22-41-35__daily__batch1 to 
tank/vm@2019-11-05_18-24-41__daily__batch1 estimated size is 4.12G
  send from @2019-11-05_18-24-41__daily__batch1 to 
tank/vm@2019-11-05_18-26-01__daily__batch1 estimated size is 2.50M
  total estimated size is 4.13G
  TIME SENT SNAPSHOT tank/vm@2019-11-05_18-24-41__daily__batch1
  receiving incremental stream of tank/vm@2019-11-05_18-24-41__daily__batch1 
into backup/vm@2019-11-05_18-24-41__daily__batch1
  20:03:24 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:25 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:26 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:27 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:28 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:29 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1
  20:03:30 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1

  Then I have to kill it.

  Any thoughts?
  thanks,
  Geoff

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

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

[Kernel-packages] [Bug 1849720] Re: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)

[Brian Mays]

I switched my networking interface from e1000e to virtio and ran the VM
on kernel 5.3.0-19-generic and had no issues with the VM. Networking
worked for both the host and the VM. When I compared this to a clone of
the machine with the e1000e networking interface, I had the system
freezing issue.

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

Title:
  KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  In Progress

Bug description:
  After upgrading to Ubuntu 19.10 I noticed that all of my Windows
  Servers VMs would cause a hard crash on the Host OS shortly after
  starting up the VM.  I tracked it down to the Guest OS attempting to
  use the Network Connection, and if I disabled the virtual NIC for the
  VM, everything runs OK (albeit without a working network connection
  for the Guest OS).  Note that I'm just using the built in virtual
  network called "default" that get's installed by default and uses NAT
  forwarding.

  I believe the problem is related to AppArmor, as I noticed some errors
  present in various log files.

  Unfortunately, due to a time critical project I had to roll back to
  Ubuntu 19.04 and didn't capture any of the log files.  I did, however,
  find another user on Reddit with the exact same problems that I
  encountered and he agreed to let me post the log files.

  Here are what are think are the relevant pieces from the log files:

  ===

  Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM
  Oct 22 22:59:23 brian-pc kernel: [   67.001284] device virbr0-nic left 
promiscuous mode
  Oct 22 22:59:23 brian-pc kernel: [   67.001298] virbr0: port 1(virbr0-nic) 
entered disabled state
  Oct 22 22:59:23 brian-pc NetworkManager[3557]:   [1571799563.3862] 
device (virbr0-nic): released from master device virbr0
  Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer 
relevant for mDNS.
  Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on 
interface virbr0.IPv4 with address 192.168.122.1.
  Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 
192.168.122.1 on virbr0.
  Oct 22 22:59:23 brian-pc NetworkManager[3557]:   [1571799563.6859] 
device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', 
sys-iface-state: 'removed')
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: 
service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 
pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
  Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection 
(0x55ccfb376e50), has been already deallocated — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 
0x55ccfb8d15f0 ==
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0   55ccfbc736c0 i   
resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1   55ccfbc73628 i   
resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2   55ccfbc73588 i   
resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3   55ccfbc734f0 i   
resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4   55ccfbc73430 i   
self-hosted:979 (7f522262dee0 @ 440)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: 
connection.get_setting_ip4_config is not a 
function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: 
connectionSettings is 
null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9
  Oct 22 22:59:23 

[Kernel-packages] [Bug 1852110] [NEW] Xenial update: 4.4.200 upstream stable release

[Connor Kuehl]

Public bug reported:


SRU Justification

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

   4.4.200 upstream stable release
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Assignee: Connor Kuehl (connork)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Connor Kuehl (connork)

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

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

Title:
  Xenial update: 4.4.200 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  
  SRU Justification

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

 4.4.200 upstream stable release
 from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1813651] Re: hpsa: DMAR invalid read

[Guilherme G. Piccoli]

For the current Ubuntu releases, the kernels with this fix are listed
below.

* Xenial (16.04)
regular kernel: 4.4.0-159
HWE kernel: 4.15.0-60

* Bionic (18.04)
regular kernel: 4.15.0-60
HWE-Disco kernel: 5.0.0-31

* Disco (19.04)
regular kernel: 5.0.0-31

*Eoan (19.10):
regular kernel: all versions (the upstream fix came in v5.2; Eoan is based on 
v5.3)

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

Title:
  hpsa: DMAR invalid read

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  Recently in kernel 4.20-rc1 and newer we observed the following
  spontaneous issue with hpsa when intel_iommu is enabled:

  [ 5173.952022] DMAR: DRHD: handling fault status reg 2
  [ 5174.190649] DMAR: [DMA Read] Request device [03:00.0] fault addr eefdd000 
[fault reason 06] PTE Read access is not set

  There's a commit that touches DMA in hpsa: "scsi: hpsa: switch to generic DMA 
API"
  We've tested with this commit reverted on top of 4.20-rc1 and it reproduces 
(the trigger is a kernel build). We cannot reproduce in 4.19.

  Investigation is ongoing.

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

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

[Kernel-packages] [Bug 1852111] [NEW] Eoan update: 5.3.10 upstream stable release

[Connor Kuehl]

Public bug reported:


SRU Justification

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

   5.3.10 upstream stable release
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Eoan)
 Importance: Medium
 Assignee: Connor Kuehl (connork)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

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

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

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

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Connor Kuehl (connork)

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

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

Title:
  Eoan update: 5.3.10 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  In Progress

Bug description:
  
  SRU Justification

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

 5.3.10 upstream stable release
 from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1813651] Re: hpsa: DMAR invalid read

[Guilherme G. Piccoli]

The problem was fixed by the following commit, present in all Ubuntu
releases: 625d7d351887 ("scsi: hpsa: correct ioaccel2 chaining").
Basically it was an access to a DMA non-mapped region, and was
restricted to non-RAID mode adapters due to the I/O path being
different.

Since it was fixed, no more work or debug is necessary here.
Cheers,

Guilherme

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

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

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

Title:
  hpsa: DMAR invalid read

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  Recently in kernel 4.20-rc1 and newer we observed the following
  spontaneous issue with hpsa when intel_iommu is enabled:

  [ 5173.952022] DMAR: DRHD: handling fault status reg 2
  [ 5174.190649] DMAR: [DMA Read] Request device [03:00.0] fault addr eefdd000 
[fault reason 06] PTE Read access is not set

  There's a commit that touches DMA in hpsa: "scsi: hpsa: switch to generic DMA 
API"
  We've tested with this commit reverted on top of 4.20-rc1 and it reproduces 
(the trigger is a kernel build). We cannot reproduce in 4.19.

  Investigation is ongoing.

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

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

[Kernel-packages] [Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured

[Guilherme G. Piccoli]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Released

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

Title:
  kdump is not captured in remote host when kdump over ssh is configured

Status in The Ubuntu-power-systems project:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  Fix Released
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  Fix Released
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  * Kdump over network (like NFS mount or SSH dump) relies on network-
  online target from systemd. Even so, there are some NICs that report
  "Link Up" state but aren't ready to transmit packets. This is a
  generally bad behavior that is credited probably to NIC firmware
  delays, usually not fixable from drivers. Some adapters known to act
  like this are bnx2x, tg3 and ixgbe.

  * Kdump is a mechanism that may be a last resort to debug complex/hard
  to reproduce issues, so it's interesting to increase its reliability /
  resilience. We then propose here a solution/quirk to this issue on
  network dump by adding a retry/delay mechanism; if it's a network
  dump, kdump will retry some times and sleep between the attempts in
  order to exclude the case of NICs that aren't ready yet but will soon
  be able to transmit packets.

  * Although first reported by IBM in PowerPC arch, the scope for this
  issue is the NIC, and it was later reported in x86 arch too.

  [Test case]

  Usually it's difficult to naturally reproduce this issue in a deterministic 
way, but we have an artificial test case on comment #24 of this LP.
  Also, we have a report from this bug in which the user managed to reproduce 
the problem consistently - it's fixed after testing our solution.

  [Regression potential]

  There's not a clear regression potential here since it's just a retry/delay 
mechanism. Some potential problems may come from bad coding in the script.
  The delay between attempts is only 3 sec per iteration, so it shouldn't block 
the kdump progress for a high amount of time at once.

  [Other information]

  Salsa Debian commit:
  
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f

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

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

[Kernel-packages] [Bug 1852047] Re: [Bionic][Regression] Disabling EPT results in KVM guests that won't start

[Thadeu Lima de Souza Cascardo]

This works fine on an older CPU (that still supports EPT), launching
qemu directly, without libvirt. I will try with libvirt instead on that
older CPU, and look for access on some newer CPU to test that.

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

Title:
  [Bionic][Regression] Disabling EPT results in KVM guests that won't
  start

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

Bug description:
  Starting with 4.15.0-68.77, currently in bionic-proposed, I can no
  longer launch VMs when I disable EPT support in the kvm_intel module.
  This works fine under 4.15.0-66.75 from bionic-security.

   ubuntu@vought:~$ cat /proc/version_signature
   Ubuntu 4.15.0-68.77-generic 4.15.18
   ubuntu@vought:~$ sudo rmmod kvm_intel
   ubuntu@vought:~$ sudo modprobe kvm_intel ept=0
   ubuntu@vought:~$ cat /sys/module/kvm_intel/parameters/ept
   N
   ubuntu@vought:~$ virsh start --console l1
   Domain l1 started
   Connected to domain l1
   Escape character is ^]

  Under 4.15.0-66.75, I see full console output from the guest and reach
  a login prompt. Under 4.15.0-68.77, I see no output and the VM is
  unresponsive. I see nothing of use in /var/log/libvirt/qemu/l1.log.

  I see this on the following system:

  ubuntu@vought:~$ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  96
  On-line CPU(s) list: 0-95
  Thread(s) per core:  2
  Core(s) per socket:  24
  Socket(s):   2
  NUMA node(s):2
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   85
  Model name:  Intel(R) Xeon(R) Gold 6252 CPU @ 2.10GHz
  Stepping:6
  CPU MHz: 1000.135
  CPU max MHz: 3700.
  CPU min MHz: 1000.
  BogoMIPS:4200.00
  Virtualization:  VT-x
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:1024K
  L3 cache:36608K
  NUMA node0 CPU(s):   0-23,48-71
  NUMA node1 CPU(s):   24-47,72-95
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl 
xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb cat_l3 cdp_l3 invpcid_single ssbd mba ibrs ibpb stibp 
ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 
hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx 
smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec 
xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida 
arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req pku ospke avx512_vnni 
md_clear flush_l1d arch_capabilities

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

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

[Kernel-packages] [Bug 1850826] Re: nvidia-graphics-drivers-390 390.129-0ubuntu2 ADT test failure with linux 5.4.0-3.4

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-390 -
390.132-0ubuntu1

---
nvidia-graphics-drivers-390 (390.132-0ubuntu1) focal; urgency=medium

  * New upstream release:
- Fixed kernel module build problems with Linux kernel 5.4.0
  release candidates (LP: #1850826).
- Updated nvidia-bug-report.sh to collect information about X
  server crashes from coredumpctl, when available.
- Updated the nvidia-drm kernel module for compatibility with the
  removal of the DRIVER_PRIME flag in recent Linux kernel
  versions.

 -- Alberto Milone   Mon, 11 Nov 2019
12:37:44 +0100

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Fix Released

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

Title:
  nvidia-graphics-drivers-390 390.129-0ubuntu2 ADT test failure with
  linux 5.4.0-3.4

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-unstable/focal/amd64/n/nvidia-graphics-drivers-390/20191030_143354_e7fac@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1850826/+subscriptions

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

[Kernel-packages] [Bug 1848997] Re: bionic/linux-oracle-5.0: 5.0.0-1006.10~18.04.2 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848998
  packages:
lrm: linux-restricted-modules-oracle-5.0
main: linux-oracle-5.0
meta: linux-meta-oracle-5.0
signed: linux-signed-oracle-5.0
- phase: Testing
- phase-changed: Friday, 01. November 2019 22:46 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 16:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  variant: debs

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

Title:
  bionic/linux-oracle-5.0: 5.0.0-1006.10~18.04.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848998
  packages:
lrm: linux-restricted-modules-oracle-5.0
main: linux-oracle-5.0
meta: linux-meta-oracle-5.0
signed: linux-signed-oracle-5.0
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 16:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848997/+subscriptions

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

[Kernel-packages] [Bug 1848983] Re: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848984
  packages:
lrm: linux-restricted-modules-aws-5.0
main: linux-aws-5.0
meta: linux-meta-aws-5.0
- phase: Testing
- phase-changed: Wednesday, 23. October 2019 16:17 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 17:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  variant: debs

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

Title:
  bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848984
  packages:
lrm: linux-restricted-modules-aws-5.0
main: linux-aws-5.0
meta: linux-meta-aws-5.0
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 17:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848983/+subscriptions

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

[Kernel-packages] [Bug 1852070] Re: The alsa hda driver is not loaded due to the missing of PCIID for Comet Lake-S [8086:a3f0]

[Anthony Wong]

** Summary changed:

- The alsa hda driver is not loaded due to the missing of PCIID for Comet-S 
[8086:a3f0]
+ The alsa hda driver is not loaded due to the missing of PCIID for Comet 
Lake-S [8086:a3f0]

** Description changed:

- 
  [Impact]
- Intel Comet-S platform has the sound controller with PCIID 0x8086:a3f0,
+ Intel Comet Lake-S platform has the sound controller with PCIID 0x8086:a3f0,
  the ID is not in the alsa hda driver yet. When we run the linux on the
  Comet-S platform, the alsa hda driver will not be loaded.
  
  [Fix]
  Adding the PCIID into the alsa hda driver.
  
  [Test Case]
  We already tested this driver on a Dell Comet-S machine with the codec
  RT274, all audio devices worked well.
  
  [Regression Risk]
  Low, adding a new PCIID, will not introduce regression.

** Description changed:

  [Impact]
  Intel Comet Lake-S platform has the sound controller with PCIID 0x8086:a3f0,
  the ID is not in the alsa hda driver yet. When we run the linux on the
- Comet-S platform, the alsa hda driver will not be loaded.
+ Comet Lake-S platform, the alsa hda driver will not be loaded.
  
  [Fix]
  Adding the PCIID into the alsa hda driver.
  
  [Test Case]
- We already tested this driver on a Dell Comet-S machine with the codec
+ We already tested this driver on a Dell Comet Lake-S machine with the codec
  RT274, all audio devices worked well.
  
  [Regression Risk]
  Low, adding a new PCIID, will not introduce regression.

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

Title:
  The alsa hda driver is not loaded due to the missing of PCIID for
  Comet Lake-S [8086:a3f0]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Intel Comet Lake-S platform has the sound controller with PCIID 0x8086:a3f0,
  the ID is not in the alsa hda driver yet. When we run the linux on the
  Comet Lake-S platform, the alsa hda driver will not be loaded.

  [Fix]
  Adding the PCIID into the alsa hda driver.

  [Test Case]
  We already tested this driver on a Dell Comet Lake-S machine with the codec
  RT274, all audio devices worked well.

  [Regression Risk]
  Low, adding a new PCIID, will not introduce regression.

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

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

[Kernel-packages] [Bug 1848987] Re: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848989
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Testing
- phase-changed: Thursday, 24. October 2019 14:12 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 16:55 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-azure-edge: bug 1848986
bionic/linux-azure/azure-kernel: bug 1848985
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848989
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 16:55 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-azure-edge: bug 1848986
bionic/linux-azure/azure-kernel: bug 1848985
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848987/+subscriptions

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

[Kernel-packages] [Bug 1848984] Re: disco/linux-aws: 5.0.0-1020.22 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Testing
- phase-changed: Wednesday, 23. October 2019 10:19 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 16:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-aws-5.0: bug 1848983
  variant: debs

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

Title:
  disco/linux-aws: 5.0.0-1020.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 16:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-aws-5.0: bug 1848983
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848984/+subscriptions

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

[Kernel-packages] [Bug 1848981] Re: disco/linux-raspi2: 5.0.0-1021.21 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Wednesday, 23. October 2019 10:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Stalled -- testing FAILED
-   verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  disco/linux-raspi2: 5.0.0-1021.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Incomplete
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Wednesday, 23. October 2019 10:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Stalled -- testing FAILED
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848981/+subscriptions

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

[Kernel-packages] [Bug 1848992] Re: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848995
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Testing
- phase-changed: Thursday, 24. October 2019 14:07 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 16:55 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-gcp-edge: bug 1848991
bionic/linux-gcp/gcp-kernel: bug 1848990
  variant: debs

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

Title:
  bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848995
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 16:55 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-gcp-edge: bug 1848991
bionic/linux-gcp/gcp-kernel: bug 1848990
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848992/+subscriptions

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

[Kernel-packages] [Bug 1848998] Re: disco/linux-oracle: 5.0.0-1006.10 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Testing
- phase-changed: Wednesday, 23. October 2019 09:36 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 16:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-oracle-5.0: bug 1848997
  variant: debs

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

Title:
  disco/linux-oracle: 5.0.0-1006.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 16:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-oracle-5.0: bug 1848997
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848998/+subscriptions

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

[Kernel-packages] [Bug 1848995] Re: disco/linux-gcp: 5.0.0-1024.24 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Testing
- phase-changed: Thursday, 24. October 2019 15:26 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 16:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-gcp: bug 1848992
bionic/linux-gke-5.0: bug 1848994
  variant: debs

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

Title:
  disco/linux-gcp: 5.0.0-1024.24 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 16:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-gcp: bug 1848992
bionic/linux-gke-5.0: bug 1848994
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848995/+subscriptions

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

[Kernel-packages] [Bug 1848996] Re: disco/linux-kvm: 5.0.0-1021.22 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Testing
- phase-changed: Wednesday, 23. October 2019 09:46 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 16:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  variant: debs

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

Title:
  disco/linux-kvm: 5.0.0-1021.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 16:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848996/+subscriptions

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

[Kernel-packages] [Bug 1848989] Re: disco/linux-azure: 5.0.0-1024.25 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Testing
- phase-changed: Wednesday, 23. October 2019 09:36 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 16:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-azure: bug 1848987
  variant: debs

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

Title:
  disco/linux-azure: 5.0.0-1024.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 16:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release
  trackers:
bionic/linux-azure: bug 1848987
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848989/+subscriptions

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

[Kernel-packages] [Bug 1848999] Re: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Wednesday, 23. October 2019 15:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Stalled -- testing FAILED
-   verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Incomplete
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1850574
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Wednesday, 23. October 2019 15:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Stalled -- testing FAILED
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848999/+subscriptions

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

[Kernel-packages] [Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Testing
- phase-changed: Tuesday, 29. October 2019 13:37 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 16:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Stalled -- kernel-block/kernel-block-proposed tag 
present
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1851507
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849852
bionic/linux/pc-lowlatency-kernel: bug 1849853
unknown/unknown: bug 1849854
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

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

Title:
  bionic/linux: 4.15.0-68.77 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 16:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Stalled -- kernel-block/kernel-block-proposed tag 
present
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1851507
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849852
bionic/linux/pc-lowlatency-kernel: bug 1849853
unknown/unknown: bug 1849854
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+subscriptions

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

[Kernel-packages] [Bug 1850574] Re: disco/linux: 5.0.0-34.36 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Testing
- phase-changed: Wednesday, 30. October 2019 18:14 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 11. November 2019 16:20 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Stalled -- kernel-block/kernel-block-proposed tag 
present
  trackers:
bionic/linux-bluefield: bug 1849002
bionic/linux-hwe: bug 1850587
bionic/linux-oem-osp1: bug 1849001
disco/linux-aws: bug 1848984
disco/linux-azure: bug 1848989
disco/linux-gcp: bug 1848995
disco/linux-kvm: bug 1848996
disco/linux-oracle: bug 1848998
disco/linux-raspi2: bug 1848981
disco/linux-snapdragon: bug 1848999
  variant: debs

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

Title:
  disco/linux: 5.0.0-34.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 16:20 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Stalled -- kernel-block/kernel-block-proposed tag 
present
  trackers:
bionic/linux-bluefield: bug 1849002
bionic/linux-hwe: bug 1850587
bionic/linux-oem-osp1: bug 1849001
disco/linux-aws: bug 1848984
disco/linux-azure: bug 1848989
disco/linux-gcp: bug 1848995
disco/linux-kvm: bug 1848996
disco/linux-oracle: bug 1848998
disco/linux-raspi2: bug 1848981
disco/linux-snapdragon: bug 1848999
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850574/+subscriptions

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

[Kernel-packages] [Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker

[Stefan Bader]

All verifications seem to be done.

** Changed in: kernel-sru-workflow/verification-testing
   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/1849855

Title:
  bionic/linux: 4.15.0-68.77 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 16:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Stalled -- kernel-block/kernel-block-proposed tag 
present
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1851507
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849852
bionic/linux/pc-lowlatency-kernel: bug 1849853
unknown/unknown: bug 1849854
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+subscriptions

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

[Kernel-packages] [Bug 1803179] Re: System does not reliably come out of suspend

[odror]

on Which kernel (of the mainline) the patches are applied. Is it coming
soon or I have to apply the patches myself.

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

Title:
  System does not reliably come out of suspend

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 (9750); it might eventually manage to suspend when the lid
  is closed, but more often than not will not wake up again when the lid
  is opened. Waking up using the power button often results in a system
  that is apparently frozen (graphics displayed are the last on screen
  before suspend, clock seconds do not change)

  System is unresponsive to the keyboard at that time (can't switch to a
  VT or otherwise interact with the system other than holding the power
  button for a few seconds to shut it down).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mtrudel2516 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 13 10:42:08 2018
  InstallationDate: Installed on 2018-11-02 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1850574] Re: disco/linux: 5.0.0-34.36 -proposed tracker

[Stefan Bader]

The one problematic verification will be handled by release.

** Changed in: kernel-sru-workflow/verification-testing
   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/1850574

Title:
  disco/linux: 5.0.0-34.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Updates
  phase-changed: Monday, 11. November 2019 16:20 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Stalled -- kernel-block/kernel-block-proposed tag 
present
  trackers:
bionic/linux-bluefield: bug 1849002
bionic/linux-hwe: bug 1850587
bionic/linux-oem-osp1: bug 1849001
disco/linux-aws: bug 1848984
disco/linux-azure: bug 1848989
disco/linux-gcp: bug 1848995
disco/linux-kvm: bug 1848996
disco/linux-oracle: bug 1848998
disco/linux-raspi2: bug 1848981
disco/linux-snapdragon: bug 1848999
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850574/+subscriptions

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

[Kernel-packages] [Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile -
1:1.6.5-1ubuntu1~18.04.3

---
makedumpfile (1:1.6.5-1ubuntu1~18.04.3) bionic; urgency=medium

  [ Guilherme G. Piccoli ]
  * Add kdump retry/delay mechanism when dumping over network (LP: #1681909)

  [ Thadeu Lima de Souza Cascardo ]
  * Use maxcpus instead of nr_cpus on ppc64el. (LP: #1828597)
  * ppc64: increase MAX_PHYSMEM_BITS to 2PB (LP: #1841288)

  [ Connor Kuehl ]
  * Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860)

 -- Thadeu Lima de Souza Cascardo   Wed, 09 Oct
2019 15:38:08 -0300

** Changed in: makedumpfile (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  kdump is not captured in remote host when kdump over ssh is configured

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  Fix Released
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  Fix Released
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  * Kdump over network (like NFS mount or SSH dump) relies on network-
  online target from systemd. Even so, there are some NICs that report
  "Link Up" state but aren't ready to transmit packets. This is a
  generally bad behavior that is credited probably to NIC firmware
  delays, usually not fixable from drivers. Some adapters known to act
  like this are bnx2x, tg3 and ixgbe.

  * Kdump is a mechanism that may be a last resort to debug complex/hard
  to reproduce issues, so it's interesting to increase its reliability /
  resilience. We then propose here a solution/quirk to this issue on
  network dump by adding a retry/delay mechanism; if it's a network
  dump, kdump will retry some times and sleep between the attempts in
  order to exclude the case of NICs that aren't ready yet but will soon
  be able to transmit packets.

  * Although first reported by IBM in PowerPC arch, the scope for this
  issue is the NIC, and it was later reported in x86 arch too.

  [Test case]

  Usually it's difficult to naturally reproduce this issue in a deterministic 
way, but we have an artificial test case on comment #24 of this LP.
  Also, we have a report from this bug in which the user managed to reproduce 
the problem consistently - it's fixed after testing our solution.

  [Regression potential]

  There's not a clear regression potential here since it's just a retry/delay 
mechanism. Some potential problems may come from bad coding in the script.
  The delay between attempts is only 3 sec per iteration, so it shouldn't block 
the kdump progress for a high amount of time at once.

  [Other information]

  Salsa Debian commit:
  
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f

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

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

[Kernel-packages] [Bug 1741860] Re: Use the kernel default for crashkernel offset

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile -
1:1.6.5-1ubuntu1~18.04.3

---
makedumpfile (1:1.6.5-1ubuntu1~18.04.3) bionic; urgency=medium

  [ Guilherme G. Piccoli ]
  * Add kdump retry/delay mechanism when dumping over network (LP: #1681909)

  [ Thadeu Lima de Souza Cascardo ]
  * Use maxcpus instead of nr_cpus on ppc64el. (LP: #1828597)
  * ppc64: increase MAX_PHYSMEM_BITS to 2PB (LP: #1841288)

  [ Connor Kuehl ]
  * Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860)

 -- Thadeu Lima de Souza Cascardo   Wed, 09 Oct
2019 15:38:08 -0300

** Changed in: makedumpfile (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Use the kernel default for crashkernel offset

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  Fix Released
Status in makedumpfile source package in Disco:
  Fix Released
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The value chosen for ppc64el of 128MB aligns with that of the
  kernel default. That may change some day, so it would be best to let
  the kernel decide what value it should use. If the value does change
  and the kernel is not allowed to choose a value, this may stop the
  kernel from booting on a production system.

  [Test Case]

   Run `cat /etc/default/grub.d/kdump-tools.cfg`

   * Expected result: there is no offset specified at the end of the
  line (.e.g, @128M).

   * Actual result: For Xenial, Bionic, Disco, and Eoan there are
  offsets specified.

  [Regression Potential]

   * Right now, the offset described in the kdump-tools.cfg aligns with
  that of what the kernel would select, so since they are the same we
  would expect no change in operation.

  
  Original bug description follows:
  -

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-08 
01:06:41 ==
  ---Problem Description---
  A default offset of 128MB is enforced for crashkernel by kdump-tools utility
  overriding the kernel default.

  While the kernel default offset for crashkernel is also 128MB, that may change
  and the right thing to do would be to let the kernel decide on the offset of
  crashkernel in the default scenario..

  Get rid of "@128M" in kdump-tools.cfg file

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   # cat /etc/default/grub.d/kdump-tools.cfg
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M"
  ---

  The offset is specified via kdump-tools where as the kernel may be the right 
place to
  set an offset by default..

  Userspace tool common name: kdump-tools

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - MAMATHA INAMDAR  - 2018-01-08 03:05:05 
==
  This bug is opened to follow-up other bug based on the comment 19
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical 
Launchpad1676884 )

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

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

[Kernel-packages] [Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1.3

---
makedumpfile (1:1.6.5-1ubuntu1.3) disco; urgency=medium

  [ Guilherme G. Piccoli ]
  * Add kdump retry/delay mechanism when dumping over network (LP: #1681909)

  [ Thadeu Lima de Souza Cascardo ]
  * Use maxcpus instead of nr_cpus on ppc64el. (LP: #1828597)
  * ppc64: increase MAX_PHYSMEM_BITS to 2PB (LP: #1841288)

  [ Connor Kuehl ]
  * Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860)

 -- Thadeu Lima de Souza Cascardo   Wed, 09 Oct
2019 15:33:57 -0300

** Changed in: makedumpfile (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  kdump is not captured in remote host when kdump over ssh is configured

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  Fix Released
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  Fix Released
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  * Kdump over network (like NFS mount or SSH dump) relies on network-
  online target from systemd. Even so, there are some NICs that report
  "Link Up" state but aren't ready to transmit packets. This is a
  generally bad behavior that is credited probably to NIC firmware
  delays, usually not fixable from drivers. Some adapters known to act
  like this are bnx2x, tg3 and ixgbe.

  * Kdump is a mechanism that may be a last resort to debug complex/hard
  to reproduce issues, so it's interesting to increase its reliability /
  resilience. We then propose here a solution/quirk to this issue on
  network dump by adding a retry/delay mechanism; if it's a network
  dump, kdump will retry some times and sleep between the attempts in
  order to exclude the case of NICs that aren't ready yet but will soon
  be able to transmit packets.

  * Although first reported by IBM in PowerPC arch, the scope for this
  issue is the NIC, and it was later reported in x86 arch too.

  [Test case]

  Usually it's difficult to naturally reproduce this issue in a deterministic 
way, but we have an artificial test case on comment #24 of this LP.
  Also, we have a report from this bug in which the user managed to reproduce 
the problem consistently - it's fixed after testing our solution.

  [Regression potential]

  There's not a clear regression potential here since it's just a retry/delay 
mechanism. Some potential problems may come from bad coding in the script.
  The delay between attempts is only 3 sec per iteration, so it shouldn't block 
the kdump progress for a high amount of time at once.

  [Other information]

  Salsa Debian commit:
  
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f

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

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