date:20191125

** 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: 1852244
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Friday, 15. November 2019 23:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
+   regression-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1852240
  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/1852241

Title:
  bionic/linux-gcp: 5.0.0-1026.27~18.04.1 -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:
  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:
  Incomplete
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1852244
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Friday, 15. November 2019 23:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1852240
  variant: debs

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

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

[Kernel-packages] [Bug 1853446] Re: linux-raspi2: set two flavours to armhf kernel and change the flavour name to raspi4 for arm64 kernel

2019-11-25 Thread Juerg Haefliger

** Also affects: linux-raspi2 (Ubuntu Focal)
   Importance: Critical
 Assignee: Hui Wang (hui.wang)
   Status: New

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

** Changed in: linux-raspi2 (Ubuntu Eoan)
   Importance: Undecided => Critical

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

Title:
  linux-raspi2: set two flavours to armhf kernel and change the flavour
  name to raspi4 for arm64 kernel

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Eoan:
  New
Status in linux-raspi2 source package in Focal:
  New

Bug description:
  [Impact]
  It is risky to use single armhf kernel to support rpi2/3/4, since
  upstream has a specific config for rpi2/3 and another config for rpi4,
  the major difference are LPAE, HIGHMEM and VMSPLIT_3G, we already
  met a bug that is intrduced by HIGHMEM and VMSPLIT_3G on rpi2/3,
  so add two falvours for rpi2/3 and rpi4.
  flavour 1: raspi2 (for rpi2/3, disable LPAE, HIGHMEM and VMSPLIT_3G)
  flavour 2: raspi4 (for rpi4, enable LPAE, HIGHMEM and VMSPLIT_3G)

  For arm64 kernel, we change the flavour name to raspi4, it supports
  rpi2/3/4.

  [Fix]
  Change the related configuration files in the debian.raspi2.

  
  [Test Case]
  After apply the patches, and I built two flavours of armhf and
  arm64 kernels, Then check the .config, they all meet the expectation.
  And boot those kernels on the rpi2/3/4 boards. worked well.

  [Regression Risk]
  Low, just change the flavour name for arm64, and for armhf, the
  flavour raspi4 is basically same as bofre (raspi2), the new flavour
  raspi2 just disable LPAE/HIGHMEM/VMSPLIT_3G, it is same as the config
  for rpi2/3 in the upstream.

  
  For armhf kernel:
   flavour 1: raspi2  # support rpi2/3 boards
   flavour 2: raspi4  # support rpi4 boards (in theory support all rpi2/3/4 
boards)

  Form arm64 kernel:
   flavour 1: raspi4  # support rpi2/3/4 boards

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

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

[Kernel-packages] [Bug 1852241] Re: bionic/linux-gcp: 5.0.0-1026.27~18.04.1 -proposed tracker

Marked as Incomplete for the new failures in ubuntu_stress_smoke_test
(bug 1853944)

5.0.0-1026.27~18.04.1 - gcp
Regression test CMPL, RTB.

Issue to note in gcp:
  ubuntu_k8s_unit_tests - scheduler and spdy (bug 1824136)
  ubuntu_kernel_selftests - test_bpf in net (bug 1812189) msg_zerocopy in net 
(bug 1812620) trace_printk in ftrace (bug 1830084)
  ubuntu_ltp - test timeouted with 4 hours threshold on jenkins (bug 1837206)
  ubuntu_ltp_syscalls - clock_settime01 (bug 1850741) msgstress03 (bug 1797341) 
pivot_root01 (bug 1852966) stime01 (bug 1845620)
  ubuntu_stress_smoke_test - schedpolicy on every instances (bug 1853944)

Skipped / blacklisted:
 * libhugetlbfs


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

** 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-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1852241

Title:
  bionic/linux-gcp: 5.0.0-1026.27~18.04.1 -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:
  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:
  Incomplete
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1852244
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Friday, 15. November 2019 23:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1852240
  variant: debs

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

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

[Kernel-packages] [Bug 1852298] Re: xenial/linux-kvm: 4.4.0-1063.70 -proposed tracker

** 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: 1852306
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Friday, 15. November 2019 11:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1852298

Title:
  xenial/linux-kvm: 4.4.0-1063.70 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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: 1852306
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Friday, 15. November 2019 11:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1852298] Re: xenial/linux-kvm: 4.4.0-1063.70 -proposed tracker

4.4.0-1063.70 - kvm
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_ecryptfs - miscdev-bad-count.sh and lp-994247 on 5 filesystems (bug 
1837523)
  ubuntu_kernel_selftests - psock_tpacket in net failed (bug 1812176) test_bpf 
in net (bug 1812189) test_user_copy return code in user (bug 1812352)
  ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) 
memory (bug 1845687) port80 (bug 1748105) vmx (bug 1821394) 
vmx_apic_passthrough_thread (bug 1822309) vmx_hlt_with_rvi_test (bug 1822308)
  ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) 
msgstress03 (bug 1783881) pivot_root01 (bug 1852966) sync_file_range02 (bug 
1853422) pkey01 failure cannot be reproduced
  ubuntu_lxc - ERROR: Unable to fetch GPG key from keyserver. proxy issue for 
Intel Cloud (bug 1838966)
  ubuntu_xfstests* - no scratch drive available for the test

Skipped / blacklisted:
  * ubuntu_blktrace_smoke_test
  * ubuntu_bpf
  * ubuntu_fan_smoke_test
  * ubuntu_ftrace_smoke_test
  * ubuntu_ltp
  * ubuntu_lttng_smoke_test
  * ubuntu_seccomp
  * ubuntu_sysdig_smoke_test


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

** Tags added: regression-testing-passed

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

Title:
  xenial/linux-kvm: 4.4.0-1063.70 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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: 1852306
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Friday, 15. November 2019 11:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1853422] Re: sync_file_range02 from ubuntu_ltp_syscalls failed on T-aws 4.4

Spotted on X-kvm 4.4.0
Failed on XFS as well.

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

Title:
  sync_file_range02 from ubuntu_ltp_syscalls failed on T-aws 4.4

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

Bug description:
  Test failed xfs filesystem:
  tst_test.c:1278: INFO: Testing on xfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
  tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:71: PASS: Sync equals write
  sync_file_range02.c:74: FAIL: Sync inside of write: Synced 25165824, 
expected 16777216
  sync_file_range02.c:71: PASS: Sync overlaps with write

   startup='Mon Nov 18 08:59:23 2019'
   tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop0'
   tst_supported_fs_types.c:59: INFO: Kernel supports ext2
   tst_supported_fs_types.c:43: INFO: mkfs.ext2 does exist
   tst_supported_fs_types.c:59: INFO: Kernel supports ext3
   tst_supported_fs_types.c:43: INFO: mkfs.ext3 does exist
   tst_supported_fs_types.c:59: INFO: Kernel supports ext4
   tst_supported_fs_types.c:43: INFO: mkfs.ext4 does exist
   tst_supported_fs_types.c:59: INFO: Kernel supports xfs
   tst_supported_fs_types.c:43: INFO: mkfs.xfs does exist
   tst_supported_fs_types.c:59: INFO: Kernel supports btrfs
   tst_supported_fs_types.c:39: INFO: mkfs.btrfs does not exist
   tst_supported_fs_types.c:59: INFO: Kernel supports vfat
   tst_supported_fs_types.c:43: INFO: mkfs.vfat does exist
   tst_supported_fs_types.c:82: INFO: Filesystem exfat is not supported
   tst_test.c:1278: INFO: Testing on ext2
   tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
   mke2fs 1.42.9 (4-Feb-2014)
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   sync_file_range02.c:71: PASS: Sync equals write
   sync_file_range02.c:71: PASS: Sync inside of write
   sync_file_range02.c:71: PASS: Sync overlaps with write
   tst_test.c:1278: INFO: Testing on ext3
   tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext3 opts='' extra opts=''
   mke2fs 1.42.9 (4-Feb-2014)
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   sync_file_range02.c:71: PASS: Sync equals write
   sync_file_range02.c:71: PASS: Sync inside of write
   sync_file_range02.c:71: PASS: Sync overlaps with write
   tst_test.c:1278: INFO: Testing on ext4
   tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts=''
   mke2fs 1.42.9 (4-Feb-2014)
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   sync_file_range02.c:71: PASS: Sync equals write
   sync_file_range02.c:71: PASS: Sync inside of write
   sync_file_range02.c:71: PASS: Sync overlaps with write
   tst_test.c:1278: INFO: Testing on xfs
   tst_mkfs.c:90: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   sync_file_range02.c:71: PASS: Sync equals write
   sync_file_range02.c:74: FAIL: Sync inside of write: Synced 25165824, 
expected 16777216
   sync_file_range02.c:71: PASS: Sync overlaps with write
   tst_test.c:1278: INFO: Testing on vfat
   tst_mkfs.c:90: INFO: Formatting /dev/loop0 with vfat opts='' extra opts=''
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   sync_file_range02.c:111: INFO: Pre-filling file
   sync_file_range02.c:71: PASS: Sync equals write
   sync_file_range02.c:71: PASS: Sync inside of write
   sync_file_range02.c:71: PASS: Sync overlaps with write

   Summary:
   passed 14
   failed 1
   skipped 0
   warnings 0
   tag=sync_file_range02 stime=1574067563 dur=4 exit=exited stat=1 core=no cu=0 
cs=57

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

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

[Kernel-packages] [Bug 1838245] Re: dkms script is missing function find_module

2019-11-25 Thread Mathew Hodson

** Tags removed: verification-needed

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

Title:
  dkms script is missing function find_module

Status in DKMS:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Bionic:
  Fix Released
Status in dkms source package in Disco:
  Fix Released
Status in dkms source package in Eoan:
  Fix Released
Status in dkms source package in Focal:
  Fix Released

Bug description:
  
  update for SRU process:
  [Impact]
  1. dkms script is missing function find_module
  2. priority of OBSOLETE_BY should higher than "force". #89  
https://github.com/dell/dkms/issues/89

  [Test case]
  install the dkms which already patched (also can be found in my ppa[1])
  1. install a dkms which for a kernel module system already installed.
  e.g. ath10k of my testing ppa : [1] 
  1.1. the dkms can be installed well.

  2. install a dkms which has OBSOLETE_BY and FORCE
  e.g.ath10k of my testing ppa : [1] (source code in [2])
   - the target dkms defined OBSOLETE_BY and FORCE
   - user install dkms on a system which installed kernel version less than 
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
   - the dkms can be installed well.

  [Regression potential]
  medium as it touched the version sanity. This change correct the code logic 
and land one more change from upstream as well.
  The logic has been verified by #5 and me.

  
  Building a kernel module using dkms in Linux Mint 19.1 shows the following 
error:

  Running module version sanity check.
  /usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden
  modinfo: ERROR: missing module or filename.

  Checking the file the function is indeed missing and another user
  confirmed, that it was removed at some point:
  https://github.com/linuxmint/linuxmint/issues/142

  Possible solution: Readd

  find_module()
  {
  # tree = $1
  # module = $2
  find "$1" -name "$2$module_uncompressed_suffix" -o -name 
"$2$module_suffix" -type f
  return $?
  }

  as found in https://github.com/dell/dkms/blob/master/dkms

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

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

[Kernel-packages] [Bug 1847948] Re: Improve NVMe guest performance on Bionic QEMU

2019-11-25 Thread Frank Heimes

Thanks for the verification Murillo.
I updated the tags based on comment #25.

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

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

Title:
  Improve NVMe guest performance on Bionic QEMU

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in qemu source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO.
     But there can be platforms (like ppc64 spapr) that can and want to do
     exactly that.

   * Backport two patches from upstream (in since qemu 2.12 / Disco).

   * Due to that there is a tremendous speedup, especially useful with page
     size bigger than 4k. This avoids that being split into chunks and makes
     direct MMIO access possible for the guest.

  [Test Case]

   * On ppc64 pass through an NVME device to the guest and run I/O
     benchmarks, see below for Details how to set that up.
     Note: this needs the HWE kernel or another kernel fixup for [1].
 Note: the test should also be done with the non-HWE kernel, the 
 expectation there is that it would not show the perf benefits, but 
 still work fine

  [Regression Potential]

   * Changes:
     a) if the host driver allows mapping of MSI-X data the entire BAR is
    mapped. This is only done if the kernel reports that capability [1].
    This ensures that only on kernels able to do so qemu does expose the
    new behavior (safe against regression in that regard)
     b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local
    to just this HW and will not affect other HW.

     Generally the regressions that come to mind are slight changes in
     behavior (real HW vs the former emulation) that on some weird/old
     guests could cause trouble. But then it is limited to only PPC where
     only a small set of certified HW is really allowed.

     The mapping that might be added even on other platforms should not
     consume too much extra memory as long as it isn't used. Further since
     it depends on the kernel capability it isn't randomly issues on kernels
     where we expect it to fail.

     So while it is quite a change, it seems safe to me.

  [Other Info]

   * I know, one could as well call that a "feature", but it really is a
     performance bug fix more than anything else. Also the SRU policy allows
     exploitation/toleration of new HW especially for LTS releases.
     Therefore I think this is fine as SRU.

  [1]:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a32295c612c57990d17fb0f41e7134394b2f35f6

  == Comment: #0 - Murilo Opsfelder Araujo  - 2019-10-11 14:16:14 ==

  ---Problem Description---
  Back-port the following patches to Bionic QEMU to improve NVMe guest 
performance by more than 200%:

  ?vfio-pci: Allow mmap of MSIX BAR?
  
https://git.qemu.org/?p=qemu.git;a=commit;h=ae0215b2bb56a9d5321a185dde133bfdd306a4c0

  ?ppc/spapr, vfio: Turn off MSIX emulation for VFIO devices?
  
https://git.qemu.org/?p=qemu.git;a=commit;h=fcad0d2121976df4b422b4007a5eb7fcaac01134

  ---uname output---
  na

  ---Additional Hardware Info---
  0030:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe 
SSD Controller 172Xa/172Xb (rev 01)

  Machine Type = AC922

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

  ---Steps to Reproduce---
   Install or setup a guest image and boot it.

  Once guest is running, passthrough the NVMe disk to the guest using
  the XML:

  host$ cat nvme-disk.xml
  
     
  
  
  
  

  host$ virsh attach-device  nvme-disk.xml --live

  On the guest, run fio benchmarks:

  guest$ fio --direct=1 --rw=randrw --refill_buffers --norandommap
  --randrepeat=0 --ioengine=libaio --bs=4k --rwmixread=100 --iodepth=16
  --runtime=60 --name=job1 --filename=/dev/nvme0n1 --numjobs=4

  Results are similar with numjobs=4 and numjobs=64, respectively:

     READ: bw=385MiB/s (404MB/s), 78.0MiB/s-115MiB/s (81.8MB/s-120MB/s), 
io=11.3GiB (12.1GB), run=30001-30001msec
     READ: bw=382MiB/s (400MB/s), 2684KiB/s-12.6MiB/s (2749kB/s-13.2MB/s), 
io=11.2GiB (12.0GB), run=30001-30009msec

  With the two patches applied, performance improved significantly for
  numjobs=4 and numjobs=64 cases, respectively:

     READ: bw=1191MiB/s (1249MB/s), 285MiB/s-309MiB/s (299MB/s-324MB/s), 
io=34.9GiB (37.5GB), run=30001-30001msec
     READ: bw=4273MiB/s (4481MB/s), 49.7MiB/s-113MiB/s (52.1MB/s-119MB/s), 
io=125GiB (134GB), run=30001-30005msec

  Userspace tool common name: qemu

  Userspace rpm: qemu

  The userspace tool has the following bit

[Kernel-packages] [Bug 1852070] Re: The alsa hda driver is not loaded due to the missing of PCIID for Comet Lake-S [8086:a3f0]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  New
Status in linux-oem-osp1 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  New
Status in linux-oem-osp1 source package in Eoan:
  Invalid

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 1843794] Re: CML CPUIDs

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

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

Title:
  CML CPUIDs

Status in intel:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  Description
  Please upstream CPUID for all CML SKUs.

  CML-U/CML-S/CML-Y/CML-H

  Target Release: 20.04
  Target Kernel: TBD

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

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

[Kernel-packages] [Bug 1853694] Re: Ubuntu causing eye strain on Intel Integrated Graphics

2019-11-25 Thread Timo Aaltonen

the flicker is a driver bug, test a newer mainline kernel build

https://kernel.ubuntu.com/~kernel-ppa/mainline/

test with drm-tip, and if it still flickers, a bug should be filed
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/1853694

Title:
  Ubuntu causing eye strain on Intel Integrated Graphics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find when running Ubuntu after 5-10 minutes get heavy eyes and after
  a few hours develop dizziness/headaches.

  After research online and talking with a community at LED Strain
  (https://ledstrain.org) it is believed the issue is caused by
  dithering being enabled on Ubuntu. There is no known way turn off all
  dithering by default and would like an option to turn off all
  dithering to avoid discomfort.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-36-generic 5.0.0-36.39~18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 23 12:56:12 2019
  InstallationDate: Installed on 2019-11-22 (1 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1848491] Re: drm/i915: Add support for another CMP-H PCH

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

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

Title:
  drm/i915: Add support for another CMP-H PCH

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

Bug description:
  [Impact]

  There's a new PCH model for Comet Lake, and drm/i915 needs to know
  about it or otherwise graphics won't work.

  [Test case]
  Check that i915 loads and works properly.

  [Regression potential]
  None, adds a new pci-id.

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

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

[Kernel-packages] [Bug 1852386] Re: no HDMI video output since GDM greeter after linux-oem-osp1 version 5.0.0-1026

** Changed in: linux-oem-osp1 (Ubuntu Focal)
   Status: New => Invalid

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

Title:
  no HDMI video output since GDM greeter after linux-oem-osp1 version
  5.0.0-1026

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  In Progress
Status in linux-oem-osp1 source package in Eoan:
  New
Status in linux source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [SRU Justification: oem-osp1-bionic]

  [Impact]
  Bug 1849278 introduced a regression on some Comet Lake platforms that
  device may have no video output on HDMI port.

  [Fix]
  A currently in-review patch
  https://patchwork.freedesktop.org/patch/340416 should be applied to
  correct PCH's identity and restore HDMI output.

  [Test Case]
  1. Apply the patches to oem-osp1 kernel >= 1026 or Eoan/Focal generic
  kernels.
  2. Boot affected platforms with HDMI cable connected to an external
  monitor.
  3. Check if the monitor lights up when GDM service is started.

  This was verified in to victim platforms.

  [Regression Risk]
  Low. This should affects only systems with matching PCH hw that is
  currently affected by the regression to be fixed.

  ==

  [SRU Justification: E/F/U]

  [Impact]
  Some Comet Lake platforms got i915 call trace dump due to the lake of
  support to its PCH id:

[2.999233] [ cut here ]
[2.999238] eDP powered off while attempting aux channel
communication.
[2.999338] WARNING: CPU: 2 PID: 296 at
drivers/gpu/drm/i915/display/intel_dp.c:1148
intel_dp_aux_xfer+0x767/0x900 [i915]
[2.999341] Modules linked in: i915(+) i2c_algo_bit drm_kms_helper
syscopyarea sysfillrect sysimgblt fb_sys_fops drm r8169 ahci realtek
libahci wmi video
[2.999350] CPU: 2 PID: 296 Comm: systemd-udevd Not tainted
5.3.0-997-generic #201910072204
[2.999352] Hardware name: Dell Inc. OptiPlex 3280 AIO/, BIOS
99.00.08 10/01/2019
[2.999391] RIP: 0010:intel_dp_aux_xfer+0x767/0x900 [i915]
[2.999394] Code: e8 ee b5 ff ff 84 c0 0f 85 ec f9 ff ff 48 8b 7d 80
e8 5d b6 ff ff 84 c0 0f 85 db f9 ff ff 48 c7 c7 50 22 5d c0 e8 84 ea b5
d1 <0f> 0b 48 8b 7d 80 48 8d 75 90 4c 8d ab a8 07 00 00 e8 63 b4 ff ff
[2.999398] RSP: 0018:b740b5b8 EFLAGS: 00010286
[2.999400] RAX:  RBX: 9bfa9dc2 RCX:
0396
[2.999402] RDX: 0001 RSI: 0082 RDI:
0246
[2.999404] RBP: b740b698 R08: 0396 R09:
0019
[2.999406] R10: 072e R11: b740b420 R12:
0004
[2.999408] R13: 9bfa9fbca120 R14: 9bfa9dc2 R15:
9bfa9dc207a8
[2.999410] FS:  7f0d8613a680() GS:9bfaaec8()
knlGS:
[2.999412] CS:  0010 DS:  ES:  CR0: 80050033
[2.999414] CR2: 7ffca955ae58 CR3: 00041e67e002 CR4:
003606e0
[2.999416] DR0:  DR1:  DR2:

[2.999418] DR3:  DR6: fffe0ff0 DR7:
0400
[2.999420] Call Trace:
[2.999425]  ? vprintk_default+0x29/0x50
[2.999464]  intel_dp_aux_transfer+0x15e/0x220 [i915]
[2.999472]  drm_dp_dpcd_access+0x72/0x110 [drm_kms_helper]
[2.999478]  drm_dp_dpcd_read+0x33/0xc0 [drm_kms_helper]
[2.999515]  intel_dp_read_dpcd+0x41/0x130 [i915]
[2.999551]  intel_edp_init_connector+0x136/0x540 [i915]
[2.999587]  intel_dp_init_connector+0x47f/0x870 [i915]
[2.999623]  intel_ddi_init+0x425/0x590 [i915]
[2.999660]  intel_setup_outputs+0x8e4/0xc60 [i915]

  [Fix]
  Two patches to be backported to have correct support:
  * commit 37c92dc303dd "drm/i915: Add new CNL PCH ID seen on a CML
platform" from drm-tip tree.
  * patch "https://patchwork.freedesktop.org/patch/340416;

  [Test Case]
  1. Apply the patches to oem-osp1 kernel >= 1026 or Eoan/Focal generic
  kernels.
  2. Boot affected platforms with HDMI cable connected to an external
  monitor.
  3. Check if the monitor lights up when GDM service is started.

  This was verified in to victim platforms.

  [Regression Risk]
  Low. This should affects only systems with matching PCH hw that is
  currently affected by the regression to be fixed.

  == original bug description ==

  This is a regression caused by bug 1849278, which sends external

[Kernel-packages] [Bug 1848555] Re: Add Intel Comet Lake ethernet support

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

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

Title:
  Add Intel Comet Lake ethernet support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
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:
  [Impact]
  e1000e.ko doesn't load for Intel CML ethernet.

  [Fix]
  Add missing ID for the device.

  [Test]
  The driver loads and works once the ID is added.

  [Regression Potential]
  Minimal. Only adds some IDs, no functional change at all.

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

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

[Kernel-packages] [Bug 1849721] Re: Raydium Touchscreen on ThinkPad L390 does not work

2019-11-25 Thread Kai-Heng Feng

** Description changed:

+ == SRU Justification ===
+ 
+ [Impact]
+ Raydium touchscreen on ThinkPad L390 doesn't work.
+ 
+ [Fix]
+ Use I2C_HID_QUIRK_NO_IRQ_AFTER_RESET to introduce an extra delay after
+ resetting the device.
+ 
+ [Test]
+ User confirmed the touchpad works with the patch.
+ 
+ [Regression Potential]
+ Low. This fix limits to one device and is quite trivial.
+ 
+ == Original Bug Report ===
+ 
  I have bought new Lenovo ThinkPad L390 with touchscreen and it works fine on 
Windows, but not on Ubuntu.
  I've tried Ubuntu LTS 18.4, 19.4 and 19.10. I've tried installing Ubuntu and 
running Live USB image, and also other distributions (Manjaro i3, Kubuntu).
  There is an Ubuntu certification with the same touchscreen using Ubuntu 18.4: 
https://certification.ubuntu.com/hardware/201812-26720
  
  Other info:
  - `xinput` is showing touchscreen: "Raydium Touchscreen id=10 [slave pointer 
(2)]"
  - if I list device props using `xinput list-props 10`, I see device: `Device 
Node (277): "/dev/input/event9"`
  - `cat /dev/input/event9` does not produce anything
  - `xinput --test-xi2 --root` does not produce any touchscreen events, even 
though events from other devices are successfully shown
  
  Also, attached `ubuntu-bug` report.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  ubuntu 1821 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu 1821 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 24 18:32:07 2019
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20NRCTO1WW
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
-  linux-restricted-modules-5.3.0-18-generic N/A
-  linux-backports-modules-5.3.0-18-generic  N/A
-  linux-firmware1.183
+  linux-restricted-modules-5.3.0-18-generic N/A
+  linux-backports-modules-5.3.0-18-generic  N/A
+  linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R10ET39W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NRCTO1WW:pvrThinkPadL390:rvnLENOVO:rn20NRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L390
  dmi.product.name: 20NRCTO1WW
  dmi.product.sku: LENOVO_MT_20NR_BU_Think_FM_ThinkPad L390
  dmi.product.version: ThinkPad L390
  dmi.sys.vendor: LENOVO

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

Title:
  Raydium Touchscreen on ThinkPad L390 does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == SRU Justification ===

  [Impact]
  Raydium touchscreen on ThinkPad L390 doesn't work.

  [Fix]
  Use I2C_HID_QUIRK_NO_IRQ_AFTER_RESET to introduce an extra delay after
  resetting the device.

  [Test]
  User confirmed the touchpad works with the patch.

  [Regression Potential]
  Low. This fix limits to one device and is quite trivial.

  == Original Bug Report ===

  I have bought new Lenovo ThinkPad L390 with touchscreen and it works fine on 
Windows, but not on Ubuntu.
  I've tried Ubuntu LTS 18.4, 19.4 and 19.10. I've tried installing Ubuntu and 
running Live USB image, and also other distributions (Manjaro i3, Kubuntu).
  There is an Ubuntu certification with the same touchscreen using Ubuntu 18.4: 
https://certification.ubuntu.com/hardware/201812-26720

  Other info:
  - `xinput` is showing touchscreen: "Raydium Touchscreen id=10 [slave pointer 
(2)]"
  - if I list device props using `xinput list-props 10`, I see device: `Device 
Node (277): "/dev/input/event9"`
  - `cat /dev/input/event9` does not produce anything
  - `xinput --test-xi2 --root` does not produce any touchscreen events, even 
though events from other devices are successfully shown

  Also, attached `ubuntu-bug` report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10

[Kernel-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140

2019-11-25 Thread David Ward

** Package changed: ubuntu => hwe-next

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in HWE Next:
  Confirmed
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT
  is set to Y, then it will make the legacy intel soc driver fail, and
  moreover the current sof driver can't support broadwell well, as a
  result, many broadwell computers with I2S codec can't support sound anymore.

  [Fix]
  Intel submitted a patch, it will make those two kconfig options exclusive,
  and the legacy soc's option has higher priority, if both of them are
  enabled, sof's option will be disabled.

  [Test Case]
  Build the kernel and check the debian/build/$buidling_dir/.config,  the
  SND_SOC_SOF_BROADWELL_SUPPORT is disabled.

  [Regression Risk]
  Low, so far, the sof driver can't support broadwell machine well, so
  there is no machine use this driver yet.


  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <->

[Kernel-packages] [Bug 1851901] Re: Touchpad doesn't work on Dell Inspiron 7000 2-in-1

2019-11-25 Thread Kai-Heng Feng

** Description changed:

+ === SRU Justification ===
+ 
+ [Impact]
+ On new Intel SoC, blacklisting intel-lpss or noapic is needed to make
+ system boot. Touchpad doesn't work as a side effect.
+ 
+ [Fix]
+ Write-comining doesn't work for intel-lpss, force it to use uncachable
+ memory region.
+ 
+ [Test]
+ User confirmed with the patch series the noapic or blacklisting
+ intel-lpss can be removed. System boot with a working touchpad.
+ 
+ [Regression Potenial]
+ Low. Tested on several older Intel laptops, still work without any
+ issue.
+ 
+ === Original Bug Report ===
+ 
  I run Ubuntu 19.04 on Dell inspiron 7000 2-in-1.
  
  After a fresh install the touchpad doesn't work, the touchscreen doesn't
  work, when the laptop doesn't recover after a suspend to RAM, it boots
  only with noapic option. The laptop is very recent, I think the hardware
  is not supported well. But I would like your advice, perhaps I can do
  something to get a working setup.
  
  The xinput output:
  
  ```
  $ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PixArt HP X500 USB Optical Mouseid=8[slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Generic Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
- ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
- ↳ Video Bus   id=6[slave  
keyboard (3)]
- ↳ Power Buttonid=7[slave  
keyboard (3)]
- ↳ Integrated_Webcam_HD: Integrate id=9[slave  
keyboard (3)]
- ↳ Intel HID eventsid=10   [slave  
keyboard (3)]
- ↳ Dell WMI hotkeysid=11   [slave  
keyboard (3)]
- ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
+ ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
+ ↳ Video Bus   id=6[slave  
keyboard (3)]
+ ↳ Power Buttonid=7[slave  
keyboard (3)]
+ ↳ Integrated_Webcam_HD: Integrate id=9[slave  
keyboard (3)]
+ ↳ Intel HID eventsid=10   [slave  
keyboard (3)]
+ ↳ Dell WMI hotkeysid=11   [slave  
keyboard (3)]
+ ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ```
  
  ```
  $ lspci
  00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c)
  00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
  00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 
/ 6th/7th Gen Core Processor Gaussian Mixture Model
  00:12.0 Signal processing controller: Intel Corporation Device 02f9
  00:13.0 Serial controller: Intel Corporation Device 02fc
  00:14.0 USB controller: Intel Corporation Device 02ed
  00:14.2 RAM memory: Intel Corporation Device 02ef
  00:14.3 Network controller: Intel Corporation Device 02f0
  00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8
  00:15.1 Serial bus controller [0c80]: Intel Corporation Device 02e9
  00:16.0 Communication controller: Intel Corporation Device 02e0
  00:17.0 SATA controller: Intel Corporation Device 02d3
  00:1c.0 PCI bridge: Intel Corporation Device 02bc (rev f0)
  00:1d.0 PCI bridge: Intel Corporation Device 02b4 (rev f0)
  00:1f.0 ISA bridge: Intel Corporation Device 0284
  00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8
  00:1f.4 SMBus: Intel Corporation Device 02a3
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 02a4
  01:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 2C 2018] (rev 06)
  02:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 2C 2018] (rev 06)
  02:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 2C 2018] (rev 06)
  02:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 2C 2018] (rev 06)
  03:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan 
Ridge 2C 2018] (rev 06)
  3b:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge 2C 2018] (rev 06)
  3c:00.0 Non-Volatile memory controller: Sandisk Corp Device 5004 (rev 01)
  ```
  
  If you need some additional information please let me know.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion:

[Kernel-packages] [Bug 1853881] Re: Xenial update: 4.4.203 upstream stable release

2019-11-25 Thread 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/1853881

Title:
  Xenial update: 4.4.203 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:

  * slip: Fix memory leak in slip_open error path
  * ax88172a: fix information leak on short answers
  * ALSA: usb-audio: Fix missing error check at mixer resolution test
  * ALSA: usb-audio: not submit urb for stopped endpoint
  * Input: ff-memless - kill timer in destroy()
  * ecryptfs_lookup_interpose(): lower_dentry->d_inode is not stable
  * ecryptfs_lookup_interpose(): lower_dentry->d_parent is not stable either
  * iommu/vt-d: Fix QI_DEV_IOTLB_PFSID and QI_DEV_EIOTLB_PFSID macros
  * mm: memcg: switch to css_tryget() in get_mem_cgroup_from_mm()
  * mm: hugetlb: switch to css_tryget() in hugetlb_cgroup_charge_cgroup()
  * mmc: sdhci-of-at91: fix quirk2 overwrite
  * iio: dac: mcp4922: fix error handling in mcp4922_write_raw
  * ALSA: pcm: signedness bug in snd_pcm_plug_alloc()
  * ARM: dts: at91/trivial: Fix USART1 definition for at91sam9g45
  * ALSA: seq: Do error checks at creating system ports
  * gfs2: Don't set GFS2_RDF_UPTODATE when the lvb is updated
  * ASoC: dpcm: Properly initialise hw->rate_max
  * MIPS: BCM47XX: Enable USB power on Netgear WNDR3400v3
  * ARM: dts: exynos: Fix sound in Snow-rev5 Chromebook
  * i40e: use correct length for strncpy
  * i40e: hold the rtnl lock on clearing interrupt scheme
  * i40e: Prevent deleting MAC address from VF when set by PF
  * ARM: dts: pxa: fix power i2c base address
  * rtl8187: Fix warning generated when strncpy() destination length matches 
the sixe argument
  * net: lan78xx: Bail out if lan78xx_get_endpoints fails
  * ASoC: sgtl5000: avoid division by zero if lo_vag is zero
  * ath10k: wmi: disable softirq's while calling ieee80211_rx
  * mips: txx9: fix iounmap related issue
  * of: make PowerMac cache node search conditional on CONFIG_PPC_PMAC
  * ARM: dts: omap3-gta04: give spi_lcd node a label so that we can overwrite 
in other DTS files
  * ARM: dts: omap3-gta04: tvout: enable as display1 alias
  * ARM: dts: omap3-gta04: make NAND partitions compatible with recent U-Boot
  * ARM: dts: omap3-gta04: keep vpll2 always on
  * dmaengine: dma-jz4780: Further residue status fix
  * signal: Always ignore SIGKILL and SIGSTOP sent to the global init
  * signal: Properly deliver SIGILL from uprobes
  * signal: Properly deliver SIGSEGV from x86 uprobes
  * scsi: sym53c8xx: fix NULL pointer dereference panic in sym_int_sir()
  * ARM: imx6: register pm_power_off handler if "fsl,pmic-stby-poweroff" is set
  * scsi: pm80xx: Corrected dma_unmap_sg() parameter
  * scsi: pm80xx: Fixed system hang issue during kexec boot
  * kprobes: Don't call BUG_ON() if there is a kprobe in use on free list
  * nvmem: core: return error code instead of NULL from nvmem_device_get
  * media: fix: media: pci: meye: validate offset to avoid arbitrary access
  * ALSA: intel8x0m: Register irq handler after register initializations
  * pinctrl: at91-pio4: fix has_config check in atmel_pctl_dt_subnode_to_map()
  * llc: avoid blocking in llc_sap_close()
  * powerpc/vdso: Correct call frame information
  * ARM: dts: socfpga: Fix I2C bus unit-address error
  * pinctrl: at91: don't use the same irqchip with multiple gpiochips
  * cxgb4: Fix endianness issue in t4_fwcache()
  * power: supply: ab8500_fg: silence uninitialized variable warnings
  * power: supply: max8998-charger: Fix platform data retrieval
  * kernfs: Fix range checks in kernfs_get_target_path
  * s390/qeth: invoke softirqs after napi_schedule()
  * PCI/ACPI: Correct error message for ASPM disabling
  * serial: mxs-auart: Fix potential infinite loop
  * powerpc/iommu: Avoid derefence before pointer check
  * powerpc/64s/hash: Fix stab_rr off by one initialization
  * powerpc/pseries: Disable CPU hotplug across migrations
  * libfdt: Ensure INT_MAX is defined in libfdt_env.h
  * power: supply: twl4030_charger: fix charging current out-of-bounds
  * power: supply: twl4030_charger: disable eoc interrupt on linear charge
  * net: toshiba: fix return type of ndo_start_xmit function
  * net: xilinx: fix return type of ndo_start_xmit function
  * net: broadcom: fix return type of ndo_start_xmit function
  * net: amd: fix return type of ndo_start_xmit

[Kernel-packages] [Bug 1853915] Re: Bionic update: upstream stable patchset 2019-11-25

2019-11-25 Thread 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/1853915

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

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

  Ported from the following upstream stable releases:
  v4.14.155, v4.19.85

     from git://git.kernel.org/

  kvm: mmu: Don't read PDPTEs when paging is not enabled
  KVM: x86: introduce is_pae_paging
  MIPS: BCM63XX: fix switch core reset on BCM6368
  scsi: core: Handle drivers which set sg_tablesize to zero
  Revert "Input: synaptics-rmi4 - avoid processing unknown IRQs"
  ax88172a: fix information leak on short answers
  net: usb: qmi_wwan: add support for Foxconn T77W968 LTE modules
  slip: Fix memory leak in slip_open error path
  ALSA: usb-audio: Fix missing error check at mixer resolution test
  ALSA: usb-audio: not submit urb for stopped endpoint
  Input: ff-memless - kill timer in destroy()
  Input: synaptics-rmi4 - fix video buffer size
  Input: synaptics-rmi4 - disable the relative position IRQ in the F12 driver
  Input: synaptics-rmi4 - do not consume more data than we have (F11, F12)
  Input: synaptics-rmi4 - clear IRQ enables for F54
  Input: synaptics-rmi4 - destroy F54 poller workqueue when removing
  IB/hfi1: Ensure full Gen3 speed in a Gen4 system
  i2c: acpi: Force bus speed to 400KHz if a Silead touchscreen is present
  ecryptfs_lookup_interpose(): lower_dentry->d_inode is not stable
  ecryptfs_lookup_interpose(): lower_dentry->d_parent is not stable either
  iommu/vt-d: Fix QI_DEV_IOTLB_PFSID and QI_DEV_EIOTLB_PFSID macros
  mm: memcg: switch to css_tryget() in get_mem_cgroup_from_mm()
  mm: hugetlb: switch to css_tryget() in hugetlb_cgroup_charge_cgroup()
  mmc: sdhci-of-at91: fix quirk2 overwrite
  iio: adc: max9611: explicitly cast gain_selectors
  tee: optee: take DT status property into account
  ath10k: fix kernel panic by moving pci flush after napi_disable
  iio: dac: mcp4922: fix error handling in mcp4922_write_raw
  arm64: dts: allwinner: a64: Olinuxino: fix DRAM voltage
  arm64: dts: allwinner: a64: NanoPi-A64: Fix DCDC1 voltage
  ALSA: pcm: signedness bug in snd_pcm_plug_alloc()
  arm64: dts: tegra210-p2180: Correct sdmmc4 vqmmc-supply
  ARM: dts: at91/trivial: Fix USART1 definition for at91sam9g45
  rtc: rv8803: fix the rv8803 id in the OF table
  remoteproc/davinci: Use %zx for formating size_t
  extcon: cht-wc: Return from default case to avoid warnings
  cfg80211: Avoid regulatory restore when COUNTRY_IE_IGNORE is set
  ALSA: seq: Do error checks at creating system ports
  ath9k: fix tx99 with monitor mode interface
  ath10k: limit available channels via DT ieee80211-freq-limit
  gfs2: Don't set GFS2_RDF_UPTODATE when the lvb is updated
  ASoC: dpcm: Properly initialise hw->rate_max
  pinctrl: ingenic: Probe driver at subsys_initcall
  MIPS: BCM47XX: Enable USB power on Netgear WNDR3400v3
  ARM: dts: exynos: Fix sound in Snow-rev5 Chromebook
  liquidio: fix race condition in instruction completion processing
  ARM: dts: exynos: Fix regulators configuration on Peach Pi/Pit Chromebooks
  i40e: use correct length for strncpy
  i40e: hold the rtnl lock on clearing interrupt scheme
  i40e: Prevent deleting MAC address from VF when set by PF
  IB/rxe: fixes for rdma read retry
  iwlwifi: don't WARN on trying to dump dead firmware
  iwlwifi: mvm: avoid sending too many BARs
  ARM: dts: pxa: fix the rtc controller
  ARM: dts: pxa: fix power i2c base address
  rtl8187: Fix warning generated when strncpy() destination length matches the 
sixe argument
  soc: imx: gpc: fix PDN delay
  ASoC: rsnd: ssi: Fix issue in dma data address assignment
  net: phy: mscc: read 'vsc8531,vddmac' as an u32
  net: phy: mscc: read 'vsc8531, edge-slowdown' as an u32
  ARM: dts: meson8: fix the clock controller register size
  ARM: dts: meson8b: fix the clock controller register size
  net: lan78xx: Bail out if lan78xx_get_endpoints fails
  ASoC: sgtl5000: avoid division by zero if lo_vag is zero
  ARM: dts: exynos: Disable pull control for S5M8767 PMIC
  ath10k: wmi: disable softirq's while calling ieee80211_rx
  IB/ipoib: Ensure that MTU isn't less than minimum permitted
  RDMA/core: Rate limit MAD error messages
  RDMA/core:

[Kernel-packages] [Bug 1852236] Re: disco/linux-aws: 5.0.0-1022.25 -proposed tracker

5.0.0-1022.25 - aws
Regression test CMPL, RTB.

Issue to note in x86_64 (aws):
  tsc - failed on i3.metal / c5.metal (bug 1851607)
  ubuntu_kernel_selftests - msg_zerocopy in net on some nodes (bug 1812620)
  ubuntu_kvm_unit_tests - vmx on i3.metal / c5.metal / r5.metal (1821394)
  ubuntu_ltp - proc01 (bug 1829849) cpuset_hotplug (bug 1834006) 
memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) 
memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) 
cpuhotplug03 on c5.metal (bug 1836167) getaddrinfo_01 (bug 1829995) 
crypto_user02 (bug 1837543) mm test failed on some instances
  ubuntu_ltp_syscalls - msgstress03 on t2.small (bug 1783881) pivot_root01 (bug 
1852966)
  ubuntu_stress_smoke_test - schedpolicy on t2.small (bug 1853944)

Skipped / blacklisted:
 * libhugetlbfs

Issue to note in arm64 (aws):
  ubuntu_kernel_selftests - msg_zerocopy in net on some nodes (bug 1812620)
  ubuntu_ltp - proc01 (bug 1829849) cpuacct_100_100 (bug 1829978) memcg_stat 
(bug 1829983) memcg_use_hierarchy (bug 1829989) getaddrinfo_01 (bug 1829995)
  ubuntu_ltp_syscalls - msgstress03 on t2.small (bug 1783881) pivot_root01 (bug 
1852966)
  ubuntu_stress_smoke_test - schedpolicy on t2.small (bug 1853944)

Skipped / blacklisted:
 * iosched_bugs
 * monotonic_time
 * tsc
 * ubuntu_32_on_64
 * libhugetlbfs
 * ubuntu_seccomp


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

** Tags added: regression-testing-passed

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

Title:
  disco/linux-aws: 5.0.0-1022.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 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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1852253
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 20. November 2019 14:18 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1852235
  variant: debs

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

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

[Kernel-packages] [Bug 1853789] Re: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel

2019-11-25 Thread Khaled El Mously

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

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

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

Title:
  Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Eoan:
  Fix Committed

Bug description:
  We enabled this driver in the linux-image-5.3.0-1013-raspi2 proposed
  kernel, then we got lots of reports from users that this driver is not
  stable, it will crash randomly, so let us disable this driver again
  and wait for the upstream branch rpi-5.3.y has the fixes for it.

  Users report crash of this driver via: #1852035 and #1850876

  This bug is for tracking the reverting the fix of #1850876.

  [Impact]
  According to the #1852035 and #1850876, users reported that the driver
  v3d will crash under desktop, then I checked the upstream kernel, the
  branch rpi-5.3.y was merged some fixes for v3d driver on Nov 11, I
  tested this branch myself, found the driver still has some problem.
  I also applied those patches to eoan kernel and built a testing
  kernel, users reported similar problems with this testing kernel.

  So the safest way is to disable this driver in the kernel agian, until
  the branch rpi-5.3.y has the fixes for this driver. Or we could
  investigate and backport fixes from rpi-4.19.y later.

  [Fix]
  Revert a patch in the 1013 kernel.

  
  [Test Case]
  Users tested 1012 kernel a lot, they didn't report the unstable issues,
  and before the 1013, this driver was always disabled.

  [Regression Risk]
  Low, just revert a new enabled driver in the 1013 kernel.

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

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

[Kernel-packages] [Bug 1852236] Re: disco/linux-aws: 5.0.0-1022.25 -proposed tracker

** 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: 1852253
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 20. November 2019 14:18 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1852235
  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/1852236

Title:
  disco/linux-aws: 5.0.0-1022.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 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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1852253
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 20. November 2019 14:18 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1852235
  variant: debs

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

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

[Kernel-packages] [Bug 1851607] Re: tsc failed on B-aws-5.0 amd64 bare metal

Found on AWS Disco instance i3.metal / c5.metal (passed on r5.metal)

** Tags added: aws disco sru-2019

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

** Summary changed:

- tsc failed on B-aws-5.0 amd64 bare metal
+ tsc failed on B-aws-5.0 / D-aws amd64 bare metal

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

Title:
  tsc failed on B-aws-5.0 / D-aws amd64 bare metal

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

Bug description:
  Issue found on AWS i3.metal bare metal node

   Running 'make '
   cc -O -Wall -Wpedantic -Werror -c -o checktsc.o checktsc.c
   cc -o checktsc checktsc.o -lpthread
   Running '/home/ubuntu/autotest/client/tmp/tsc/src/checktsc -t 650'
   Program checktsc exit status is 1
   Exception escaping from test:  
   Traceback (most recent call last):
   File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
   _call_test_function(self.execute, *p_args, **p_dargs)
   File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
   return func(*args, **dargs)
   File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
   postprocess_profiled_run, args, dargs)
   File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
   self.run_once(*args, **dargs)
   File "/home/ubuntu/autotest/client/tests/tsc/tsc.py", line 74, in run_once
   raise error.TestFail(reason)
   TestFail: Latency CPU 63 - CPU 50 = 746 exceeds threshold 650

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

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

[Kernel-packages] [Bug 1845434] Re: 5.0-based linux-oracle kernels can't run ADT

2019-11-25 Thread Launchpad Bug Tracker

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

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

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

Title:
  5.0-based linux-oracle kernels can't run ADT

Status in linux package in Ubuntu:
  Expired

Bug description:
  ADT tests cannot run on those kernels..looks like it's a CONFIG_VIRTIO
  thing?

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

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

[Kernel-packages] [Bug 1845586] Re: System can NOT be installed only if add a kernel parameter nomodeset on Eoan 19.10

2019-11-25 Thread Launchpad Bug Tracker

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

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

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

Title:
  System can NOT be installed only if add a kernel parameter nomodeset
  on Eoan 19.10

Status in linux package in Ubuntu:
  Expired

Bug description:
  [Summary]
  System can NOT be installed only if add a kernel parameter nomodeset in 
booting grub.

  [Steps to reproduce]
  1. Make a usb stick.
  2. Boot from the usb stick to install system.
  3. Check the result.
  4. Add a parameter nomodeset in boot grub if step 3 is failed.

  [Expected result]
  System can be install without any parameter.

  [Actual result]
  Need a kernel parameter system can be installed.

  [Failure rate]
  100%

  [Additional information]
  bios-version: N2EET41W (1.23 )
  GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
  01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c8c (rev a1)
  system-product-name: 20MGZ484US
  system-manufacturer: LENOVO
  kernel-version: 5.3.0-10-generic
  CPU: Intel(R) Core(TM) i5-8400H CPU @ 2.50GHz (8x)

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

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

[Kernel-packages] [Bug 1812620] Re: msg_zerocopy in net from ubuntu_kernel_selftests failed

For D-AWS , it's not failing on all nodes.
Take ARM64 instances for example, this has passed on a1.2xlarge but not 
a1.large / a1.medium

** Tags added: sru-2019

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

Title:
  msg_zerocopy in net from ubuntu_kernel_selftests failed

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

Bug description:
  This test will return 1

  $ sudo ./msg_zerocopy.sh 
  ipv4 tcp -t 1
  ./msg_zerocopy: setaffinity 2
  ./msg_zerocopy: setaffinity 3
  $ echo $?
  1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 21 07:41 seq
   crw-rw 1 root audio 116, 33 Jan 21 07:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jan 21 07:50:33 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
  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: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1847193] Re: ath10k_pci: firmware crashed randomly (Qualcomm Atheros QCA6174 )

2019-11-25 Thread Alex Tu

** Tags added: originate-from-1853938

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

Title:
  ath10k_pci: firmware crashed randomly (Qualcomm Atheros QCA6174 )

Status in OEM Priority Project:
  New
Status in linux-oem package in Ubuntu:
  New

Bug description:
  the wifi failed randomly, and it seems always happens with error message:
  " ath10k_pci :02:00.0: firmware crashed!"

  02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter [1a56:143a]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66
  ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18
  Uname: Linux 4.15.0-1057-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  8 14:52:39 2019
  InstallationDate: Installed on 2019-08-11 (57 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed-oem
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Dependencies:

  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-11 (57 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux-firmware 1.173.9
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-1057-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1852386] Re: no HDMI video output since GDM greeter after linux-oem-osp1 version 5.0.0-1026

2019-11-25 Thread Yuan-Chen Cheng

per test 5.0.0.1030.34 from the proposed chanel on a Comet Lake-S
platform, I confirm the issue is gone.

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

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

Title:
  no HDMI video output since GDM greeter after linux-oem-osp1 version
  5.0.0-1026

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

Bug description:
  [SRU Justification: oem-osp1-bionic]

  [Impact]
  Bug 1849278 introduced a regression on some Comet Lake platforms that
  device may have no video output on HDMI port.

  [Fix]
  A currently in-review patch
  https://patchwork.freedesktop.org/patch/340416 should be applied to
  correct PCH's identity and restore HDMI output.

  [Test Case]
  1. Apply the patches to oem-osp1 kernel >= 1026 or Eoan/Focal generic
  kernels.
  2. Boot affected platforms with HDMI cable connected to an external
  monitor.
  3. Check if the monitor lights up when GDM service is started.

  This was verified in to victim platforms.

  [Regression Risk]
  Low. This should affects only systems with matching PCH hw that is
  currently affected by the regression to be fixed.

  ==

  [SRU Justification: E/F/U]

  [Impact]
  Some Comet Lake platforms got i915 call trace dump due to the lake of
  support to its PCH id:

[2.999233] [ cut here ]
[2.999238] eDP powered off while attempting aux channel
communication.
[2.999338] WARNING: CPU: 2 PID: 296 at
drivers/gpu/drm/i915/display/intel_dp.c:1148
intel_dp_aux_xfer+0x767/0x900 [i915]
[2.999341] Modules linked in: i915(+) i2c_algo_bit drm_kms_helper
syscopyarea sysfillrect sysimgblt fb_sys_fops drm r8169 ahci realtek
libahci wmi video
[2.999350] CPU: 2 PID: 296 Comm: systemd-udevd Not tainted
5.3.0-997-generic #201910072204
[2.999352] Hardware name: Dell Inc. OptiPlex 3280 AIO/, BIOS
99.00.08 10/01/2019
[2.999391] RIP: 0010:intel_dp_aux_xfer+0x767/0x900 [i915]
[2.999394] Code: e8 ee b5 ff ff 84 c0 0f 85 ec f9 ff ff 48 8b 7d 80
e8 5d b6 ff ff 84 c0 0f 85 db f9 ff ff 48 c7 c7 50 22 5d c0 e8 84 ea b5
d1 <0f> 0b 48 8b 7d 80 48 8d 75 90 4c 8d ab a8 07 00 00 e8 63 b4 ff ff
[2.999398] RSP: 0018:b740b5b8 EFLAGS: 00010286
[2.999400] RAX:  RBX: 9bfa9dc2 RCX:
0396
[2.999402] RDX: 0001 RSI: 0082 RDI:
0246
[2.999404] RBP: b740b698 R08: 0396 R09:
0019
[2.999406] R10: 072e R11: b740b420 R12:
0004
[2.999408] R13: 9bfa9fbca120 R14: 9bfa9dc2 R15:
9bfa9dc207a8
[2.999410] FS:  7f0d8613a680() GS:9bfaaec8()
knlGS:
[2.999412] CS:  0010 DS:  ES:  CR0: 80050033
[2.999414] CR2: 7ffca955ae58 CR3: 00041e67e002 CR4:
003606e0
[2.999416] DR0:  DR1:  DR2:

[2.999418] DR3:  DR6: fffe0ff0 DR7:
0400
[2.999420] Call Trace:
[2.999425]  ? vprintk_default+0x29/0x50
[2.999464]  intel_dp_aux_transfer+0x15e/0x220 [i915]
[2.999472]  drm_dp_dpcd_access+0x72/0x110 [drm_kms_helper]
[2.999478]  drm_dp_dpcd_read+0x33/0xc0 [drm_kms_helper]
[2.999515]  intel_dp_read_dpcd+0x41/0x130 [i915]
[2.999551]  intel_edp_init_connector+0x136/0x540 [i915]
[2.999587]  intel_dp_init_connector+0x47f/0x870 [i915]
[2.999623]  intel_ddi_init+0x425/0x590 [i915]
[2.999660]  intel_setup_outputs+0x8e4/0xc60 [i915]

  [Fix]
  Two patches to be backported to have correct support:
  * commit 37c92dc303dd "drm/i915: Add new CNL PCH ID seen on a CML
platform" from drm-tip tree.
  * patch "https://patchwork.freedesktop.org/patch/340416;

  [Test Case]
  1. Apply the patches to oem-osp1 kernel >= 1026 or Eoan/Focal generic
  kernels.
  2. Boot affected platforms with HDMI cable connected to an external
  monitor.
  3. Check if the monitor lights up when GDM service is started.

  This was verified in to victim platforms.

  [Regression Risk]
  Low. This should affects only systems with matching PCH hw that is
  currently affected by the regression to be fixed.

  ==

[Kernel-packages] [Bug 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

This issue could be found on D-AWS bare-metal instance c5.metal

** Tags added: sru-2019

** No longer affects: linux (Ubuntu Cosmic)

** Summary changed:

- cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64
+ cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes

** Tags added: amd64

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer

[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker

** 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: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 25. November 2019 23:22 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
-   bionic/linux-azure: bug 1853900, bug 1852238
+   bionic/linux-azure: bug 1853900
  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/1853901

Title:
  disco/linux-azure: 5.0.0-1027.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  Confirmed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 25. November 2019 23:22 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-azure: bug 1853900
  variant: debs

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

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

[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed

Didn't see this on D-AWS

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

Title:
  fib related test in net from ubuntu_kernel_selftests failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Cosmic:
  Incomplete
Status in linux-kvm source package in Cosmic:
  New
Status in linux source package in Disco:
  New
Status in linux-aws source package in Disco:
  New
Status in linux-kvm source package in Disco:
  New

Bug description:
  These tests:
  * fib_tests.sh
  * fib-onlink-tests.sh
  * fib_rule_tests.sh

  All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not
  supported:

  
   selftests: net: fib_tests.sh
  
   Single path route test
   RTNETLINK answers: Operation not supported
   not ok 1..11 selftests: net: fib_tests.sh [FAIL]

   selftests: net: fib-onlink-tests.sh
  
  
   Configuring interfaces
   RTNETLINK answers: Operation not supported
   not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL]

   selftests: net: fib_rule_tests.sh
   
   RTNETLINK answers: Operation not supported
   not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL]


  (works on generic Cosmic kernel)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
  ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
  Uname: Linux 4.18.0-1006-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Jan 21 08:00:22 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1813877] Re: Can't adjust brightness on DELL UHD dGPU AIO

2019-11-25 Thread AceLan Kao

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

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

Title:
  Can't adjust brightness on DELL UHD dGPU AIO

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  [Impact]
  The dell-uart-backlight driver has been loaded, but the backlight is 
controller by graphics driver instead of scalar IC. The old way to determinate 
weather the driver should be loaded is not working anymore, since the behavior 
of scalar command, show firmware version, is not the same as old platforms.

  [Fix]
  Using more a reliable command, get_scalar_status, to check if scalar is in 
charge of the AIO backlight.
  For the old platforms which don't have the new command, I add a list to list 
them all and use the old way to determinate the scalar IC. 

  [Test]
  Verified on old and new Dell AIO platforms.

  [Regression Potential]
  Low. The quirk lists all old platforms which use the old way to check if 
scalar IC is in use. So, it won't change the behavior on old platforms, and 
apply the new method on new platforms.

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

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

[Kernel-packages] [Bug 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with D-KVM

Didn't see this with D-AWS 5.0.0-1022.25

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

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  with D-KVM

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

Bug description:
  Issue found on a AMD64 KVM node with Disco KVM kernel.

  selftests: net: test_vxlan_under_vrf.sh
  
  Error: Unknown device type.
  Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory
  Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory
  Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory
  not ok 1..24 selftests: net: test_vxlan_under_vrf.sh [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11
  ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8
  Uname: Linux 5.0.0-1010-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Mon Jul 22 05:04:42 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

apport-collect 1853927

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

Title:
  Stream Scale Time is 12% higher in 4.15.0-70.77 than 4.15.0-68.75

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a test bug to verify that we can instrument each new bug found
  in DGX-2 Performance Testing and to refine how we create and manage
  the bugs

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

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

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

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

apport-collect 1853930

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

Title:
  io RAID Read 100% Rand 128K 4 jobs depth 8 test for Config 1 shows
  -11.23 % drop in 4.15.0-70.77 than 4.15.0-68.75

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a test bug to verify that we can instrument each new bug found
  in DGX-2 Performance Testing and to refine how we create and manage
  the bugs

  summary:  - fio RAID Read 100% Rand 128K 4 jobs depth 8 test shows -11.32 
% drop in
  - 4.15.0-70.77 than 4.15.0-68.75
  + fio RAID Read 100% Rand 128K 4 jobs depth 8 test for Config 1 shows
  + -11.23 % drop in 4.15.0-70.77 than 4.15.0-68.75

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

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

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

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

apport-collect 1853928

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

Title:
  Stream Scale Rate Test shows -11.99% lower for Config 1 in
  4.15.0-70.77 than 4.15.0-68.75

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a test bug to verify that we can instrument each new bug found
  in DGX-2 Performance Testing and to refine how we create and manage
  the bugs

  summary:  - Stream Scale Rate is -11.99% lower for Config 1 in 
4.15.0-70.77 than
  - 4.15.0-68.75
  + Stream Scale Rate Test shows -11.99% lower for Config 1 in 4.15.0-70.77
  + than 4.15.0-68.75

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

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

[Kernel-packages] [Bug 1853927] [NEW] Stream Scale Time is 12% higher in 4.15.0-70.77 than 4.15.0-68.75

2019-11-25 Thread Terry Rudd

Public bug reported:

This is a test bug to verify that we can instrument each new bug found
in DGX-2 Performance Testing and to refine how we create and manage the
bugs

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

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

Title:
  Stream Scale Time is 12% higher in 4.15.0-70.77 than 4.15.0-68.75

Status in linux package in Ubuntu:
  New

Bug description:
  This is a test bug to verify that we can instrument each new bug found
  in DGX-2 Performance Testing and to refine how we create and manage
  the bugs

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

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

[Kernel-packages] [Bug 1853928] [NEW] Stream Scale Rate Test shows -11.99% lower for Config 1 in 4.15.0-70.77 than 4.15.0-68.75

2019-11-25 Thread Terry Rudd

Public bug reported:

This is a test bug to verify that we can instrument each new bug found
in DGX-2 Performance Testing and to refine how we create and manage the
bugs

summary:- Stream Scale Rate is -11.99% lower for Config 1 in 
4.15.0-70.77 than
- 4.15.0-68.75
+ Stream Scale Rate Test shows -11.99% lower for Config 1 in 4.15.0-70.77
+ than 4.15.0-68.75

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

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

Title:
  Stream Scale Rate Test shows -11.99% lower for Config 1 in
  4.15.0-70.77 than 4.15.0-68.75

Status in linux package in Ubuntu:
  New

Bug description:
  This is a test bug to verify that we can instrument each new bug found
  in DGX-2 Performance Testing and to refine how we create and manage
  the bugs

  summary:  - Stream Scale Rate is -11.99% lower for Config 1 in 
4.15.0-70.77 than
  - 4.15.0-68.75
  + Stream Scale Rate Test shows -11.99% lower for Config 1 in 4.15.0-70.77
  + than 4.15.0-68.75

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

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

[Kernel-packages] [Bug 1853930] [NEW] io RAID Read 100% Rand 128K 4 jobs depth 8 test for Config 1 shows -11.23 % drop in 4.15.0-70.77 than 4.15.0-68.75

2019-11-25 Thread Terry Rudd

Public bug reported:

This is a test bug to verify that we can instrument each new bug found
in DGX-2 Performance Testing and to refine how we create and manage the
bugs

summary:- fio RAID Read 100% Rand 128K 4 jobs depth 8 test shows -11.32 
% drop in
- 4.15.0-70.77 than 4.15.0-68.75
+ fio RAID Read 100% Rand 128K 4 jobs depth 8 test for Config 1 shows
+ -11.23 % drop in 4.15.0-70.77 than 4.15.0-68.75

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

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

Title:
  io RAID Read 100% Rand 128K 4 jobs depth 8 test for Config 1 shows
  -11.23 % drop in 4.15.0-70.77 than 4.15.0-68.75

Status in linux package in Ubuntu:
  New

Bug description:
  This is a test bug to verify that we can instrument each new bug found
  in DGX-2 Performance Testing and to refine how we create and manage
  the bugs

  summary:  - fio RAID Read 100% Rand 128K 4 jobs depth 8 test shows -11.32 
% drop in
  - 4.15.0-70.77 than 4.15.0-68.75
  + fio RAID Read 100% Rand 128K 4 jobs depth 8 test for Config 1 shows
  + -11.23 % drop in 4.15.0-70.77 than 4.15.0-68.75

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

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

[Kernel-packages] [Bug 1853694] Re: Ubuntu causing eye strain on Intel Integrated Graphics

2019-11-25 Thread hapstad

I have the same issues across OS and distros and modern hardware. It has
ruined my career and life. I have tested/ruled out all conventional
gremlins from posture to PWM. I too am convinced this is related to
dithering and since it's one thing that thus far cannot be verifiably
shut off and tested I think it's critical to be able to. PLEASE can
someone with the skills to do this work on this. I would pay for a
solution here.

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

Title:
  Ubuntu causing eye strain on Intel Integrated Graphics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find when running Ubuntu after 5-10 minutes get heavy eyes and after
  a few hours develop dizziness/headaches.

  After research online and talking with a community at LED Strain
  (https://ledstrain.org) it is believed the issue is caused by
  dithering being enabled on Ubuntu. There is no known way turn off all
  dithering by default and would like an option to turn off all
  dithering to avoid discomfort.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-36-generic 5.0.0-36.39~18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 23 12:56:12 2019
  InstallationDate: Installed on 2019-11-22 (1 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

** 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: 1852282
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 25. November 2019 12:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
-   stakeholder-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Stalled -- waiting for signoff
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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1852281

Title:
  trusty/linux-azure: 4.15.0-1064.69~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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1852282
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 25. November 2019 12:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1852238] Re: bionic/linux-azure: 5.0.0-1026.28~18.04.1 -proposed tracker

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

** This bug has been marked a duplicate of bug 1853900
   bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

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

Title:
  bionic/linux-azure: 5.0.0-1026.28~18.04.1 -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:
  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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 15. November 2019 02:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1852237
  variant: debs

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

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

[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-lrm
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** 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: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Packaging
- phase-changed: Monday, 25. November 2019 20:51 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Tuesday, 26. November 2019 00:41 UTC
  reason:
-   prepare-package: Stalled -- package tag not yet published
-   prepare-package-lrm: Stalled -- package tag not yet published
-   prepare-package-meta: Stalled -- package tag not yet published
-   prepare-package-signed: Stalled -- package tag not yet published
-   promote-to-proposed: Pending -- source package tags missing
- replaces: bug 1852238
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-azure/azure-kernel: bug 1853899
  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/1853900

Title:
  bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  Confirmed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 26. November 2019 00:41 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-azure/azure-kernel: bug 1853899
  variant: debs

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

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

[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker

** 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: Thursday, 14. November 2019 18:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1853116
disco/linux-aws: bug 1852236
-   disco/linux-azure: bug 1852239, bug 1853901
+   disco/linux-azure: bug 1853901
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
unknown/unknown: bug 1852245
  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/1852253

Title:
  disco/linux: 5.0.0-37.40 -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:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: Testing
  phase-changed: Thursday, 14. November 2019 18:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1853116
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1853901
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
unknown/unknown: bug 1852245
  variant: debs

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

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

[Kernel-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)

2019-11-25 Thread Doug Smythies

Ever since the default changed to never blanking the screen, and after I
whined in comment #18 above, I have been running this in
/etc/default/grub:

GRUB_CMDLINE_LINUX_DEFAULT=" consoleblank=300 "

always save a copy of grub first, and do "sudo update-grub afterwards",
then re-boot.

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

Title:
  Ubuntu server enables screenblanking, concealing crashdumps (DPMS is
  not used)

Status in kbd package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in kbd source package in Zesty:
  Invalid
Status in linux source package in Zesty:
  Fix Released
Status in kbd package in Debian:
  Fix Released

Bug description:
  James Rice of Jump Networks noticed that there is a screen-blanker
  enabled on Ubuntu Server.

  James notes that this blanking is not enabling DPMS power saving
  (thereby negating any power-saving benefit), and is simply turning the
  screen content blank.   This means that the crash output is invisible
  which is unhelpful on a server (virtual or otherwise).

  Ideally the screen should (at a minimum) be turned on and unblanked at
  the point of an OOPs/crash being printed.

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

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

[Kernel-packages] [Bug 1851901] Re: Touchpad doesn't work on Dell Inspiron 7000 2-in-1

2019-11-25 Thread Mirosław Marszałek

Ok I got this sorted out and turns out it was my fault. A few weeks ago,
when I was struggling to boot Ubuntu at all, I blacklisted
intel_lpss_pci. It turned out that a BIOS update fixed the boot issue
but I completely forgot about the blacklisted module... No idea why
things worked later on and then suddenly stopped but removing the
blacklist fixed everything.

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

Title:
  Touchpad doesn't work on Dell Inspiron 7000 2-in-1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run Ubuntu 19.04 on Dell inspiron 7000 2-in-1.

  After a fresh install the touchpad doesn't work, the touchscreen
  doesn't work, when the laptop doesn't recover after a suspend to RAM,
  it boots only with noapic option. The laptop is very recent, I think
  the hardware is not supported well. But I would like your advice,
  perhaps I can do something to get a working setup.

  The xinput output:

  ```
  $ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PixArt HP X500 USB Optical Mouseid=8[slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Generic Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Video Bus   id=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=9[slave  
keyboard (3)]
  ↳ Intel HID eventsid=10   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=11   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ```

  ```
  $ lspci
  00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c)
  00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
  00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 
/ 6th/7th Gen Core Processor Gaussian Mixture Model
  00:12.0 Signal processing controller: Intel Corporation Device 02f9
  00:13.0 Serial controller: Intel Corporation Device 02fc
  00:14.0 USB controller: Intel Corporation Device 02ed
  00:14.2 RAM memory: Intel Corporation Device 02ef
  00:14.3 Network controller: Intel Corporation Device 02f0
  00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8
  00:15.1 Serial bus controller [0c80]: Intel Corporation Device 02e9
  00:16.0 Communication controller: Intel Corporation Device 02e0
  00:17.0 SATA controller: Intel Corporation Device 02d3
  00:1c.0 PCI bridge: Intel Corporation Device 02bc (rev f0)
  00:1d.0 PCI bridge: Intel Corporation Device 02b4 (rev f0)
  00:1f.0 ISA bridge: Intel Corporation Device 0284
  00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8
  00:1f.4 SMBus: Intel Corporation Device 02a3
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 02a4
  01:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 2C 2018] (rev 06)
  02:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 2C 2018] (rev 06)
  02:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 2C 2018] (rev 06)
  02:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 2C 2018] (rev 06)
  03:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan 
Ridge 2C 2018] (rev 06)
  3b:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge 2C 2018] (rev 06)
  3c:00.0 Non-Volatile memory controller: Sandisk Corp Device 5004 (rev 01)
  ```

  If you need some additional information please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mviey  1561 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  9 03:26:18 2019
  InstallationDate: Installed on 2019-11-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 7391 2n1
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine:

[Kernel-packages] [Bug 1853005] Re: Wifi drops out randomly and at large bandwidth usage

2019-11-25 Thread thedoctar

It seems when I update *all* firmware, not just for my wifi card, the
issue seems to be fixed. Thanks!

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

Title:
  Wifi drops out randomly and at large bandwidth usage

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue
  Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  Problem: Wifi drops out randomly and with large bandwidth usage. For
  example, I had trouble downloading a folder from a ssh server at uni.
  During the download, the wifi stopped. In the log of journalctl
  --follow, I found many records of the kernel complaining about an
  unknown pci event, which I think is related to the wifi dropping out.
  The output of journalctl --follow during the wifi drop outs is
  attached as the file log.txt. I deleted all entries from Nautilus and
  plank.desktop.

  Additional notes: simply turning the wifi on and off again re-
  establishes the connection, but obviously irritating if I need to
  download lots of files from a ssh server. Furthermore, my iPad has
  internet connection after my Linux laptop wifi drops out, so the
  problem is not the router/ISP.

  Limiting the download speed allowed me to download from the ssh
  server. scp -r -l 100 user@address:~/Documents/Textbooks ./

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-70-generic 4.15.0-70.79
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 18 14:31:06 2019
  HibernationDevice: RESUME=UUID=9f8b6855-caac-4e96-91bd-b366050fd722
  InstallationDate: Installed on 2017-02-26 (995 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-70-generic N/A
   linux-backports-modules-4.15.0-70-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-10-06 (407 days ago)
  dmi.bios.date: 05/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.12.0
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1853915] [NEW] Bionic update: upstream stable patchset 2019-11-25

2019-11-25 Thread Kamal Mostafa

Public bug reported:

SRU Justification

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

   upstream stable patchset 2019-11-25

Ported from the following upstream stable releases:
v4.14.155, v4.19.85

   from git://git.kernel.org/

kvm: mmu: Don't read PDPTEs when paging is not enabled
KVM: x86: introduce is_pae_paging
MIPS: BCM63XX: fix switch core reset on BCM6368
scsi: core: Handle drivers which set sg_tablesize to zero
Revert "Input: synaptics-rmi4 - avoid processing unknown IRQs"
ax88172a: fix information leak on short answers
net: usb: qmi_wwan: add support for Foxconn T77W968 LTE modules
slip: Fix memory leak in slip_open error path
ALSA: usb-audio: Fix missing error check at mixer resolution test
ALSA: usb-audio: not submit urb for stopped endpoint
Input: ff-memless - kill timer in destroy()
Input: synaptics-rmi4 - fix video buffer size
Input: synaptics-rmi4 - disable the relative position IRQ in the F12 driver
Input: synaptics-rmi4 - do not consume more data than we have (F11, F12)
Input: synaptics-rmi4 - clear IRQ enables for F54
Input: synaptics-rmi4 - destroy F54 poller workqueue when removing
IB/hfi1: Ensure full Gen3 speed in a Gen4 system
i2c: acpi: Force bus speed to 400KHz if a Silead touchscreen is present
ecryptfs_lookup_interpose(): lower_dentry->d_inode is not stable
ecryptfs_lookup_interpose(): lower_dentry->d_parent is not stable either
iommu/vt-d: Fix QI_DEV_IOTLB_PFSID and QI_DEV_EIOTLB_PFSID macros
mm: memcg: switch to css_tryget() in get_mem_cgroup_from_mm()
mm: hugetlb: switch to css_tryget() in hugetlb_cgroup_charge_cgroup()
mmc: sdhci-of-at91: fix quirk2 overwrite
iio: adc: max9611: explicitly cast gain_selectors
tee: optee: take DT status property into account
ath10k: fix kernel panic by moving pci flush after napi_disable
iio: dac: mcp4922: fix error handling in mcp4922_write_raw
arm64: dts: allwinner: a64: Olinuxino: fix DRAM voltage
arm64: dts: allwinner: a64: NanoPi-A64: Fix DCDC1 voltage
ALSA: pcm: signedness bug in snd_pcm_plug_alloc()
arm64: dts: tegra210-p2180: Correct sdmmc4 vqmmc-supply
ARM: dts: at91/trivial: Fix USART1 definition for at91sam9g45
rtc: rv8803: fix the rv8803 id in the OF table
remoteproc/davinci: Use %zx for formating size_t
extcon: cht-wc: Return from default case to avoid warnings
cfg80211: Avoid regulatory restore when COUNTRY_IE_IGNORE is set
ALSA: seq: Do error checks at creating system ports
ath9k: fix tx99 with monitor mode interface
ath10k: limit available channels via DT ieee80211-freq-limit
gfs2: Don't set GFS2_RDF_UPTODATE when the lvb is updated
ASoC: dpcm: Properly initialise hw->rate_max
pinctrl: ingenic: Probe driver at subsys_initcall
MIPS: BCM47XX: Enable USB power on Netgear WNDR3400v3
ARM: dts: exynos: Fix sound in Snow-rev5 Chromebook
liquidio: fix race condition in instruction completion processing
ARM: dts: exynos: Fix regulators configuration on Peach Pi/Pit Chromebooks
i40e: use correct length for strncpy
i40e: hold the rtnl lock on clearing interrupt scheme
i40e: Prevent deleting MAC address from VF when set by PF
IB/rxe: fixes for rdma read retry
iwlwifi: don't WARN on trying to dump dead firmware
iwlwifi: mvm: avoid sending too many BARs
ARM: dts: pxa: fix the rtc controller
ARM: dts: pxa: fix power i2c base address
rtl8187: Fix warning generated when strncpy() destination length matches the 
sixe argument
soc: imx: gpc: fix PDN delay
ASoC: rsnd: ssi: Fix issue in dma data address assignment
net: phy: mscc: read 'vsc8531,vddmac' as an u32
net: phy: mscc: read 'vsc8531, edge-slowdown' as an u32
ARM: dts: meson8: fix the clock controller register size
ARM: dts: meson8b: fix the clock controller register size
net: lan78xx: Bail out if lan78xx_get_endpoints fails
ASoC: sgtl5000: avoid division by zero if lo_vag is zero
ARM: dts: exynos: Disable pull control for S5M8767 PMIC
ath10k: wmi: disable softirq's while calling ieee80211_rx
IB/ipoib: Ensure that MTU isn't less than minimum permitted
RDMA/core: Rate limit MAD error messages
RDMA/core: Follow correct unregister order between sysfs and cgroup
mips: txx9: fix iounmap related issue
ASoC: Intel: hdac_hdmi: Limit sampling rates at dai creation
of: make PowerMac cache node search conditional on CONFIG_PPC_PMAC
ARM: dts: omap3-gta04: give spi_lcd node a label so that we can overwrite in 
other DTS files
ARM: dts: omap3-gta04: fixes for tvout / venc
ARM: dts: omap3-gta04: tvout: enable as display1 alias
ARM: dts: omap3-gta04: fix touchscreen tsc2007
ARM: dts: omap3-gta04: make NAND partitions compatible with recent U-Boot
ARM: dts: omap3-gta04: keep vpll2

[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-disco

** Tags added: block-proposed

** 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: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Holding before Promote to Proposed
- phase-changed: Monday, 25. November 2019 21:12 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Monday, 25. November 2019 23:22 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait
- replaces: bug 1852239
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-azure: bug 1852238, bug 1853900
  variant: debs

** 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: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 25. November 2019 23:22 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
-   bionic/linux-azure: bug 1852238, bug 1853900
+   bionic/linux-azure: bug 1853900, bug 1852238
  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/1853901

Title:
  disco/linux-azure: 5.0.0-1027.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  Confirmed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 25. November 2019 23:22 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-azure: bug 1853900, bug 1852238
  variant: debs

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

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

[Kernel-packages] [Bug 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files

2019-11-25 Thread Colin Ian King

** Also affects: linux (Ubuntu Focal)
   Importance: Critical
 Assignee: Colin Ian King (colin-king)
   Status: Confirmed

** Also affects: linux-hwe (Ubuntu Focal)
   Importance: Undecided
   Status: Invalid

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

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

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

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

** No longer affects: linux-hwe (Ubuntu Focal)

** No longer affects: linux-hwe (Ubuntu Eoan)

** No longer affects: linux-hwe (Ubuntu Disco)

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

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

Title:
  remount of multilower moved pivoted-root overlayfs root, results in
  I/O errors on some modified files

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Bionic:
  In Progress
Status in linux source package in Disco:
  New
Status in linux source package in Eoan:
  New
Status in linux source package in Focal:
  In Progress

Bug description:
  == SRU Justification Disco, Eoan, Focal ==

  Multiple squashfs filesystems with overlayfs cause file corruption issues
  when modifying zero sized files

  == Fix ==

  The current fix is pending in
  
https://github.com/amir73il/linux/commit/b2d4f0ea5af42e16e154254de99da064f3ac551a

  == Test case ==

  With an Ubuntu ISO on the cdrom drive, use:

  #!/bin/bash -x
  mkdir -p /cdrom
  mount -t iso9660 -o ro,noatime /dev/sr0 /cdrom
  sleep 1
  mkdir -p /cow
  mount -t tmpfs -o 'rw,noatime,mode=755' tmpfs /cow
  sleep 1
  mkdir -p /cow/upper
  mkdir -p /cow/work
  modprobe -q -b overlay
  sleep 1
  modprobe -q -b loop
  sleep 1
  dev=$(losetup -f)
  mkdir -p /filesystem.squashfs
  losetup $dev /cdrom/casper/filesystem.squashfs
  mount -t squashfs -o ro,noatime $dev /filesystem.squashfs
  sleep 1

  dev=$(losetup -f)
  mkdir -p /installer.squashfs
  losetup $dev /cdrom/casper/installer.squashfs
  mount -t squashfs -o ro,noatime $dev /installer.squashfs
  sleep 1

  mkdir -p /root-tmp
  mount -t overlay -o 
'upperdir=/cow/upper,lowerdir=/installer.squashfs:/filesystem.squashfs,workdir=/cow/work'
 /cow /root-tmp

  FILE=/root-tmp/etc/.pwd.lock

  echo foo > $FILE
  cat $FILE
  sync
  #
  # dropping caches or remounting causes the bug
  #
  echo 3 > /proc/sys/vm/drop_caches
  cat $FILE

  Without the fix the cat of the file will produce an error. With the
  the cat will work correctly.

  == Regression Potential ==

  There is an unhandled corner case:
  - two filesystems, A and B, both have null uuid
  - upper layer is on A
  - lower layer 1 is also on A
  - lower layer 2 is on B

  However, since this is an issue without the fix and will be addressed
  later with subsequent fixes once they are OK with upstream I think the
  risk is minimal considering nobody is complaining about these corner
  cases with the current broken overlayfs squashfs layering.

  ---

  1) Download focal subiquity pending image, or eoan release image
  2) boot, and press ESC and edit boot command line (F6 in bios, e in UEFI)
  3) After --- insert the following options

     break=top debug init=/bin/bash

  4) Continue boot (Enter in BIOS, ctrl+x in UEFI)
  5) in the initramfs execute:

  rm /scripts/casper-bottom/25adduser
  exit

  6) you will be dropped into pivoted root filesystem, before systemd is execed 
as pid one
  7) /run/initramfs/ will contain a debug log, showing how everything was 
mounted. Ie. cdrom mounted, squashfs losetup from there, then multilower 
overlay setup from them, moved to /root, and then pivot-root to /root done to 
finally end up as /. Underlying layers are moved into /cow for your convenience.

  8) At this point modifying zero-byte length files, that exist in the
  lowest layer, but not the middle one, in certain ways, will results in
  them to be corrupted, after / is remounted.

  9) Corruption examples

  (On both focal & eoan)

  cat /etc/.pwd.lock
  systemd-sysusers
  cat /etc/.pwd.lock
  mount -o remount /
  cat /etc/.pwd.lock
  overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000)
  cat: /etc/.pwd.lock: Input/output error

  (Only on eoan)

  cat /etc/machine-id
  systemd-machine-id-setup
  cat /etc/machine-id
  mount -o remount /
  cat /etc/machine-id
  overlayfs: invalid origin (etc/machine-id, ftype=8000, origin ftype=4000)
  cat: /etc/machine-id: Input/output error

  Lots of things break once machine-id and .pwd.lock are corrupted. I.e.
  unable to dhcp, connect to dbus, add/remove/change

[Kernel-packages] [Bug 1852239] Re: disco/linux-azure: 5.0.0-1026.28 -proposed tracker

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

** This bug has been marked a duplicate of bug 1853901
   disco/linux-azure: 5.0.0-1027.29 -proposed tracker

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

Title:
  disco/linux-azure: 5.0.0-1026.28 -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:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 14. November 2019 22:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1852238
  variant: debs

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

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

[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

** 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 --
  kernel-stable-master-bug: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:51 UTC
  reason:
prepare-package: Stalled -- package tag not yet published
prepare-package-lrm: Stalled -- package tag not yet published
prepare-package-meta: Stalled -- package tag not yet published
prepare-package-signed: Stalled -- package tag not yet published
-   promote-to-proposed: Pending -- builds not complete in ppa 
lrm:building,signed:queued
+   promote-to-proposed: Pending -- source package tags missing
  replaces: bug 1852238
  trackers:
bionic/linux-azure/azure-kernel: bug 1853899
  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/1853900

Title:
  bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:51 UTC
  reason:
prepare-package: Stalled -- package tag not yet published
prepare-package-lrm: Stalled -- package tag not yet published
prepare-package-meta: Stalled -- package tag not yet published
prepare-package-signed: Stalled -- package tag not yet published
promote-to-proposed: Pending -- source package tags missing
  replaces: bug 1852238
  trackers:
bionic/linux-azure/azure-kernel: bug 1853899
  variant: debs

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

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

[Kernel-packages] [Bug 1853005] Re: Wifi drops out randomly and at large bandwidth usage

2019-11-25 Thread thedoctar

I updated the firmware via the instructions here:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/firmware

It didn't help. I looked at journalctl --follow and dmesg before and
after the connections drops when downloading the large file, and no
error messages appear.

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

Title:
  Wifi drops out randomly and at large bandwidth usage

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue
  Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  Problem: Wifi drops out randomly and with large bandwidth usage. For
  example, I had trouble downloading a folder from a ssh server at uni.
  During the download, the wifi stopped. In the log of journalctl
  --follow, I found many records of the kernel complaining about an
  unknown pci event, which I think is related to the wifi dropping out.
  The output of journalctl --follow during the wifi drop outs is
  attached as the file log.txt. I deleted all entries from Nautilus and
  plank.desktop.

  Additional notes: simply turning the wifi on and off again re-
  establishes the connection, but obviously irritating if I need to
  download lots of files from a ssh server. Furthermore, my iPad has
  internet connection after my Linux laptop wifi drops out, so the
  problem is not the router/ISP.

  Limiting the download speed allowed me to download from the ssh
  server. scp -r -l 100 user@address:~/Documents/Textbooks ./

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-70-generic 4.15.0-70.79
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 18 14:31:06 2019
  HibernationDevice: RESUME=UUID=9f8b6855-caac-4e96-91bd-b366050fd722
  InstallationDate: Installed on 2017-02-26 (995 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-70-generic N/A
   linux-backports-modules-4.15.0-70-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-10-06 (407 days ago)
  dmi.bios.date: 05/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.12.0
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

** 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 --
  kernel-stable-master-bug: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:51 UTC
  reason:
prepare-package: Stalled -- package tag not yet published
prepare-package-lrm: Stalled -- package tag not yet published
prepare-package-meta: Stalled -- package tag not yet published
prepare-package-signed: Stalled -- package tag not yet published
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
+   promote-to-proposed: Pending -- builds not complete in ppa 
lrm:building,signed:queued
  replaces: bug 1852238
  trackers:
bionic/linux-azure/azure-kernel: bug 1853899
  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/1853900

Title:
  bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:51 UTC
  reason:
prepare-package: Stalled -- package tag not yet published
prepare-package-lrm: Stalled -- package tag not yet published
prepare-package-meta: Stalled -- package tag not yet published
prepare-package-signed: Stalled -- package tag not yet published
promote-to-proposed: Pending -- builds not complete in ppa 
lrm:building,signed:queued
  replaces: bug 1852238
  trackers:
bionic/linux-azure/azure-kernel: bug 1853899
  variant: debs

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

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

[Kernel-packages] [Bug 1851901] Re: Touchpad doesn't work on Dell Inspiron 7000 2-in-1

2019-11-25 Thread Mirosław Marszałek

Unfortunately neither of those works for me.

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

Title:
  Touchpad doesn't work on Dell Inspiron 7000 2-in-1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run Ubuntu 19.04 on Dell inspiron 7000 2-in-1.

  After a fresh install the touchpad doesn't work, the touchscreen
  doesn't work, when the laptop doesn't recover after a suspend to RAM,
  it boots only with noapic option. The laptop is very recent, I think
  the hardware is not supported well. But I would like your advice,
  perhaps I can do something to get a working setup.

  The xinput output:

  ```
  $ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PixArt HP X500 USB Optical Mouseid=8[slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Generic Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Video Bus   id=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=9[slave  
keyboard (3)]
  ↳ Intel HID eventsid=10   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=11   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ```

  ```
  $ lspci
  00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c)
  00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
  00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 
/ 6th/7th Gen Core Processor Gaussian Mixture Model
  00:12.0 Signal processing controller: Intel Corporation Device 02f9
  00:13.0 Serial controller: Intel Corporation Device 02fc
  00:14.0 USB controller: Intel Corporation Device 02ed
  00:14.2 RAM memory: Intel Corporation Device 02ef
  00:14.3 Network controller: Intel Corporation Device 02f0
  00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8
  00:15.1 Serial bus controller [0c80]: Intel Corporation Device 02e9
  00:16.0 Communication controller: Intel Corporation Device 02e0
  00:17.0 SATA controller: Intel Corporation Device 02d3
  00:1c.0 PCI bridge: Intel Corporation Device 02bc (rev f0)
  00:1d.0 PCI bridge: Intel Corporation Device 02b4 (rev f0)
  00:1f.0 ISA bridge: Intel Corporation Device 0284
  00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8
  00:1f.4 SMBus: Intel Corporation Device 02a3
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 02a4
  01:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 2C 2018] (rev 06)
  02:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 2C 2018] (rev 06)
  02:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 2C 2018] (rev 06)
  02:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 2C 2018] (rev 06)
  03:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan 
Ridge 2C 2018] (rev 06)
  3b:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge 2C 2018] (rev 06)
  3c:00.0 Non-Volatile memory controller: Sandisk Corp Device 5004 (rev 01)
  ```

  If you need some additional information please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mviey  1561 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  9 03:26:18 2019
  InstallationDate: Installed on 2019-11-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 7391 2n1
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash noapic
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably

[Kernel-packages] [Bug 1853881] Re: Xenial update: 4.4.203 upstream stable release

2019-11-25 Thread Connor Kuehl

The following patch required offset adjustments:

x86/atomic: Fix smp_mb__{before,after}_atomic() 
- the changes to smp_mb__before_atomic and smp_mb__after_atomic had to be 
manually placed

The following patches were skipped since they have already been applied:

apparmor: fix uninitialized lsm_audit member
- Skipped as an equivalent patch has already been applied and it looks invasive 
to shape it into the stable version

apparmor: fix update the mtime of the profile file on replacement   
- Skipped as an equivalent patch has already been applied and it would be quite 
invasive to revert

apparmor: fix module parameters can be changed after policy is locked   
- Skipped as an equivalent patch has already been applied and it would be too 
invasive to revert and apply this.


** 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:
+ * slip: Fix memory leak in slip_open error path
+ * ax88172a: fix information leak on short answers
+ * ALSA: usb-audio: Fix missing error check at mixer resolution test
+ * ALSA: usb-audio: not submit urb for stopped endpoint
+ * Input: ff-memless - kill timer in destroy()
+ * ecryptfs_lookup_interpose(): lower_dentry->d_inode is not stable
+ * ecryptfs_lookup_interpose(): lower_dentry->d_parent is not stable either
+ * iommu/vt-d: Fix QI_DEV_IOTLB_PFSID and QI_DEV_EIOTLB_PFSID macros
+ * mm: memcg: switch to css_tryget() in get_mem_cgroup_from_mm()
+ * mm: hugetlb: switch to css_tryget() in hugetlb_cgroup_charge_cgroup()
+ * mmc: sdhci-of-at91: fix quirk2 overwrite
+ * iio: dac: mcp4922: fix error handling in mcp4922_write_raw
+ * ALSA: pcm: signedness bug in snd_pcm_plug_alloc()
+ * ARM: dts: at91/trivial: Fix USART1 definition for at91sam9g45
+ * ALSA: seq: Do error checks at creating system ports
+ * gfs2: Don't set GFS2_RDF_UPTODATE when the lvb is updated
+ * ASoC: dpcm: Properly initialise hw->rate_max
+ * MIPS: BCM47XX: Enable USB power on Netgear WNDR3400v3
+ * ARM: dts: exynos: Fix sound in Snow-rev5 Chromebook
+ * i40e: use correct length for strncpy
+ * i40e: hold the rtnl lock on clearing interrupt scheme
+ * i40e: Prevent deleting MAC address from VF when set by PF
+ * ARM: dts: pxa: fix power i2c base address
+ * rtl8187: Fix warning generated when strncpy() destination length matches 
the sixe argument
+ * net: lan78xx: Bail out if lan78xx_get_endpoints fails
+ * ASoC: sgtl5000: avoid division by zero if lo_vag is zero
+ * ath10k: wmi: disable softirq's while calling ieee80211_rx
+ * mips: txx9: fix iounmap related issue
+ * of: make PowerMac cache node search conditional on CONFIG_PPC_PMAC
+ * ARM: dts: omap3-gta04: give spi_lcd node a label so that we can overwrite 
in other DTS files
+ * ARM: dts: omap3-gta04: tvout: enable as display1 alias
+ * ARM: dts: omap3-gta04: make NAND partitions compatible with recent U-Boot
+ * ARM: dts: omap3-gta04: keep vpll2 always on
+ * dmaengine: dma-jz4780: Further residue status fix
+ * signal: Always ignore SIGKILL and SIGSTOP sent to the global init
+ * signal: Properly deliver SIGILL from uprobes
+ * signal: Properly deliver SIGSEGV from x86 uprobes
+ * scsi: sym53c8xx: fix NULL pointer dereference panic in sym_int_sir()
+ * ARM: imx6: register pm_power_off handler if "fsl,pmic-stby-poweroff" is set
+ * scsi: pm80xx: Corrected dma_unmap_sg() parameter
+ * scsi: pm80xx: Fixed system hang issue during kexec boot
+ * kprobes: Don't call BUG_ON() if there is a kprobe in use on free list
+ * nvmem: core: return error code instead of NULL from nvmem_device_get
+ * media: fix: media: pci: meye: validate offset to avoid arbitrary access
+ * ALSA: intel8x0m: Register irq handler after register initializations
+ * pinctrl: at91-pio4: fix has_config check in atmel_pctl_dt_subnode_to_map()
+ * llc: avoid blocking in

[Kernel-packages] [Bug 1853005] Re: Wifi drops out randomly and at large bandwidth usage

2019-11-25 Thread thedoctar

** Summary changed:

- Wifi drops out at large bandwidth usage
+ Wifi drops out randomly and at large bandwidth usage

** Description changed:

System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue Nov
12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

- Problem: Wifi drops out with large bandwidth usage. For example, I had
- trouble downloading a folder from a ssh server at uni. During the
- download, the wifi stopped. In the log of journalctl --follow, I found
- many records of the kernel complaining about an unknown pci event, which
- I think is related to the wifi dropping out. The output of journalctl
- --follow during the wifi drop outs is attached as the file log.txt. I
- deleted all entries from Nautilus and plank.desktop.
+ Problem: Wifi drops out randomly and with large bandwidth usage. For
+ example, I had trouble downloading a folder from a ssh server at uni.
+ During the download, the wifi stopped. In the log of journalctl
+ --follow, I found many records of the kernel complaining about an
+ unknown pci event, which I think is related to the wifi dropping out.
+ The output of journalctl --follow during the wifi drop outs is attached
+ as the file log.txt. I deleted all entries from Nautilus and
+ plank.desktop.

Additional notes: simply turning the wifi on and off again re-
establishes the connection, but obviously irritating if I need to
download lots of files from a ssh server. Furthermore, my iPad has
internet connection after my Linux laptop wifi drops out, so the problem
is not the router/ISP.

Limiting the download speed allowed me to download from the ssh server.
scp -r -l 100 user@address:~/Documents/Textbooks ./

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-70-generic 4.15.0-70.79
ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
Uname: Linux 4.15.0-70-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: albert 2011 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 18 14:31:06 2019
HibernationDevice: RESUME=UUID=9f8b6855-caac-4e96-91bd-b366050fd722
InstallationDate: Installed on 2017-02-26 (995 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc.
Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-70-generic N/A
linux-backports-modules-4.15.0-70-generic N/A
linux-firmware 1.173.12
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-10-06 (407 days ago)
dmi.bios.date: 05/26/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.12.0
dmi.board.name: 0T3FTF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.

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

Title:
Wifi drops out randomly and at large bandwidth usage

Status in linux package in Ubuntu:
Confirmed

Bug description:
System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue
Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Problem: Wifi drops out randomly and with large bandwidth usage. For
example, I had trouble downloading a folder from a ssh server at uni.
During the download, the wifi stopped. In the log of journalctl
--follow, I found many records of the kernel complaining about an
unknown pci event, which I think is related to the wifi dropping out.
The output of journalctl --follow during the wifi drop outs is
attached as the file log.txt. I deleted all entries from Nautilus and
plank.desktop.

Limiting the download speed allowed me to download from the ssh
server. scp -r -l 100 user@address:~/Documents/Textbooks ./

ProblemType: Bug
DistroRelease: Ubuntu 18.04

[Kernel-packages] [Bug 1845704] Re: HDMI monitor is not detected as sound output device starting from kernel 4.18.0-21 and above, Ubuntu 18.10 and 19.04

2019-11-25 Thread Oleksandr

Hi Kai-Heng,

Sorry, I don't know how to build kernels from commit, and didn't have time to 
play with that.
Today I installed 5.0.0-15-generic, and system is able to see my HDMI sound 
output device. Found this solution here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771

Do you still need to test those commits? If yes, could you please add
steps on how to build them or build them for me, so I can install them?
I can also follow bug #1834771.

Thanks!

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

Title:
  HDMI monitor is not detected as sound output device starting from
  kernel 4.18.0-21 and above, Ubuntu 18.10 and 19.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu 18.10 from kernel 4.18.0-20-generic to
  4.18.0-21-generic, HDMI Audio stopped working, system does not detect
  it at all as a sound output device. Downgrading to 4.18.0-20 helped on
  Ubuntu 18.10, but currently I'm using Ubuntu 19.04 with kernel
  5.0.0-29-generic, and HDMI sound still does not work and system cannot
  detect it.

  Adding the following parameters to GRUB didn't helped ():
  - amdgpu.dc=1
  - radeon.audio=1

  Video card: Radeon HD 4850 with 2 DVI ports with ability to output
  sound thru DVI (DVI-HDMI cable or DVI-HDMI adapter).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-29-generic 5.0.0-29.31
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oshmyrko   2595 F pulseaudio
   /dev/snd/controlC2:  oshmyrko   2595 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 22:14:27 2019
  InstallationDate: Installed on 2019-04-13 (166 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=a88b1763-5d14-4204-ba95-d6718c22158d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-07-09 (80 days ago)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx: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: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker

** 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 --
  kernel-stable-master-bug: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 25. November 2019 21:12 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait
  replaces: bug 1852239
  trackers:
bionic/linux-azure: bug 1852238, bug 1853900
  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/1853901

Title:
  disco/linux-azure: 5.0.0-1027.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 25. November 2019 21:12 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait
  replaces: bug 1852239
  trackers:
bionic/linux-azure: bug 1852238, bug 1853900
  variant: debs

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

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

[Kernel-packages] [Bug 1853762] Re: Headphones stop working until pairing again

2019-11-25 Thread Guillaume Michaud

** Attachment added: "system.journal"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+attachment/5307827/+files/system.journal

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

Title:
  Headphones stop working until pairing again

Status in bluez package in Ubuntu:
  New

Bug description:
  I'm using Marshall MID ANC headphones with Ubuntu 19.10.
  Every now and then, I won't be able to use them without re-pairing first 
(like today - see logs).
  After re-pairing, everything works again for a while : I can switch off and 
on the headphones, reboot... Until it breaks again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 24 19:13:40 2019
  InstallationDate: Installed on 2018-07-28 (483 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:AB:C5:7E:41:26  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:319948 acl:71 sco:0 events:45583 errors:0
TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0

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

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

[Kernel-packages] [Bug 1853762] Re: Headphones stop working until pairing again

2019-11-25 Thread Guillaume Michaud

I'm adding system.journal and user-1000.journal to this bug report.
Today (November 25th) at :
- 20:47 : I switched the headphones on... which didn't connect
- 20:48 : I tried to connect manually using UI (but the switch/toggle 
immediately came back to "off")
- 20:49-50 : I used bluetoothctl, which worked
- 20:51 : I used bluetootctl to disconnect the headphones, and tried to connect 
them back with UI (which didn't work)

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

Title:
  Headphones stop working until pairing again

Status in bluez package in Ubuntu:
  New

Bug description:
  I'm using Marshall MID ANC headphones with Ubuntu 19.10.
  Every now and then, I won't be able to use them without re-pairing first 
(like today - see logs).
  After re-pairing, everything works again for a while : I can switch off and 
on the headphones, reboot... Until it breaks again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 24 19:13:40 2019
  InstallationDate: Installed on 2018-07-28 (483 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:AB:C5:7E:41:26  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:319948 acl:71 sco:0 events:45583 errors:0
TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0

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

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

[Kernel-packages] [Bug 1853762] Re: Headphones stop working until pairing again

2019-11-25 Thread Guillaume Michaud

** Attachment added: "user-1000.journal"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+attachment/5307828/+files/user-1000.journal

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

Title:
  Headphones stop working until pairing again

Status in bluez package in Ubuntu:
  New

Bug description:
  I'm using Marshall MID ANC headphones with Ubuntu 19.10.
  Every now and then, I won't be able to use them without re-pairing first 
(like today - see logs).
  After re-pairing, everything works again for a while : I can switch off and 
on the headphones, reboot... Until it breaks again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 24 19:13:40 2019
  InstallationDate: Installed on 2018-07-28 (483 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:AB:C5:7E:41:26  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:319948 acl:71 sco:0 events:45583 errors:0
TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0

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

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

[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-lrm
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Committed

** 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 --
  kernel-stable-master-bug: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:51 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-lrm: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   prepare-package: Stalled -- package tag not yet published
+   prepare-package-lrm: Stalled -- package tag not yet published
+   prepare-package-meta: Stalled -- package tag not yet published
+   prepare-package-signed: Stalled -- package tag not yet published
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
  replaces: bug 1852238
  trackers:
bionic/linux-azure/azure-kernel: bug 1853899
  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/1853900

Title:
  bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:51 UTC
  reason:
prepare-package: Stalled -- package tag not yet published
prepare-package-lrm: Stalled -- package tag not yet published
prepare-package-meta: Stalled -- package tag not yet published
prepare-package-signed: Stalled -- package tag not yet published
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
  replaces: bug 1852238
  trackers:
bionic/linux-azure/azure-kernel: bug 1853899
  variant: debs

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

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

[Kernel-packages] [Bug 1852406] Re: Double-escape in initramfs DECRYPT_CMD

2019-11-25 Thread Colin Ian King

Thanks Witold! Much appreciated.

** Tags added: verification-done verification-done-eoan

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

Title:
  Double-escape in initramfs DECRYPT_CMD

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Eoan:
  Fix Committed
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  == SRU Justification, Eoan ==

  initramfs/scripts/zfs.in incorrectly quotes ${ENCRYPTIONROOT} on line
  414:

  DECRYPT_CMD="${ZFS} load-key '${ENCRYPTIONROOT}'"

  This is OK when the line is executed by shell, such as in line 430 or
  436, but when plymouth is used it results in plymouth executing "zfs
  load-key 'rpool'" - and zfs  is unable to find pool called "'rpool'".

  If I understand
  https://docs.oracle.com/cd/E23824_01/html/821-1448/gbcpt.html
  correctly zfs pool name is always 'shell-friendly', so removing the
  quotation marks would be a proper fix for that.

  == Fix ==

  One line fix as attached in https://bugs.launchpad.net/ubuntu/+source
  /zfs-linux/+bug/1852406/comments/1

  == Test ==

  Boot with encrypted data set with plymouth. Without the fix zfs is
  unable to find the root encrypted pool. With the fix this works.

  == Regression Potential ==

  This just affects the encrypted dataset that holds key for root
  dataset; currently this is causing issues because of the bug, so the
  risk of the fix outweighs the current situation where this is
  currently broken.

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

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

[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Fix Committed => 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 --
  kernel-stable-master-bug: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Packaging
- phase-changed: Monday, 25. November 2019 20:05 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Monday, 25. November 2019 21:12 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
  replaces: bug 1852239
  trackers:
-   bionic/linux-azure: bug 1853900, bug 1852238
+   bionic/linux-azure: bug 1852238, bug 1853900
  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/1853901

Title:
  disco/linux-azure: 5.0.0-1027.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 25. November 2019 21:12 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
  replaces: bug 1852239
  trackers:
bionic/linux-azure: bug 1852238, bug 1853900
  variant: debs

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

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

[Kernel-packages] [Bug 1847948] Comment bridged from LTC Bugzilla

2019-11-25 Thread bugproxy

--- Comment From mu...@br.ibm.com 2019-11-25 16:06 EDT---
Apologies for the delay, just tested with the 1:2.11+dfsg-1ubuntu7.21 release 
and the performance numbers are good in it:

# fio --direct=1 --rw=randrw --refill_buffers --norandommap
--randrepeat=0 --ioengine=libaio --bs=4k --rwmixread=100 --iodepth=16
--runtime=60 --name=job1 --filename=/dev/nvme0n1 --numjobs=4

READ: bw=1216MiB/s (1275MB/s), 300MiB/s-315MiB/s (314MB/s-330MB/s),
io=71.3GiB (76.5GB), run=60001-60002msec

# fio --direct=1 --rw=randrw --refill_buffers --norandommap
--randrepeat=0 --ioengine=libaio --bs=4k --rwmixread=100 --iodepth=16
--runtime=60 --name=job1 --filename=/dev/nvme0n1 --numjobs=64

READ: bw=4081MiB/s (4280MB/s), 58.3MiB/s-69.8MiB/s (61.1MB/s-73.1MB/s),
io=239GiB (257GB), run=60001-60011msec

The same note as before applies that I am using the patched custom
kernel mentioned in previous comments.

$ dpkg -l | grep 1:2.11+dfsg-1ubuntu7.21
ii  qemu   1:2.11+dfsg-1ubuntu7.21  
  ppc64el  fast processor emulator
ii  qemu-block-extra:ppc64el   1:2.11+dfsg-1ubuntu7.21  
  ppc64el  extra block backend modules for qemu-system and 
qemu-utils
ii  qemu-kvm   1:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU Full virtualization on x86 hardware
ii  qemu-system1:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU full system emulation binaries
ii  qemu-system-arm1:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU full system emulation binaries (arm)
ii  qemu-system-common 1:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU full system emulation binaries (common files)
ii  qemu-system-mips   1:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU full system emulation binaries (mips)
ii  qemu-system-misc   1:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU full system emulation binaries (miscellaneous)
ii  qemu-system-ppc1:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU full system emulation binaries (ppc)
ii  qemu-system-s390x  1:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU full system emulation binaries (s390x)
ii  qemu-system-sparc  1:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU full system emulation binaries (sparc)
ii  qemu-system-x861:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU full system emulation binaries (x86)
ii  qemu-user  1:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU user mode emulation binaries
ii  qemu-user-binfmt   1:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU user mode binfmt registration for qemu-user
ii  qemu-utils 1:2.11+dfsg-1ubuntu7.21  
  ppc64el  QEMU utilities

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

Title:
  Improve NVMe guest performance on Bionic QEMU

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in qemu source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO.
     But there can be platforms (like ppc64 spapr) that can and want to do
     exactly that.

   * Backport two patches from upstream (in since qemu 2.12 / Disco).

   * Due to that there is a tremendous speedup, especially useful with page
     size bigger than 4k. This avoids that being split into chunks and makes
     direct MMIO access possible for the guest.

  [Test Case]

   * On ppc64 pass through an NVME device to the guest and run I/O
     benchmarks, see below for Details how to set that up.
     Note: this needs the HWE kernel or another kernel fixup for [1].
 Note: the test should also be done with the non-HWE kernel, the 
 expectation there is that it would not show the perf benefits, but 
 still work fine

  [Regression Potential]

   * Changes:
     a) if the host driver allows mapping of MSI-X data the entire BAR is
    mapped. This is only done if the kernel reports that capability [1].
    This ensures that only on kernels able to do so qemu does expose the
    new behavior (safe against regression in that regard)
     b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local
    to just this HW and will not affect other HW.

[Kernel-packages] [Bug 1852406] Re: Double-escape in initramfs DECRYPT_CMD

2019-11-25 Thread Witold Krecicki

@colin-king I got it (0.8.1-1ubuntu14.2) from eoan-proposed, and yes -
this version fixes the issue.

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

Title:
  Double-escape in initramfs DECRYPT_CMD

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Eoan:
  Fix Committed
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  == SRU Justification, Eoan ==

  initramfs/scripts/zfs.in incorrectly quotes ${ENCRYPTIONROOT} on line
  414:

  DECRYPT_CMD="${ZFS} load-key '${ENCRYPTIONROOT}'"

  This is OK when the line is executed by shell, such as in line 430 or
  436, but when plymouth is used it results in plymouth executing "zfs
  load-key 'rpool'" - and zfs  is unable to find pool called "'rpool'".

  If I understand
  https://docs.oracle.com/cd/E23824_01/html/821-1448/gbcpt.html
  correctly zfs pool name is always 'shell-friendly', so removing the
  quotation marks would be a proper fix for that.

  == Fix ==

  One line fix as attached in https://bugs.launchpad.net/ubuntu/+source
  /zfs-linux/+bug/1852406/comments/1

  == Test ==

  Boot with encrypted data set with plymouth. Without the fix zfs is
  unable to find the root encrypted pool. With the fix this works.

  == Regression Potential ==

  This just affects the encrypted dataset that holds key for root
  dataset; currently this is causing issues because of the bug, so the
  risk of the fix outweighs the current situation where this is
  currently broken.

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

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

[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

** 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 --
  kernel-stable-master-bug: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Holding before Packaging
- phase-changed: Monday, 25. November 2019 20:01 UTC
+ phase: Packaging
+ phase-changed: Monday, 25. November 2019 20:51 UTC
  reason:
-   prepare-package: Holding -- waiting for master bug
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-lrm: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1852238
  trackers:
bionic/linux-azure/azure-kernel: bug 1853899
  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/1853900

Title:
  bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:51 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1852238
  trackers:
bionic/linux-azure/azure-kernel: bug 1853899
  variant: debs

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

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

[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

** Summary changed:

- bionic/linux-azure:  -proposed tracker
+ bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

** Changed in: kernel-sru-workflow/prepare-package-lrm
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-lrm
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

Title:
  bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:51 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1852238
  trackers:
bionic/linux-azure/azure-kernel: bug 1853899
  variant: debs

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

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

[Kernel-packages] [Bug 1777586] Re: Ubuntu Server 18.04 LTS aacraid error

2019-11-25 Thread Simone Lazzaris

I also have this issue triggered on my system. Is there a fix in the
ubuntu-provided kernel yet?

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

Title:
  Ubuntu Server 18.04 LTS aacraid error

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

Bug description:
  I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and
  am now running into these raid adapter driver errors.   The server ran
  fine in older version.  My apologies as I lost the exact version, but
  it never had any errors like this version.

  Now when ever I try to copy files to the RAID 5 drive, or untar a
  file, I get these errors now after a few MB's of written data.

  Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

  batboat:/var/log$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  I have tried the IRQ debugging tips to no avail.   I loaded in
  Debian9.4.0 and it only briefly showed this error once.   But appears
  to be much more resilient and appears to work fine.


  Jun 19 00:02:21 batboat kernel: [  498.770839] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.139167] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.795083] aacraid :03:09.0: Adapter 
health - 199
  Jun 19 00:02:37 batboat kernel: [  514.800376] aacraid :03:09.0: 
outstanding cmd: midlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800378] aacraid :03:09.0: 
outstanding cmd: lowlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800381] aacraid :03:09.0: 
outstanding cmd: error handler-0
  Jun 19 00:02:37 batboat kernel: [  514.800383] aacraid :03:09.0: 
outstanding cmd: firmware-5
  Jun 19 00:02:37 batboat kernel: [  514.800385] aacraid :03:09.0: 
outstanding cmd: kernel-0
  Jun 19 00:02:37 batboat kernel: [  514.800391] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800394] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800396] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800399] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800401] sd 4:0:0:0: Device offlined - 
not ready after error recovery

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

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

[Kernel-packages] [Bug 1852581] Re: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO

2019-11-25 Thread Vladimir Schuka

Hello, I have HP x360
The same situation that laptop does not boot with kernel 5.3.0-23 with error

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

Title:
  hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-hwe-edge source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-hwe-edge source package in Eoan:
  Invalid

Bug description:
  SRU Justification

  Impact: The fix for bug 1850234 does not function as intended in
  bionic, as a result of modinfo not knowing about module signatures.
  This results in no modules being signed in hwe kernels based on 5.3,
  rendering systems with secure boot enabled unbootable.

  Fix: Check for the module signature at the end of modules instead of
  relying on modinfo. This can be done without any external tools
  needing to be aware of module signatures.

  Test Case: Check that all built modules contain signatures, except for
  those in staging which have not been whitelisted.

  Regression Potential: I can think of two possible regression
  situations. We could regress to the behavior prior to the fix for bug
  1850234, or the eoan 5.3 kernel could also end up with all modules
  unsigned. I've done test builds of both the eoan 5.3 kernel and the
  bionic 5.3 hwe-edge kernel with this patch and checked that the
  results are as intended. We should also check this again once new
  kernels have been built, before copying them out to -proposed.

  ---

  The latest hwe-edge kernel 5.3.0-23.25 fails to boot with the message
  that it cannot find the UUID associated with the root partition. The
  user gets dropped to a busybox shell with an initramfs prompt. The
  standard hwe kernel does not have this issue and the last hwe-edge
  kernel that does work is 5.3.0-19.20.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic-hwe-18.04-edge 5.3.0.23.90
  ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 14 08:19:57 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-09-01 (73 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker

** 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 --
  kernel-stable-master-bug: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:05 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1852239
  trackers:
-   bionic/linux-azure: bug 1852238, bug 1853900
+   bionic/linux-azure: bug 1853900, bug 1852238
  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/1853901

Title:
  disco/linux-azure: 5.0.0-1027.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:05 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1852239
  trackers:
bionic/linux-azure: bug 1853900, bug 1852238
  variant: debs

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

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

[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker

** 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: Thursday, 14. November 2019 18:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1853116
disco/linux-aws: bug 1852236
-   disco/linux-azure: bug 1852239
+   disco/linux-azure: bug 1852239, bug 1853901
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
unknown/unknown: bug 1852245
  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/1852253

Title:
  disco/linux: 5.0.0-37.40 -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:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: Testing
  phase-changed: Thursday, 14. November 2019 18:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1853116
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239, bug 1853901
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
unknown/unknown: bug 1852245
  variant: debs

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

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

[Kernel-packages] [Bug 1852238] Re: bionic/linux-azure: 5.0.0-1026.28~18.04.1 -proposed tracker

** 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: 1852239
+ kernel-stable-master-bug: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 15. November 2019 02:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1852237
  variant: debs

** Tags removed: kernel-sru-backport-of-1852239

** Tags added: kernel-sru-backport-of-1853901

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

Title:
  bionic/linux-azure: 5.0.0-1026.28~18.04.1 -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:
  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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 15. November 2019 02:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1852237
  variant: debs

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

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

[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: -proposed tracker

** Summary changed:

- linux-azure:  -proposed tracker
+ bionic/linux-azure:  -proposed tracker

** 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 --
  kernel-stable-master-bug: 1853901
+ packages:
+   lrm: linux-restricted-modules-azure
+   main: linux-azure
+   meta: linux-meta-azure
+   signed: linux-signed-azure
+ phase: Holding before Packaging
+ phase-changed: Monday, 25. November 2019 20:01 UTC
+ reason:
+   prepare-package: Holding -- waiting for master bug
  replaces: bug 1852238
+ trackers:
+   bionic/linux-azure/azure-kernel: bug 1853899
  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/1853900

Title:
  bionic/linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-lrm series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1853901
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Packaging
  phase-changed: Monday, 25. November 2019 20:01 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  replaces: bug 1852238
  trackers:
bionic/linux-azure/azure-kernel: bug 1853899
  variant: debs

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

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

[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker

** 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 --
  kernel-stable-master-bug: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Packaging
- phase-changed: Monday, 25. November 2019 20:02 UTC
+ phase: Packaging
+ phase-changed: Monday, 25. November 2019 20:05 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1852239
  trackers:
bionic/linux-azure: bug 1852238, bug 1853900
  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/1853901

Title:
  disco/linux-azure: 5.0.0-1027.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:05 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1852239
  trackers:
bionic/linux-azure: bug 1853900, bug 1852238
  variant: debs

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

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

[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker

** Summary changed:

- disco/linux-azure:  -proposed tracker
+ disco/linux-azure: 5.0.0-1027.29 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

Title:
  disco/linux-azure: 5.0.0-1027.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:05 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1852239
  trackers:
bionic/linux-azure: bug 1852238, bug 1853900
  variant: debs

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

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

[Kernel-packages] [Bug 1853901] [NEW] disco/linux-azure: 5.0.0-1027.29 -proposed tracker

Public bug reported:

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 --
kernel-stable-master-bug: 1852253
packages:
  main: linux-azure
  meta: linux-meta-azure
  signed: linux-signed-azure
phase: Packaging
phase-changed: Monday, 25. November 2019 20:05 UTC
reason:
  prepare-package: Pending -- package not yet uploaded
  prepare-package-meta: Pending -- package not yet uploaded
  prepare-package-signed: Pending -- package not yet uploaded
replaces: bug 1852239
trackers:
  bionic/linux-azure: bug 1852238, bug 1853900
variant: debs

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: linux-azure stakeholder signoff (linux-azure-signoff)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux-azure (Ubuntu Disco)
 Importance: Medium
 Status: Confirmed


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.11.11-4 kernel-sru-derivative-of-1852253

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Tags added: disco kernel-release-tracking-bug

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

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/certification-testing
   Status: New =>

[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: -proposed tracker

** Summary changed:

- linux-azure:  -proposed tracker
+ disco/linux-azure:  -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** 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 --
  kernel-stable-master-bug: 1852253
+ packages:
+   main: linux-azure
+   meta: linux-meta-azure
+   signed: linux-signed-azure
+ phase: Ready for Packaging
+ phase-changed: Monday, 25. November 2019 20:02 UTC
+ reason:
+   prepare-package: Pending -- version not specified
  replaces: bug 1852239
+ trackers:
+   bionic/linux-azure: bug 1852238, bug 1853900
  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/1853901

Title:
  disco/linux-azure: 5.0.0-1027.29 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1852253
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Monday, 25. November 2019 20:05 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1852239
  trackers:
bionic/linux-azure: bug 1852238, bug 1853900
  variant: debs

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

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

[Kernel-packages] [Bug 1853900] [NEW] bionic/linux-azure: -proposed tracker

Public bug reported:

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 --
kernel-stable-master-bug: 1853901
packages:
  lrm: linux-restricted-modules-azure
  main: linux-azure
  meta: linux-meta-azure
  signed: linux-signed-azure
phase: Holding before Packaging
phase-changed: Monday, 25. November 2019 20:01 UTC
reason:
  prepare-package: Holding -- waiting for master bug
replaces: bug 1852238
trackers:
  bionic/linux-azure/azure-kernel: bug 1853899
variant: debs

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-lrm
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: linux-azure stakeholder signoff (linux-azure-signoff)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux-azure (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1853901 kernel-sru-cycle-2019.11.11-4

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-lrm
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Tags added: bionic kernel-release-tracking-bug

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

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided

[Kernel-packages] [Bug 1853694] Re: Ubuntu causing eye strain on Intel Integrated Graphics

2019-11-25 Thread Paul F

The screen is flickering in so much as there is a very faint shimmering
effect. This is usually the effect of dithering which adjusts the pixel
color values rapidly to give the impression of colors that are not
normally present. This effect is welcomed if using a low quality display
however for certain indivduals causes significant discomfort. Can it be
confirmed that any form of dithering is enabled by default in Ubuntu and
is there an option to turn it off?

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

Title:
  Ubuntu causing eye strain on Intel Integrated Graphics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find when running Ubuntu after 5-10 minutes get heavy eyes and after
  a few hours develop dizziness/headaches.

  After research online and talking with a community at LED Strain
  (https://ledstrain.org) it is believed the issue is caused by
  dithering being enabled on Ubuntu. There is no known way turn off all
  dithering by default and would like an option to turn off all
  dithering to avoid discomfort.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-36-generic 5.0.0-36.39~18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 23 12:56:12 2019
  InstallationDate: Installed on 2019-11-22 (1 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1853882] Re: Eoan update: 5.3.13 upstream stable release

2019-11-25 Thread Connor Kuehl

** 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:
+ * net: cdc_ncm: Signedness bug in cdc_ncm_set_dgram_size()
+ * block, bfq: deschedule empty bfq_queues not referred by any process
+ * mm/memory_hotplug: don't access uninitialized memmaps in shrink_pgdat_span()
+ * mm/memory_hotplug: fix updating the node span
+ * arm64: uaccess: Ensure PAN is re-enabled after unhandled uaccess fault
+ * fbdev: Ditch fb_edid_add_monspecs
+ * Linux 5.3.13
+ * UBUNTU: upstream stable to v5.3.13
  
-5.3.13 upstream stable release
-from git://git.kernel.org/
+    5.3.13 upstream stable release
+    from git://git.kernel.org/

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

Title:
  Eoan update: 5.3.13 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:

  * net: cdc_ncm: Signedness bug in cdc_ncm_set_dgram_size()
  * block, bfq: deschedule empty bfq_queues not referred by any process
  * mm/memory_hotplug: don't access uninitialized memmaps in shrink_pgdat_span()
  * mm/memory_hotplug: fix updating the node span
  * arm64: uaccess: Ensure PAN is re-enabled after unhandled uaccess fault
  * fbdev: Ditch fb_edid_add_monspecs
  * Linux 5.3.13
  * UBUNTU: upstream stable to v5.3.13

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

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

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

[Kernel-packages] [Bug 1852225] Re: eoan/linux-azure: 5.3.0-1008.9 -proposed tracker

** Changed in: kernel-sru-workflow/regression-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: 1852232
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 15. November 2019 16:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1852224
  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/1852225

Title:
  eoan/linux-azure: 5.3.0-1008.9 -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:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Eoan:
  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: 1852232
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 15. November 2019 16:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1852224
  variant: debs

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

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

[Kernel-packages] [Bug 1852223] Re: eoan/linux-aws: 5.3.0-1008.9 -proposed tracker

** Changed in: kernel-sru-workflow/regression-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: 1852232
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Friday, 15. November 2019 15:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.3: bug 185
  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/1852223

Title:
  eoan/linux-aws: 5.3.0-1008.9 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Eoan:
  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: 1852232
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Friday, 15. November 2019 15:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.3: bug 185
  variant: debs

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

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

[Kernel-packages] [Bug 1852225] Re: eoan/linux-azure: 5.3.0-1008.9 -proposed tracker

** Tags added: regression-testing-passed

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

Title:
  eoan/linux-azure: 5.3.0-1008.9 -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:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Eoan:
  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: 1852232
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 15. November 2019 16:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1852224
  variant: debs

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

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

[Kernel-packages] [Bug 1829992] Re: zram02 from kernel_misc test suite in LTP failed

** Tags added: arm64

** Tags removed: cosmic
** Tags added: eoan

** Tags added: arm64-aws

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

Title:
  zram02 from kernel_misc test suite in LTP failed

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

Bug description:
  startup='Wed May 22 07:02:20 2019'
  zram02 1 TINFO: create '1' zram device(s)
  zram02 1 TFAIL: unexpected num of devices: 4
  zram02 2 TINFO: zram cleanup
  tag=zram02 stime=1558508540 dur=0 exit=exited stat=1 core=no cu=1 cs=0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-20-generic 4.18.0-20.21
  ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 06:28 seq
   crw-rw 1 root audio 116, 33 May 22 06:28 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed May 22 07:52:48 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-20-generic N/A
   linux-backports-modules-4.18.0-20-generic  N/A
   linux-firmware 1.175.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

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

looks to be more related with the 5.3 kernel, also affects Eoan

** Tags added: eoan

** Tags added: aws

** Tags added: sru-2019

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1852223] Re: eoan/linux-aws: 5.3.0-1008.9 -proposed tracker

** Tags added: regression-testing-passed

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

Title:
  eoan/linux-aws: 5.3.0-1008.9 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Eoan:
  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: 1852232
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Friday, 15. November 2019 15:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.3: bug 185
  variant: debs

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

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

[Kernel-packages] [Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker

** Changed in: kernel-sru-workflow/regression-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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 14. November 2019 18:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
  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/1852232

Title:
  eoan/linux: 5.3.0-24.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:
  Confirmed
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  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: Testing
  phase-changed: Thursday, 14. November 2019 18:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
  variant: debs

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

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

[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed with B/E

** Tags added: s390x

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

Title:
  proc01 in fs from ubuntu_ltp failed with B/E

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

Bug description:
   proc01  0  TINFO  :  /proc/sys/fs/binfmt_misc/register: is write-only.
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/all/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/default/stable_secret: 
known issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/ens6/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/lo/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/kmsg: known issue: 
errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable
   proc01  0  TINFO  :  /proc/sysrq-trigger: is write-only.
   proc01  0  TINFO  :  /proc/self/task/8782/mem: known issue: 
errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/self/task/8782/clear_refs: is write-only.
   proc01  0  TINFO  :  /proc/self/task/8782/pagemap: reached maxmbytes (-m)
   proc01  0  TINFO  :  /proc/self/task/8782/attr/prev: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/exec: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/fscreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/keycreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/sockcreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  1  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument
   proc01  2  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument
   proc01  3  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument
   proc01  4  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument
   proc01  5  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument
   proc01  6  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument
   proc01  7  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument
   proc01  8  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument
   proc01  9  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/mem: known issue: errno=EIO(5): 
Input/output error
   proc01  0  TINFO  :  /proc/self/clear_refs: is write-only.
   proc01  0  TINFO  :  /proc/self/pagemap: reached maxmbytes (-m)
   proc01  0  TINFO  :  /proc/self/attr/prev: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/exec: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/fscreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/keycreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/sockcreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01 10  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument
   proc01 11  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument
   proc01 12  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument
   proc01 13  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument
   proc01 14  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument
   proc01 15  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument
   proc01 16  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument
   proc01 17  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument
   proc01 18  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/apparmor/exec: errno=EINVAL(22): Invalid argument
   proc01 19  TFAIL  :  proc01.c:466:

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

** Tags added: arm64

** Tags added: arm64-aws

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

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

Title:
  getaddrinfo_01 from ipv6_lib test suite in LTP failed

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

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

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

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

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

[Kernel-packages] [Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker

** Tags added: regression-testing-passed

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

Title:
  eoan/linux: 5.3.0-24.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:
  Confirmed
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  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: Testing
  phase-changed: Thursday, 14. November 2019 18:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
  variant: debs

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

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

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

Smoke/Boot test passed across amd64/ppc/s390x

** Tags added: regression-testing-passed

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1043.46 -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:
  Invalid
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, 25. 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/1853365/+subscriptions

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

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

** Changed in: kernel-sru-workflow/regression-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: Friday, 22. November 2019 09:52 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Monday, 25. November 2019 18:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-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/1853365

Title:
  bionic/linux-ibm-gt: 4.15.0-1043.46 -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:
  Invalid
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, 25. 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/1853365/+subscriptions

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

[Kernel-packages] [Bug 1836169] Re: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64

Again, similar to bug#1790825  I would like to see this test run on
newer hardware, not the HP Moonshots. will speak with sam

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

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Sean Feole (sfeole)

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

Title:
  cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64

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

Bug description:
  This issue can be found on both ThunderX and Moonshot ARM64

  <<>>
  incrementing stop
  Name:   cpuhotplug04
  Date:   Thu Jul 11 08:34:50 UTC 2019
  Desc:   Does it prevent us from offlining the last CPU?

  sh: echo: I/O error
  cpuhotplug04 1 TFAIL: Could not offline cpu0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=9 cstime=4
  <<>>

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jul 11 08:28:42 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1852406] Re: Double-escape in initramfs DECRYPT_CMD

2019-11-25 Thread Colin Ian King

I was hoping you could test the version in -proposed. Without it being
verified as fixed then the fix won't be released for Eoan.

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

Title:
  Double-escape in initramfs DECRYPT_CMD

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Eoan:
  Fix Committed
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  == SRU Justification, Eoan ==

  initramfs/scripts/zfs.in incorrectly quotes ${ENCRYPTIONROOT} on line
  414:

  DECRYPT_CMD="${ZFS} load-key '${ENCRYPTIONROOT}'"

  This is OK when the line is executed by shell, such as in line 430 or
  436, but when plymouth is used it results in plymouth executing "zfs
  load-key 'rpool'" - and zfs  is unable to find pool called "'rpool'".

  If I understand
  https://docs.oracle.com/cd/E23824_01/html/821-1448/gbcpt.html
  correctly zfs pool name is always 'shell-friendly', so removing the
  quotation marks would be a proper fix for that.

  == Fix ==

  One line fix as attached in https://bugs.launchpad.net/ubuntu/+source
  /zfs-linux/+bug/1852406/comments/1

  == Test ==

  Boot with encrypted data set with plymouth. Without the fix zfs is
  unable to find the root encrypted pool. With the fix this works.

  == Regression Potential ==

  This just affects the encrypted dataset that holds key for root
  dataset; currently this is causing issues because of the bug, so the
  risk of the fix outweighs the current situation where this is
  currently broken.

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

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

[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed with B/E

** Tags added: arm64

** Tags added: amd64

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

Title:
  proc01 in fs from ubuntu_ltp failed with B/E

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

Bug description:
   proc01  0  TINFO  :  /proc/sys/fs/binfmt_misc/register: is write-only.
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/all/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/default/stable_secret: 
known issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/ens6/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/lo/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/kmsg: known issue: 
errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable
   proc01  0  TINFO  :  /proc/sysrq-trigger: is write-only.
   proc01  0  TINFO  :  /proc/self/task/8782/mem: known issue: 
errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/self/task/8782/clear_refs: is write-only.
   proc01  0  TINFO  :  /proc/self/task/8782/pagemap: reached maxmbytes (-m)
   proc01  0  TINFO  :  /proc/self/task/8782/attr/prev: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/exec: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/fscreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/keycreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/sockcreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  1  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument
   proc01  2  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument
   proc01  3  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument
   proc01  4  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument
   proc01  5  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument
   proc01  6  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument
   proc01  7  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument
   proc01  8  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument
   proc01  9  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/mem: known issue: errno=EIO(5): 
Input/output error
   proc01  0  TINFO  :  /proc/self/clear_refs: is write-only.
   proc01  0  TINFO  :  /proc/self/pagemap: reached maxmbytes (-m)
   proc01  0  TINFO  :  /proc/self/attr/prev: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/exec: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/fscreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/keycreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/sockcreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01 10  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument
   proc01 11  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument
   proc01 12  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument
   proc01 13  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument
   proc01 14  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument
   proc01 15  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument
   proc01 16  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument
   proc01 17  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument
   proc01 18  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/apparmor/exec: errno=EINVAL(22): Invalid argument
   proc01 19  TFAIL  :

[Kernel-packages] [Bug 1790825] Re: gicv3-ipi and gicv3-active failed on Bionic Moonshot ARM64 server