[Kernel-packages] [Bug 1860969] Re: ipsec interfaces: fix sending with bpf_redirect() / AF_PACKET sockets

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-eoan

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

Title:
  ipsec interfaces: fix sending with bpf_redirect() / AF_PACKET sockets

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

Bug description:
  [SRU Justification]

  [Impact]

  Packets sent to a vti[6]/xfrm interface via bpf_redirect() or via an
  AF_PACKET socket are dropped (no carrier).

  This has been fixed in v5.5 by the following upstream commits
   - 95224166a903 ("vti[6]: fix packet tx through bpf_redirect()")
   - f042365dbffe ("xfrm interface: fix packet tx through bpf_redirect()")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=95224166a903
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f042365dbffe

  The bug exists since the beginning of each driver.

  == Fix ==

  Backport the requested patches to Focal (5.4), Eoan (5.3), Bionic (4.15) and
  Xenial (4.4).

  == Risk of Regression ==

  This patch affects only the cases described above (when no dst is
  attached to the skb), thus the risk should be low.

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

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


[Kernel-packages] [Bug 1860041] Re: shiftfs: prevent lower dentries from going negative during unlink

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-eoan

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

Title:
  shiftfs: prevent lower dentries from going negative during unlink

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

Bug description:
  SRU Justification

  Impact: All non-special files (For shiftfs this only includes fifos
  and - for this case - unix sockets - since we don't allow character
  and block devices to be created.) go through shiftfs_open() and have
  their dentry pinned through this codepath preventing it from going
  negative. But fifos don't use the shiftfs fops but rather use the
  pipefifo_fops which means they do not go through shiftfs_open() and
  thus don't have their dentry pinned that way. Thus, the lower dentries
  for such files can go negative on unlink causing segfaults. The
  following C program can be used to reproduce the crash:

  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char *argv[])
  {
struct stat stat;

  unlink("./bbb");

int ret = mknod("./bbb", S_IFIFO|0666, 0);
if (ret < 0)
exit(1);

int fd = open("./bbb", O_RDWR);
if (fd < 0)
exit(2);

if (unlink("./bbb"))
exit(4);

  fstat(fd, );

return 0;
  }

  Fix: Similar to ecryptfs we need to dget() the lower dentry before
  calling vfs_unlink() on it and dput() it afterwards.

  Regression Potential: Limited to shiftfs.

  Test Case: Compiled a kernel with the fix and used the reproducer
  above to verify that the kernel cannot be crashed anymore.

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

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


[Kernel-packages] [Bug 1861238] Re: Root can lift kernel lockdown via USB/IP

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-eoan

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

Title:
  Root can lift kernel lockdown via USB/IP

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]

  It's possible to turn off kernel lockdown by emulating a USB keyboard
  via USB/IP and sending an Alt+SysRq+X key combination through it.

  Ubuntu's kernels have USB/IP enabled (CONFIG_USBIP_VHCI_HCD=m and
  CONFIG_USBIP_CORE=m) with signed usbip_core and vhci_hcd modules
  provided in the linux-extra-modules-* package.

  See the PoC here: https://github.com/xairy/unlockdown#method-1-usbip

  [Test Case]

  $ git clone https://github.com/xairy/unlockdown.git
  $ cd unlockdown/01-usbip/
  $ sudo ./run.sh
  $ dmesg

  # Ensure there are no log entries talking about lifting lockdown:
  sysrq: SysRq : Disabling Secure Boot restrictions
  Lifting lockdown

  # You should see a SysRq help log entry because the Alt+SysRq+X
  # combination should be disabled
  sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) 
memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) 
show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) 
poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) 
show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) 
dump-ftrace-buffer(z)

  [Regression Potential]

  Some users may see a usability regression due to the Lockdown lift
  sysrq combination being removed. Some users are known to disable
  lockdown, using the sysrq combination, in order to perform some
  "dangerous" operation such as writing to an MSR. It is believed that
  this is a small number of users but it is impossible to know for sure.

  Users that rely on this functionality may need to permanently disable
  secure boot using 'mokutil --disable-validation'.

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

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


[Kernel-packages] [Bug 1862885] Re: Sometimes can't adjust brightness on Dell AIO

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-eoan

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

Title:
  Sometimes can't adjust brightness on Dell AIO

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  We already added retry on the backlight driver, but the scalar have to take 
some time to activate panel during booting up, and 2 seconds seem doesn't 
enough. So, it sometimes fails to get the response from scalar.

  [Fix]
  Enlarge the retry time from 2 seconds to 5 seconds.
  We didn't observe the response time longer than 3 seconds, but to be more 
confident, enlarge the value to 5 seconds.

  [Test]
  Verified on new Dell AIO platform.

  [Regression Potential]
  Low, increase the retry times doesn't hurt anything.

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

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


[Kernel-packages] [Bug 1862263] Re: test_sysctl in bpf from ubuntu_kernel_selftests make net test fails to build on eoan

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-eoan

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

Title:
  test_sysctl in bpf from ubuntu_kernel_selftests make net test fails to
  build on eoan

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  == SRU Justification ==
  Commit 7541c87c ("bpf: Allow narrow loads of bpf_sysctl fields with
  offset > 0") applied to Eoan tree via stable-update process brought a
  member called "seek" to tools/testing/selftests/bpf/test_sysctl.c:
 .seek = 4,

  However we don't have the commit that declares it, so the compilation
  failed with:
  test_sysctl.c:181:4: error: ‘struct sysctl_test’ has no member named 
‘seek’
181 | .seek = 4,
| ^~~~

  == Fix ==
  * d895a0f1 ("bpf: fix accessing bpf_sysctl.file_pos on s390")

  Only Eoan is affected.

  == Test ==
  Patch tested against the affected kernels, the bpf test can be built
  without any issue.

  == Regression Potential ==
  Low, changes limited to testing tools.

  
  ==Original Bug Report ==
  test_sysctl.c:181:4: error: ‘struct sysctl_test’ has no member named ‘seek’
  181 |   .seek = 4,
  |^~~~

  This affects all arches. Kernel 5.3.0-40.32.

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

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


[Kernel-packages] [Bug 1863294] Re: eoan/linux: 5.3.0-41.33 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

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

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

** 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: Promote to Proposed
- phase-changed: Monday, 17. February 2020 10:59 UTC
+ phase: Testing
+ phase-changed: Monday, 17. February 2020 22:51 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1863292
eoan/linux-aws: bug 1863272
eoan/linux-azure: bug 1863274
eoan/linux-gcp: bug 1863280
eoan/linux-kvm: bug 1863283
eoan/linux-oracle: bug 1863290
eoan/linux-raspi2: bug 1863269
  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/1863294

Title:
  eoan/linux: 5.3.0-41.33 -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:
  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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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: Monday, 17. February 2020 22:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1863292
eoan/linux-aws: bug 1863272
eoan/linux-azure: bug 1863274
eoan/linux-gcp: bug 1863280
eoan/linux-kvm: bug 1863283
eoan/linux-oracle: bug 1863290
eoan/linux-raspi2: bug 1863269
  variant: debs

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

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


[Kernel-packages] [Bug 1863276] Re: bionic/linux-hwe-5.0: 5.0.0-42.46~18.04.1 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-hwe-5.0
main: linux-hwe-5.0
meta: linux-meta-hwe-5.0
signed: linux-signed-hwe-5.0
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 14:53 UTC
- reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
  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/1863276

Title:
  bionic/linux-hwe-5.0: 5.0.0-42.46~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:
  New
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:
  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 verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-hwe-5.0
main: linux-hwe-5.0
meta: linux-meta-hwe-5.0
signed: linux-signed-hwe-5.0
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 14:53 UTC
  variant: debs

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

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


[Kernel-packages] [Bug 1862824] Re: bionic/linux: 4.15.0-88.88 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-security
   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 --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Holding before Promote to Security
- phase-changed: Monday, 17. February 2020 10:46 UTC
+ phase: Ready for Promote to Security
+ phase-changed: Monday, 17. February 2020 22:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Holding -- not ready for security (replication dwell)
+   promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-aws: bug 1862808
bionic/linux-fips: bug 1861152
bionic/linux-gke-4.15: bug 1862810
bionic/linux-ibm-gt: bug 1862812
bionic/linux-kvm: bug 1862811
bionic/linux-oem: bug 1863592
bionic/linux-oracle: bug 1862814
bionic/linux-raspi2: bug 1861134
bionic/linux-snapdragon: bug 1861136
bionic/linux/pc-kernel: bug 1862803
bionic/linux/pc-lowlatency-kernel: bug 1862804
xenial/linux-azure: bug 1862818
xenial/linux-gcp: bug 1862821
xenial/linux-hwe: bug 1862823
  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/1862824

Title:
  bionic/linux: 4.15.0-88.88 -proposed tracker

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

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: Ready for Promote to Security
  phase-changed: Monday, 17. February 2020 22:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-aws: bug 1862808
bionic/linux-fips: bug 1861152
bionic/linux-gke-4.15: bug 1862810
bionic/linux-ibm-gt: bug 1862812
bionic/linux-kvm: bug 1862811
bionic/linux-oem: bug 1863592
bionic/linux-oracle: bug 1862814
bionic/linux-raspi2: bug 1861134
bionic/linux-snapdragon: bug 1861136
bionic/linux/pc-kernel: bug 1862803
bionic/linux/pc-lowlatency-kernel: bug 1862804
xenial/linux-azure: bug 1862818
xenial/linux-gcp: bug 1862821
xenial/linux-hwe: bug 1862823
  variant: debs

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

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


[Kernel-packages] [Bug 1861199] Re: eoan/linux-aws: 5.3.0-1011.12 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-security
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861214
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
- phase: Holding before Promote to Security
- phase-changed: Monday, 17. February 2020 10:33 UTC
+ phase: Ready for Promote to Security
+ phase-changed: Monday, 17. February 2020 22:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Holding -- not ready for security (replication dwell)
+   promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-aws-5.3: bug 1861198
  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/1861199

Title:
  eoan/linux-aws: 5.3.0-1011.12 -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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Eoan:
  Fix Released

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: 1861214
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Ready for Promote to Security
  phase-changed: Monday, 17. February 2020 22:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-aws-5.3: bug 1861198
  variant: debs

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

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


[Kernel-packages] [Bug 1861205] Re: eoan/linux-gcp: 5.3.0-1012.13 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-security
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861214
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Holding before Promote to Security
- phase-changed: Monday, 17. February 2020 10:33 UTC
+ phase: Ready for Promote to Security
+ phase-changed: Monday, 17. February 2020 22:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Holding -- not ready for security (replication dwell)
+   promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-gcp-5.3: bug 1861202
bionic/linux-gke-5.3: bug 1861204
  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/1861205

Title:
  eoan/linux-gcp: 5.3.0-1012.13 -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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Eoan:
  Fix Released

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: 1861214
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Ready for Promote to Security
  phase-changed: Monday, 17. February 2020 22:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-gcp-5.3: bug 1861202
bionic/linux-gke-5.3: bug 1861204
  variant: debs

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

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


[Kernel-packages] [Bug 1861206] Re: eoan/linux-kvm: 5.3.0-1010.11 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-security
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861214
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Holding before Promote to Security
- phase-changed: Monday, 17. February 2020 10:33 UTC
+ phase: Ready for Promote to Security
+ phase-changed: Monday, 17. February 2020 22:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Holding -- not ready for security (replication dwell)
+   promote-to-security: Pending -- ready to copy
  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/1861206

Title:
  eoan/linux-kvm: 5.3.0-1010.11 -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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Eoan:
  Fix Released

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: 1861214
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Ready for Promote to Security
  phase-changed: Monday, 17. February 2020 22:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
  variant: debs

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

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


[Kernel-packages] [Bug 1861208] Re: eoan/linux-oracle: 5.3.0-1009.10 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-security
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861214
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Holding before Promote to Security
- phase-changed: Monday, 17. February 2020 10:34 UTC
+ phase: Ready for Promote to Security
+ phase-changed: Monday, 17. February 2020 22:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Holding -- not ready for security (replication dwell)
+   promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-oracle-5.3: bug 1861207
  variant: debs

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

Title:
  eoan/linux-oracle: 5.3.0-1009.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Eoan:
  Fix Released

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: 1861214
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Ready for Promote to Security
  phase-changed: Monday, 17. February 2020 22:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-oracle-5.3: bug 1861207
  variant: debs

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

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


[Kernel-packages] [Bug 1862398] Re: eoan/linux-azure: 5.3.0-1013.14 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-security
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861214
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Holding before Promote to Security
- phase-changed: Monday, 17. February 2020 10:34 UTC
+ phase: Ready for Promote to Security
+ phase-changed: Monday, 17. February 2020 22:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Holding -- not ready for security (replication dwell)
+   promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-azure-5.3: bug 1862397
  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/1862398

Title:
  eoan/linux-azure: 5.3.0-1013.14 -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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Eoan:
  Fix Released

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: 1861214
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Security
  phase-changed: Monday, 17. February 2020 22:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-azure-5.3: bug 1862397
  variant: debs

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

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


[Kernel-packages] [Bug 1863272] Re: eoan/linux-aws: 5.3.0-1012.13 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-eoan

** 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: 1863294
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
- phase: Holding before Promote to Proposed
- phase-changed: Monday, 17. February 2020 16:14 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Monday, 17. February 2020 22:26 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-aws-5.3: bug 1863270
  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/1863272

Title:
  eoan/linux-aws: 5.3.0-1012.13 -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 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 verification-testing series:
  New
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: 1863294
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 17. February 2020 22:26 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-aws-5.3: bug 1863270
  variant: debs

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

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


[Kernel-packages] [Bug 1861214] Re: eoan/linux: 5.3.0-40.32 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-security
   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 --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Holding before Promote to Security
- phase-changed: Monday, 17. February 2020 10:31 UTC
+ phase: Ready for Promote to Security
+ phase-changed: Monday, 17. February 2020 22:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Holding -- not ready for security (replication dwell)
+   promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-hwe: bug 1861212
eoan/linux-aws: bug 1861199
eoan/linux-azure: bug 1862398
eoan/linux-gcp: bug 1861205
eoan/linux-kvm: bug 1861206
eoan/linux-oracle: bug 1861208
eoan/linux-raspi2: bug 1861197
  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/1861214

Title:
  eoan/linux: 5.3.0-40.32 -proposed tracker

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

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: Ready for Promote to Security
  phase-changed: Monday, 17. February 2020 22:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
  trackers:
bionic/linux-hwe: bug 1861212
eoan/linux-aws: bug 1861199
eoan/linux-azure: bug 1862398
eoan/linux-gcp: bug 1861205
eoan/linux-kvm: bug 1861206
eoan/linux-oracle: bug 1861208
eoan/linux-raspi2: bug 1861197
  variant: debs

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

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


[Kernel-packages] [Bug 1863285] Re: bionic/linux-azure: 5.0.0-1033.35 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 22:13 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  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/1863285

Title:
  bionic/linux-azure: 5.0.0-1033.35 -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:
  Fix Committed
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: 1863297
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 22:13 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  variant: debs

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

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


[Kernel-packages] [Bug 988799]

2020-02-17 Thread ccloughwilliams
https://immiguy.com/

Mp3 Download: David & Nicole Binion ft. Todd Dulaney – Faith Sees +
Video

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

Title:
  Precise freezes under heavy i/o

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

Bug description:
  Whilst creating a VM with 20 GB persistent HD and my system froze
  until the disk was created.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-23-generic 3.2.0-23.36
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gema   2526 F pulseaudio
   /dev/snd/controlC0:  gema   2526 F pulseaudio
   /dev/snd/controlC1:  gema   2526 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 52'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11060397,104383c4,0010'
 Controls  : 45
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:00:1d.0-1.3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:081d'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 16
 Mono: Capture 12 [75%] [24.00dB] [on]
  Card2.Amixer.info:
   Card hw:2 'Generic'/'HD-Audio Generic at 0xfbbfc000 irq 53'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Thu Apr 26 11:59:11 2012
  HibernationDevice: RESUME=UUID=f32abdd2-8167-48c2-9d93-61eeb2632ca0
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IwConfig:
   lono wireless extensions.
   
   virbr0no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic 
root=UUID=109d1e55-4f64-489e-91e8-48ff46f6ba16 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-23-generic N/A
   linux-backports-modules-3.2.0-23-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2012-04-25 (0 days ago)
  dmi.bios.date: 03/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0401
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D-E LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0401:bd03/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1863274] Re: eoan/linux-azure: 5.3.0-1014.15 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:48 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-azure-5.3: bug 1863273
  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/1863274

Title:
  eoan/linux-azure: 5.3.0-1014.15 -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:
  Fix Committed
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 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: 1863294
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:48 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-azure-5.3: bug 1863273
  variant: debs

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

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


[Kernel-packages] [Bug 1863280] Re: eoan/linux-gcp: 5.3.0-1013.14 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:48 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-gcp-5.3: bug 1863275
bionic/linux-gke-5.3: bug 1863278
  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/1863280

Title:
  eoan/linux-gcp: 5.3.0-1013.14 -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:
  Fix Committed
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 verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1863294
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:48 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-gcp-5.3: bug 1863275
bionic/linux-gke-5.3: bug 1863278
  variant: debs

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

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


[Kernel-packages] [Bug 1863285] Re: bionic/linux-azure: 5.0.0-1033.35 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1863297
  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: Monday, 17. February 2020 21:16 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 17. February 2020 22:13 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  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/1863285

Title:
  bionic/linux-azure: 5.0.0-1033.35 -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:
  In Progress
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: 1863297
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 22:13 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  variant: debs

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

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


[Kernel-packages] [Bug 1863285] Re: bionic/linux-azure: 5.0.0-1033.35 -proposed tracker

2020-02-17 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  bionic/linux-azure: 5.0.0-1033.35 -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:
  In Progress
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: 1863297
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 22:13 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  variant: debs

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

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


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

2020-02-17 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX534FTC.304
  

[Kernel-packages] [Bug 1863269] Re: eoan/linux-raspi2: 5.3.0-1019.21 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1863294
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:37 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1019.21 -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:
  New
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 Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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: 1863294
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:37 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
  variant: debs

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

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


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

2020-02-17 Thread Kirill
apport information

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

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

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: 

[Kernel-packages] [Bug 1863274] Re: eoan/linux-azure: 5.3.0-1014.15 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1863294
  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: Monday, 17. February 2020 21:33 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 17. February 2020 21:48 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-azure-5.3: bug 1863273
  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/1863274

Title:
  eoan/linux-azure: 5.3.0-1014.15 -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:
  In Progress
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 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: 1863294
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:48 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-azure-5.3: bug 1863273
  variant: debs

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

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


[Kernel-packages] [Bug 1854842] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs

2020-02-17 Thread Matthew Ruffell
Hi Mohammad,

Thanks for verifying the kernel again, and good to see that things have
been fixed when you run padded traffic over your NICs.

The SRU cycle has completed, and the 4.15.0-88-generic kernel has been
released to -updates. You can go ahead and tell your affected customers
to upgrade to this kernel to fix their checksum problems.

That's all from me now. Let me know if you need anything else.

Thanks,
Matthew

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

Title:
  mlx5_core reports hardware checksum error for padded packets on
  Mellanox NICs

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

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1854842

  [Impact]

  On machines equipped with Mellanox NIC's, in this particular case,
  Mellanox 5 series NICs using the mlx5_core driver, there is a kernel
  splat when sending large IP packets which have padding at the end.

  enp6s0f0: hw csum failure
  CPU: 19 PID: 0 Comm: swapper/19 Not tainted 4.15.0-72-generic
  Call Trace:
  
  dump_stack+0x63/0x8e
  netdev_rx_csum_fault+0x38/0x40
  __skb_checksum_complete+0xbc/0xd0
  nf_ip_checksum+0xc3/0xf0
  icmp_error+0x27d/0x310 [nf_conntrack_ipv4]
  nf_conntrack_in+0x15a/0x510 [nf_conntrack]
  ? __skb_checksum+0x68/0x330
  ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4]
  nf_hook_slow+0x48/0xc0
  ? skb_send_sock+0x50/0x50
  ip_rcv+0x301/0x360
  ? inet_del_offload+0x40/0x40
  __netif_receive_skb_core+0x432/0xb80
  __netif_receive_skb+0x18/0x60
  ? __netif_receive_skb+0x18/0x60
  netif_receive_skb_internal+0x45/0xe0
  napi_gro_receive+0xc5/0xf0
  mlx5e_handle_rx_cqe+0x48d/0x5e0 [mlx5_core]
  ? enqueue_task_rt+0x1b4/0x2e0
  mlx5e_poll_rx_cq+0xd1/0x8c0 [mlx5_core]
  mlx5e_napi_poll+0x9d/0x290 [mlx5_core]
  net_rx_action+0x140/0x3a0
  __do_softirq+0xe4/0x2d4
  irq_exit+0xc5/0xd0
  do_IRQ+0x86/0xe0
  common_interrupt+0x8c/0x8c
  

  This bug is a further attempt to fix these splats, as there has been
  previous fixes in LP #1840854 and a series of commits which landed in
  4.15.0-67 (LP #1847155) as a part of upstream -stable patches.

  This bug will also fix the same problems on the new Mellanox CX6 and
  Bluefield hardware, which has been enabled already via previous
  upstream -stable patches which landed in LP #1847155.

  [Fix]

  This particular issue was fixed for Mellanox series 5 drivers in the
  following commits:

  commit 0aa1d18615c163f92935b806dcaff9157645233a
  Author: Saeed Mahameed 
  Date:   Tue Mar 12 00:24:52 2019 -0700
  Subject: net/mlx5e: Rx, Fixup skb checksum for packets with tail padding

  This commit required a minor backport.

  This commit was selected for upstream -stable in 4.19.76 and 5.0.10.
  This commit appears to be omitted from "Bionic update: upstream stable 
patchset 2019-10-07", which is LP #1847155, probably due to requiring a 
backport.

  commit db849faa9bef993a1379dc510623f750a72fa7ce
  Author: Saeed Mahameed 
  Date:   Fri May 3 13:14:59 2019 -0700
  Subject: net/mlx5e: Rx, Fix checksum calculation for new hardware

  This commit required a minor backport.

  This commit was selected for upstream -stable in 5.1.21 and 5.2.4.
  This commit has already been applied to the disco kernel, as part of stable 
updates.

  [Testcase]

  The following scapy script will reproduce this issue. Run from the
  machine with the Mellanox series 5 NIC:

  1)
  
a=Ether(dst='ff:ff:ff:ff:ff:ff')/IP(dst='127.0.0.1')/ICMP()/Padding(load='\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe')

  2) sendp(a, iface='enp6s0f0')

  3) Check dmesg on the reciever side. The example uses localhost, so
  check dmesg.

  I have built some test kernels, which are available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp1854842-test
  This kernel contains 0aa1d18615c163f92935b806dcaff9157645233a.

  and

  https://launchpad.net/~mruffell/+archive/ubuntu/lp1854842-test-2
  This kernel contains db849faa9bef993a1379dc510623f750a72fa7ce.

  If you install the test kernels the issue is resolved.

  [Regression Potential]

  The changes are limited to the mlx5_core driver, and only modify how
  packet checksums are calculated when padding is involved.

  Both patches have been accepted and published by upstream -stable, and
  are widely accepted by the community.

  Because of this, I believe the risk of regression is low.

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

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

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

2020-02-17 Thread Kirill
apport information

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American Megatrends Inc.
 

[Kernel-packages] [Bug 1863592] Re: bionic/linux-oem: 4.15.0-1073.83 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:32 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1073.83 -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:
  New
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 Committed
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 verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:32 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  variant: debs

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

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


[Kernel-packages] [Bug 1863280] Re: eoan/linux-gcp: 5.3.0-1013.14 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Ready for Promote to Proposed
- phase-changed: Monday, 17. February 2020 21:33 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 17. February 2020 21:48 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-gcp-5.3: bug 1863275
bionic/linux-gke-5.3: bug 1863278
  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/1863280

Title:
  eoan/linux-gcp: 5.3.0-1013.14 -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:
  In Progress
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 verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1863294
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:48 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-gcp-5.3: bug 1863275
bionic/linux-gke-5.3: bug 1863278
  variant: debs

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

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


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

2020-02-17 Thread Kirill
apport information

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American Megatrends Inc.
 

[Kernel-packages] [Bug 1863280] Re: eoan/linux-gcp: 5.3.0-1013.14 -proposed tracker

2020-02-17 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  eoan/linux-gcp: 5.3.0-1013.14 -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:
  In Progress
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 verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1863294
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:48 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-gcp-5.3: bug 1863275
bionic/linux-gke-5.3: bug 1863278
  variant: debs

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

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


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

2020-02-17 Thread Kirill
apport information

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  

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

2020-02-17 Thread Kirill
apport information

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American 

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

2020-02-17 Thread Kirill
apport information

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: 

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

2020-02-17 Thread Kirill
apport information

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American 

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

2020-02-17 Thread Kirill
apport information

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American Megatrends 

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

2020-02-17 Thread Kirill
apport information

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American 

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

2020-02-17 Thread Kirill
apport information

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American 

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

2020-02-17 Thread Kirill
apport information

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  

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

2020-02-17 Thread Kirill
apport information

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American 

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

2020-02-17 Thread Kirill
apport information

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

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  New

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polina29075 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks 
   Bus 001 Device 002: ID 248a:8367  
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American 

[Kernel-packages] [Bug 1863675] Re: ASUS Zenbook 15 UX534FTC no sound

2020-02-17 Thread Kirill
apport information

** Tags added: apport-collected bionic

** Description changed:

  Hello everyone.
  
  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I installed
  Ubuntu 18.04 on it and everything works fine except sound. When music
  plays - pavucontrol indicates that there is sound, but my speakers are
  silent. No sound at all.
  
  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645
  
  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:
  
  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel
  
  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.
  
  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  
  
  Seems like a bug. Need solution.
  
  P.S. Sorry for my English.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.9
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  polina29075 F pulseaudio
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-02-15 (2 days ago)
+ InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 13d3:56cb IMC Networks 
+  Bus 001 Device 002: ID 248a:8367  
+  Bus 001 Device 004: ID 8087:0026 Intel Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-40-generic N/A
+  linux-backports-modules-5.3.0-40-generic  N/A
+  linux-firmware1.173.14
+ Tags:  bionic
+ Uname: Linux 5.3.0-40-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/16/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX534FTC.304
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX534FTC
+ 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

[Kernel-packages] [Bug 1863269] Re: eoan/linux-raspi2: 5.3.0-1019.21 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1863294
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Ready for Promote to Proposed
- phase-changed: Monday, 17. February 2020 19:53 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 17. February 2020 21:37 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1019.21 -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:
  New
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:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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: 1863294
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:37 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
  variant: debs

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

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


[Kernel-packages] [Bug 1863274] Re: eoan/linux-azure: 5.3.0-1014.15 -proposed tracker

2020-02-17 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  eoan/linux-azure: 5.3.0-1014.15 -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:
  In Progress
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 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: 1863294
  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: Monday, 17. February 2020 21:33 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-azure-5.3: bug 1863273
  variant: debs

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

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


[Kernel-packages] [Bug 1863274] Re: eoan/linux-azure: 5.3.0-1014.15 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-eoan

** 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: 1863294
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Holding before Promote to Proposed
- phase-changed: Monday, 17. February 2020 16:57 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Monday, 17. February 2020 21:33 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-azure-5.3: bug 1863273
  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/1863274

Title:
  eoan/linux-azure: 5.3.0-1014.15 -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:
  In Progress
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 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: 1863294
  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: Monday, 17. February 2020 21:33 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-azure-5.3: bug 1863273
  variant: debs

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

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


[Kernel-packages] [Bug 1863272] Re: eoan/linux-aws: 5.3.0-1012.13 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 16:14 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building
+   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  trackers:
bionic/linux-aws-5.3: bug 1863270
  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/1863272

Title:
  eoan/linux-aws: 5.3.0-1012.13 -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 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 verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 16:14 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  trackers:
bionic/linux-aws-5.3: bug 1863270
  variant: debs

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

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


[Kernel-packages] [Bug 1863280] Re: eoan/linux-gcp: 5.3.0-1013.14 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-eoan

** 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: 1863294
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Holding before Promote to Proposed
- phase-changed: Monday, 17. February 2020 16:16 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Monday, 17. February 2020 21:33 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-gcp-5.3: bug 1863275
bionic/linux-gke-5.3: bug 1863278
  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/1863280

Title:
  eoan/linux-gcp: 5.3.0-1013.14 -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 verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1863294
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:33 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-gcp-5.3: bug 1863275
bionic/linux-gke-5.3: bug 1863278
  variant: debs

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

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


[Kernel-packages] [Bug 1863269] Re: eoan/linux-raspi2: 5.3.0-1019.21 -proposed tracker

2020-02-17 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  eoan/linux-raspi2: 5.3.0-1019.21 -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:
  New
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:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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: 1863294
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:37 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
  variant: debs

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

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


[Kernel-packages] [Bug 1863592] Re: bionic/linux-oem: 4.15.0-1073.83 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
- phase: Ready for Promote to Proposed
- phase-changed: Monday, 17. February 2020 14:00 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 17. February 2020 21:32 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1073.83 -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:
  New
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:
  In Progress
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 verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:32 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1799497

Title:
  4.15 kernel hard lockup about once a week

Status in linux package in Ubuntu:
  Incomplete
Status in zram-config package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in zram-config source package in Bionic:
  Confirmed

Bug description:
  == SRU Justification ==

  When using zram (as installed and configured with the zram-config package)
  systems can lockup after about a week of use.  This occurs because of
  a hang in a lock in zram.

  == Test Case ==

  Run stress-ng --brk 0 --stack 0 in a Bionic amd64 server VM with 1GM of
  memory, 16 CPU threads and zram-config installed.  Without the fix the
  kernel will hang in a spinlock after 1-2 hours of run time. With the fix,
  the hang does not occur.  Testing shows that with the fix, 5 x 16 CPU hours
  of stress testing with stress-ng works fine without the lockup occurring.

  == The fix ==

  Upstream commit c4d6c4cc7bfd ("zram: correct flag name of ZRAM_ACCESS") as
  a prerequisite followed by a minor context wiggle backport of the fix with
  commit 3c9959e02547 ("zram: fix lockdep warning of free block handling").

  == Regression Potential ==

  This touches the zram locking, so the core zram driver is affected. However
  the fixes are backports from 5.0, so the fixes have had a fair amount of
  testing in later kernels.


  My main server has been running into hard lockups about once a week
  ever since I switched to the 4.15 Ubuntu 18.04 kernel.

  When this happens, nothing is printed to the console, it's effectively
  stuck showing a login prompt. The system is running with panic=1 on
  the cmdline but isn't rebooting so the kernel isn't even processing
  this as a kernel panic.

  As this felt like a potential hardware issue, I had my hosting
  provider give me a completely different system, different motherboard,
  different CPU, different RAM and different storage, I installed that
  system on 18.04 and moved my data over, a week later, I hit the issue
  again.

  We've since also had a LXD user reporting similar symptoms here also on 
varying hardware:
    https://github.com/lxc/lxd/issues/5197

  My system doesn't have a lot of memory pressure with about 50% of free
  memory:

  root@vorash:~# free -m
    totalusedfree  shared  buff/cache   
available
  Mem:  31819   17574 402 513   13842   
13292
  Swap: 159092687   13222

  I will now try to increase console logging as much as possible on the
  system in the hopes that next time it hangs we can get a better idea
  of what happened but I'm not too hopeful given the complete silence on
  the console when this occurs.

  System is currently on:
    Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  But I've seen this since the GA kernel on 4.15 so it's not a recent 
regression.
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 23 16:12 seq
   crw-rw 1 root audio 116, 33 Oct 23 16:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  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: Cannot stat file /proc/22822/fd/10: Permission denied
   Cannot stat file /proc/22831/fd/10: Permission denied
  DistroRelease: Ubuntu 18.04
  HibernationDevice:
   RESUME=none
   CRYPTSETUP=n
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation S1200SP
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   

[Kernel-packages] [Bug 1860284] Re: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot

2020-02-17 Thread Benoit Grégoire
Still no luck with 5.5.4

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

Title:
  thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on
  Yoga C940 unless plugged in before boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a
  New Lenovo Yoga C940 laptop.

  - The dock works fine when plugged-in before boot.
  - The dock does NOT work when plugged after the system booted.
  - The dock does NOT work when plugged-in at boot, subsequently unplugged and 
plugged back in.

  When it fails, it fails with memory allocation messages such as:

  [  342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20]
  [  342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 
0x0c20]

  Things I tried:
  - Kernel mainline 5.4.12, same symptoms
  - Kernel mainline 5.5.-rc6, 
  same symptoms.
  - Plugging it after powering up the laptop, but at the grub screen before 
boot.  In this case the dock works fine after boot.

  
  Other potentially useful information to narrow it down:

  - The tests were done with only an ethernet cable and power plugged into the 
dock to minimize the number of moving parts...
  - Dock and laptop both have the very latest firmware as of 2020-01-17.
  - The displayport part of the dock always work, but all other ports (USB, 
ethernet, card readers fail) when plugged-in after boot.
  - Doesn't seem to be a thunderbolt authorization problem:
  benoitg@benoitg-Yoga-C940:~$ boltctl 
   ? Lenovo ThinkPad Thunderbolt 3 Dock
 ?? type:  peripheral
 ?? name:  ThinkPad Thunderbolt 3 Dock
 ?? vendor:Lenovo
 ?? uuid:  001730c5-7042-0801--
 ?? status:authorized
 ?  ?? domain: c06e823d-af8a-8680--
 ?  ?? authflags:  none
 ?? authorized:Sun Jan 19 17:41:04 2020
 ?? connected: Sun Jan 19 17:41:04 2020
 ?? stored:Thu Jan 16 07:27:43 2020
?? policy: iommu
?? key:no

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-26-generic 5.3.0-26.28
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benoitg1182 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun Jan 19 12:38:17 2020
  InstallationDate: Installed on 2020-01-16 (3 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81Q9
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1861238] Re: Root can lift kernel lockdown via USB/IP

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1861238

Title:
  Root can lift kernel lockdown via USB/IP

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]

  It's possible to turn off kernel lockdown by emulating a USB keyboard
  via USB/IP and sending an Alt+SysRq+X key combination through it.

  Ubuntu's kernels have USB/IP enabled (CONFIG_USBIP_VHCI_HCD=m and
  CONFIG_USBIP_CORE=m) with signed usbip_core and vhci_hcd modules
  provided in the linux-extra-modules-* package.

  See the PoC here: https://github.com/xairy/unlockdown#method-1-usbip

  [Test Case]

  $ git clone https://github.com/xairy/unlockdown.git
  $ cd unlockdown/01-usbip/
  $ sudo ./run.sh
  $ dmesg

  # Ensure there are no log entries talking about lifting lockdown:
  sysrq: SysRq : Disabling Secure Boot restrictions
  Lifting lockdown

  # You should see a SysRq help log entry because the Alt+SysRq+X
  # combination should be disabled
  sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) 
memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) 
show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) 
poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) 
show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) 
dump-ftrace-buffer(z)

  [Regression Potential]

  Some users may see a usability regression due to the Lockdown lift
  sysrq combination being removed. Some users are known to disable
  lockdown, using the sysrq combination, in order to perform some
  "dangerous" operation such as writing to an MSR. It is believed that
  this is a small number of users but it is impossible to know for sure.

  Users that rely on this functionality may need to permanently disable
  secure boot using 'mokutil --disable-validation'.

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

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


[Kernel-packages] [Bug 1774815] Re: Add bpftool to linux-tools-common

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1774815

Title:
  Add bpftool to linux-tools-common

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  bpftool is a debugging and introspection tool actively developed by
  the BPF kernel community. It's developed as part of the kernel source
  tree under tools/:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/bpf/bpftool

  It would be really great and appreciated if Ubuntu folks could package
  this as part of linux-tools-common.

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

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


[Kernel-packages] [Bug 1862114] Re: pty03 from pty in ubuntu_ltp failed on Eoan

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1862114

Title:
  pty03 from pty in ubuntu_ltp failed on Eoan

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  == Justification ==
  The test case pty03 from pty in ubuntu_ltp is failing with kernel NULL
  pointer dereference:

  [ 951.306823] BUG: kernel NULL pointer dereference, address: 0020
  [ 951.309960] #PF: supervisor write access in kernel mode
  [ 951.312130] #PF: error_code(0x0002) - not-present page
  [ 951.314227] PGD 0 P4D 0
  [ 951.315278] Oops: 0002 [#1] SMP PTI
  [ 951.316705] CPU: 1 PID: 39102 Comm: pty03 Not tainted 5.4.0-12-generic 
#15-Ubuntu
  [ 951.319737] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [ 951.322713] RIP: 0010:queue_work_on+0x1b/0x50

  [ 951.352494] Call Trace:
  [ 951.353244] slip_write_wakeup+0x25/0x30 [slip]
  [ 951.354600] tty_wakeup+0x5b/0x70
  [ 951.355539] pty_unthrottle+0x19/0x30
  [ 951.356560] tty_unthrottle+0x42/0x60
  [ 951.357566] __tty_perform_flush+0x87/0x90
  [ 951.358768] n_tty_ioctl_helper+0xcc/0x150
  [ 951.359955] n_tty_ioctl+0x2d/0x100
  [ 951.360930] tty_ioctl+0x3c0/0x8e0
  [ 951.361882] ? __switch_to_asm+0x34/0x70
  [ 951.363049] ? __switch_to_asm+0x40/0x70
  [ 951.364191] ? __switch_to_asm+0x34/0x70
  [ 951.365261] ? __switch_to_asm+0x40/0x70
  [ 951.366382] ? __switch_to_asm+0x34/0x70
  [ 951.367452] ? __switch_to_asm+0x40/0x70
  [ 951.368523] ? __switch_to_asm+0x34/0x70
  [ 951.369693] ? __switch_to_asm+0x40/0x70
  [ 951.370829] ? __switch_to_asm+0x34/0x70
  [ 951.371923] ? __switch_to_asm+0x40/0x70
  [ 951.372998] ? __switch_to_asm+0x34/0x70
  [ 951.374097] ? __switch_to_asm+0x40/0x70
  [ 951.375183] ? __switch_to_asm+0x34/0x70
  [ 951.376288] ? __switch_to_asm+0x40/0x70
  [ 951.377390] ? __switch_to+0x110/0x470
  [ 951.378863] do_vfs_ioctl+0x407/0x670
  [ 951.380269] ? __schedule+0x2eb/0x740
  [ 951.381761] ksys_ioctl+0x67/0x90
  [ 951.383076] __x64_sys_ioctl+0x1a/0x20
  [ 951.384510] do_syscall_64+0x57/0x190
  [ 951.385896] entry_SYSCALL_64_after_hwframe+0x44/0xa9

  == Fixes ==
  Indicated by the test case, this issue can be fixed by:
  * 0ace17d5 (can, slip: Protect tty->disc_data in write_wakeup and
  close with RCU)

  This patch can be cherry-picked into all of our kernels.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1862114-pty03/

  Tested on KVM nodes and the patched kernels work as expected, there
  will be no more kernel null pointer dereference issue, and the test
  can finish properly.

  == Regression potential ==
  Low, changes limited to two specific drivers for serial line TTY. This
  issue can be reproduced quite easily and the patched kernels show
  positive results.


  == Original Bug Report ==
  startup='Thu Feb  6 02:45:23 2020'
   tst_test.c:1215: INFO: Timeout per run is 0h 05m 00s
   pty03.c:101: INFO: Creating PTY with SLIP line discipline
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Cannot kill test processes!
   Congratulation, likely test hit a kernel bug.
   Exitting uncleanly...
   tag=pty03 stime=1580957123 dur=350 exit=exited stat=1 core=no cu=0 cs=0

  This is a new test case, so it's not a regression.

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

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


[Kernel-packages] [Bug 1860657] Re: Prevent arm64 guest from accessing host debug registers

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1860657

Title:
  Prevent arm64 guest from accessing host debug registers

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Guests could access host debug/PMU registers. This could happen very briefly 
before they are first preempted.
  This only affects arm64 CPUs that support virtualization.

  [Regression potential]
  This could break virtualization or guest access to PMU registers.

  [Test case]
  A guest has been run with a host with the patched kernel. perf top has been 
run on the guest. Using uvtool:

  host$ sudo apt install uvtool qemu-efi-aarch64
  host$ uvt-kvm create test release=eoan arch=arm64
  host$ uvt-kvm ssh test
  guest$ sudo perf top

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

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


[Kernel-packages] [Bug 1863350] Re: bionic/linux: 4.15.0-89.89 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

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

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

** 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: Promote to Proposed
- phase-changed: Monday, 17. February 2020 13:46 UTC
+ phase: Testing
+ phase-changed: Monday, 17. February 2020 21:28 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1863325
bionic/linux-fips: bug 1863341
bionic/linux-gke-4.15: bug 1863330
bionic/linux-ibm-gt: bug 1863335
bionic/linux-kvm: bug 1863332
bionic/linux-oem: bug 1863312
bionic/linux-oracle: bug 1863339
bionic/linux-raspi2: bug 1863305
bionic/linux-snapdragon: bug 1863310
bionic/linux/pc-kernel: bug 1863301
bionic/linux/pc-lowlatency-kernel: bug 1863302
xenial/linux-azure: bug 1863344
xenial/linux-gcp: bug 1863347
xenial/linux-hwe: bug 1863349
  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/1863350

Title:
  bionic/linux: 4.15.0-89.89 -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:
  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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Monday, 17. February 2020 21:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1863325
bionic/linux-fips: bug 1863341
bionic/linux-gke-4.15: bug 1863330
bionic/linux-ibm-gt: bug 1863335
bionic/linux-kvm: bug 1863332
bionic/linux-oem: bug 1863312
bionic/linux-oracle: bug 1863339
bionic/linux-raspi2: bug 1863305
bionic/linux-snapdragon: bug 1863310
bionic/linux/pc-kernel: bug 1863301
bionic/linux/pc-lowlatency-kernel: bug 1863302
xenial/linux-azure: bug 1863344
xenial/linux-gcp: bug 1863347

[Kernel-packages] [Bug 1863675] [NEW] ASUS Zenbook 15 UX534FTC no sound

2020-02-17 Thread Kirill
Public bug reported:

Hello everyone.

Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I installed
Ubuntu 18.04 on it and everything works fine except sound. When music
plays - pavucontrol indicates that there is sound, but my speakers are
silent. No sound at all.

I googled that problem and found this topic:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

I tried Petr Nosek's solution, but unfortunately sound not appeared.
What did I do:

1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
3. Added one line to the patch_realtek.c:
$ git diff
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 1fc4cc89d62b..ba04bbe75ba0 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
+   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
4. Typed 2 commands: 
fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic binary-perarch
5. Kernel build was successful and then I've installed it
6. Rebooted my laptop and booted into the new kernel

Sound not appeared after these steps. Pavucontrol indicates that
everything is OK, but speakers not producing any sound. Screenshot in
attachment.

My hwinfo:
$ hwinfo --sound
18: PCI 1f.3: 0403 Audio device 
  [Created at pci.378]
  Unique ID: nS1_.9G5mT1GK4nF
  SysFS ID: /devices/pci:00/:00:1f.3
  SysFS BusID: :00:1f.3
  Hardware Class: sound
  Model: "Intel Audio device"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x02c8 
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x1a61 
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
  Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
  IRQ: 148 (635 events)
  Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
  Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
  Driver Info #1:
Driver Status: snd_soc_skl is active
Driver Activation Cmd: "modprobe snd_soc_skl"
  Driver Info #2:
Driver Status: sof_pci_dev is active
Driver Activation Cmd: "modprobe sof_pci_dev"
  Config Status: cfg=new, avail=yes, need=no, active=unknown


Seems like a bug. Need solution.

P.S. Sorry for my English.

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


** Tags: asus sound

** Attachment added: "pavucontrol_screenshot.png"
   
https://bugs.launchpad.net/bugs/1863675/+attachment/5329078/+files/pavucontrol_screenshot.png

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  

[Kernel-packages] [Bug 1863294] Re: eoan/linux: 5.3.0-41.33 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 10:59 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-hwe: bug 1863292
eoan/linux-aws: bug 1863272
eoan/linux-azure: bug 1863274
eoan/linux-gcp: bug 1863280
eoan/linux-kvm: bug 1863283
eoan/linux-oracle: bug 1863290
eoan/linux-raspi2: bug 1863269
  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/1863294

Title:
  eoan/linux: 5.3.0-41.33 -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:
  New
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 Committed
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 verification-testing series:
  New
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
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 10:59 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-hwe: bug 1863292
eoan/linux-aws: bug 1863272
eoan/linux-azure: bug 1863274
eoan/linux-gcp: bug 1863280
eoan/linux-kvm: bug 1863283
eoan/linux-oracle: bug 1863290
eoan/linux-raspi2: bug 1863269
  variant: debs

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

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


[Kernel-packages] [Bug 1862840] Re: [Bionic] i915 incomplete fix for CVE-2019-14615

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1862840

Title:
  [Bionic] i915 incomplete fix for CVE-2019-14615

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

Bug description:
  [Impact]

  Gregory Herrero reported that the proof-of-concept for CVE-2019-14615
  indicates that the information leak is not fixed in the Bionic 4.15
  kernel as indicated by USN-4255-1:

   https://usn.ubuntu.com/4255-1/

  This only affects Ubuntu's 4.15 kernel series. Xenial (4.4), Disco
  (5.0), Eoan (5.3), and Focal (5.4) are not affected by this incomplete
  fix issue.

  I've verified this by testing each Ubuntu release with the proof-of-
  concept. I then tested vanilla 4.15 with commit bc8a76a152c5
  ("drm/i915/gen9: Clear residual context state on context switch")
  applied, which is the fix for CVE-2019-14615, and verified that the
  proof-of-concept showed that the info leak was still possible. I then
  tested vanilla 4.16 with commit bc8a76a152c5 applied to verify that
  the proof-of-concept showed that the info leak was fixed.

  After bisecting changes to the DRM subsystem as well as the i915
  driver, it looks like commit d2b4b97933f5 ("drm/i915: Record the
  default hw state after reset upon load") as well as its prerequisites
  are necessary to fully fix CVE-2019-14615 in 4.15 based kernels.

  [Test Case]

  A proof-of-concept for CVE-2019-14615 became available once the issue
  was made public. It can be found here:

   https://github.com/HE-Wenjian/iGPU-Leak

  Steps to use the proof-of-concept:

   $ git clone https://github.com/HE-Wenjian/iGPU-Leak.git

   # In one terminal
   $ cd iGPU-Leak/demo/SLM_Leak/
   $ ./run_victim.sh

   # In another terminal
   $ cd iGPU-Leak/demo/SLM_Leak/
   $ ./run_attacker.sh

   # In the terminal running run_attacker.sh, ensure that all data dumped
   # to the terminal is zeros and that there is no non-zero data. You'll
   # have to closely monitor the script for a minute or so to ensure that
   # the information leak is not possible.

  [Regression Potential]

  High as the changes are complex in comparison to the typical SRU.
  However, the bulk of the change is to the initialization stages of the
  driver and we're just pulling back changes that landed in 4.16-rc1 to
  our 4.15 kernel. I don't see any later Fixes tags that reference the
  needed commits.

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

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


[Kernel-packages] [Bug 1862885] Re: Sometimes can't adjust brightness on Dell AIO

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1862885

Title:
  Sometimes can't adjust brightness on Dell AIO

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  We already added retry on the backlight driver, but the scalar have to take 
some time to activate panel during booting up, and 2 seconds seem doesn't 
enough. So, it sometimes fails to get the response from scalar.

  [Fix]
  Enlarge the retry time from 2 seconds to 5 seconds.
  We didn't observe the response time longer than 3 seconds, but to be more 
confident, enlarge the value to 5 seconds.

  [Test]
  Verified on new Dell AIO platform.

  [Regression Potential]
  Low, increase the retry times doesn't hurt anything.

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

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


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

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

apport-collect 1863675

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

Title:
  ASUS Zenbook 15 UX534FTC no sound

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello everyone.

  Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
  installed Ubuntu 18.04 on it and everything works fine except sound.
  When music plays - pavucontrol indicates that there is sound, but my
  speakers are silent. No sound at all.

  I googled that problem and found this topic:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645

  I tried Petr Nosek's solution, but unfortunately sound not appeared.
  What did I do:

  1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
  2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
  3. Added one line to the patch_realtek.c:
  $ git diff
  diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
  index 1fc4cc89d62b..ba04bbe75ba0 100644
  --- a/sound/pci/hda/patch_realtek.c
  +++ b/sound/pci/hda/patch_realtek.c
  @@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
  SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", 
ALC256_FIXUP_ASUS_HEADSET_MIC),
  SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
  SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
  +   SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC", 
ALC294_FIXUP_ASUS_SPK),
  SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
  SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA", 
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
  SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
  4. Typed 2 commands: 
  fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic binary-perarch
  5. Kernel build was successful and then I've installed it
  6. Rebooted my laptop and booted into the new kernel

  Sound not appeared after these steps. Pavucontrol indicates that
  everything is OK, but speakers not producing any sound. Screenshot in
  attachment.

  My hwinfo:
  $ hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61 
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
  Driver Status: sof_pci_dev is active
  Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
  Seems like a bug. Need solution.

  P.S. Sorry for my English.

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

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


[Kernel-packages] [Bug 1862567] Re: [SRU][B/OEM-B] Fix multitouch support on some devices

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1862567

Title:
  [SRU][B/OEM-B] Fix multitouch support on some devices

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Some LG touchscreens reported themselves as generic touch devices,
  actually it is multitouch devices.
  Even after adding IDs in hid-multitouch, hid-generic will bind the device 
still.
  multitouch features are not supported.

  [Fix]
  commit e04a0442 make hid-generic work nicely with other drivers like 
hid-multitouch.
  If other drivers match the devices, hid-generic will step back.
  This patch will benefit many devices to support their own drivers without 
adding IDs.

  [Test]
  Verified on LG/ELAN/RAYDIUM touchscreens with positive results.

  [Regression Potential]
  Medium.
  commit e04a0442 is included by 4.16 kernel, only bionic kernel should be 
applied.
  This commit is based on the other 3  patches, mostly changes are moving codes 
to hid-quirk.c.
  Backports are during to the other backports patches, these changes are moved 
to
  hid-quirk.c too.

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

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


[Kernel-packages] [Bug 1863592] Re: bionic/linux-oem: 4.15.0-1073.83 -proposed tracker

2020-02-17 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

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

Title:
  bionic/linux-oem: 4.15.0-1073.83 -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:
  New
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:
  In Progress
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 verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 21:32 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1863285] Re: bionic/linux-azure: 5.0.0-1033.35 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** 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: 1863297
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Holding before Promote to Proposed
- phase-changed: Monday, 17. February 2020 18:16 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Monday, 17. February 2020 21:16 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  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/1863285

Title:
  bionic/linux-azure: 5.0.0-1033.35 -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: 1863297
  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: Monday, 17. February 2020 21:16 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  variant: debs

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

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


[Kernel-packages] [Bug 1861973] Re: run_afpackettests in ubuntu_kernel_selftests failed with "./in_netns.sh: Permission denied"

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  run_afpackettests in ubuntu_kernel_selftests failed with
  "./in_netns.sh: Permission denied"

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux-signed package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux-signed source package in Xenial:
  Invalid

Bug description:
  This issue begins with my fix in bug 1853375,
  the newly created in_netns.sh script got file permission with:
  new file mode 100755

  However, it lost the executable property when downloaded by the test case:
  -rw-r--r--  1 root root   298 Feb  5 07:41 in_netns.sh

  If you do a manual chmod this test will pass without any issue.

  This commit can be found here in Xenial tree:
  https://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h
  =master-next=df9283329019ce48157c84fcd06c61204139abb7

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-174-generic 4.4.0-174.204
  ProcVersionSignature: User Name 4.4.0-174.204-generic 4.4.211
  Uname: Linux 4.4.0-174-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Wed Feb  5 07:27:33 2020
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1863338] Re: xenial/linux: 4.4.0-175.205 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

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

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

** 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:
main: linux
meta: linux-meta
signed: linux-signed
- phase: Promote to Proposed
- phase-changed: Monday, 17. February 2020 14:48 UTC
+ phase: Testing
+ phase-changed: Monday, 17. February 2020 21:02 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1863334
trusty/linux-lts-xenial: bug 1863336
xenial/linux-aws: bug 1863311
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1863331
xenial/linux-kvm: bug 1863319
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1863304
xenial/linux/pc-kernel: bug 1863306
xenial/linux/stlouis-kernel: bug 1863307
  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/1863338

Title:
  xenial/linux: 4.4.0-175.205 -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:
  Confirmed
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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Monday, 17. February 2020 21:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1863334
trusty/linux-lts-xenial: bug 1863336
xenial/linux-aws: bug 1863311
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1863331
xenial/linux-kvm: bug 1863319
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1863304
xenial/linux/pc-kernel: bug 1863306
xenial/linux/stlouis-kernel: bug 1863307
  variant: debs

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

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

[Kernel-packages] [Bug 1862114] Re: pty03 from pty in ubuntu_ltp failed on Eoan

2020-02-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  pty03 from pty in ubuntu_ltp failed on Eoan

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  == Justification ==
  The test case pty03 from pty in ubuntu_ltp is failing with kernel NULL
  pointer dereference:

  [ 951.306823] BUG: kernel NULL pointer dereference, address: 0020
  [ 951.309960] #PF: supervisor write access in kernel mode
  [ 951.312130] #PF: error_code(0x0002) - not-present page
  [ 951.314227] PGD 0 P4D 0
  [ 951.315278] Oops: 0002 [#1] SMP PTI
  [ 951.316705] CPU: 1 PID: 39102 Comm: pty03 Not tainted 5.4.0-12-generic 
#15-Ubuntu
  [ 951.319737] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [ 951.322713] RIP: 0010:queue_work_on+0x1b/0x50

  [ 951.352494] Call Trace:
  [ 951.353244] slip_write_wakeup+0x25/0x30 [slip]
  [ 951.354600] tty_wakeup+0x5b/0x70
  [ 951.355539] pty_unthrottle+0x19/0x30
  [ 951.356560] tty_unthrottle+0x42/0x60
  [ 951.357566] __tty_perform_flush+0x87/0x90
  [ 951.358768] n_tty_ioctl_helper+0xcc/0x150
  [ 951.359955] n_tty_ioctl+0x2d/0x100
  [ 951.360930] tty_ioctl+0x3c0/0x8e0
  [ 951.361882] ? __switch_to_asm+0x34/0x70
  [ 951.363049] ? __switch_to_asm+0x40/0x70
  [ 951.364191] ? __switch_to_asm+0x34/0x70
  [ 951.365261] ? __switch_to_asm+0x40/0x70
  [ 951.366382] ? __switch_to_asm+0x34/0x70
  [ 951.367452] ? __switch_to_asm+0x40/0x70
  [ 951.368523] ? __switch_to_asm+0x34/0x70
  [ 951.369693] ? __switch_to_asm+0x40/0x70
  [ 951.370829] ? __switch_to_asm+0x34/0x70
  [ 951.371923] ? __switch_to_asm+0x40/0x70
  [ 951.372998] ? __switch_to_asm+0x34/0x70
  [ 951.374097] ? __switch_to_asm+0x40/0x70
  [ 951.375183] ? __switch_to_asm+0x34/0x70
  [ 951.376288] ? __switch_to_asm+0x40/0x70
  [ 951.377390] ? __switch_to+0x110/0x470
  [ 951.378863] do_vfs_ioctl+0x407/0x670
  [ 951.380269] ? __schedule+0x2eb/0x740
  [ 951.381761] ksys_ioctl+0x67/0x90
  [ 951.383076] __x64_sys_ioctl+0x1a/0x20
  [ 951.384510] do_syscall_64+0x57/0x190
  [ 951.385896] entry_SYSCALL_64_after_hwframe+0x44/0xa9

  == Fixes ==
  Indicated by the test case, this issue can be fixed by:
  * 0ace17d5 (can, slip: Protect tty->disc_data in write_wakeup and
  close with RCU)

  This patch can be cherry-picked into all of our kernels.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1862114-pty03/

  Tested on KVM nodes and the patched kernels work as expected, there
  will be no more kernel null pointer dereference issue, and the test
  can finish properly.

  == Regression potential ==
  Low, changes limited to two specific drivers for serial line TTY. This
  issue can be reproduced quite easily and the patched kernels show
  positive results.


  == Original Bug Report ==
  startup='Thu Feb  6 02:45:23 2020'
   tst_test.c:1215: INFO: Timeout per run is 0h 05m 00s
   pty03.c:101: INFO: Creating PTY with SLIP line discipline
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Cannot kill test processes!
   Congratulation, likely test hit a kernel bug.
   Exitting uncleanly...
   tag=pty03 stime=1580957123 dur=350 exit=exited stat=1 core=no cu=0 cs=0

  This is a new test case, so it's not a regression.

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

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


[Kernel-packages] [Bug 1863289] Re: bionic/linux-gcp: 5.0.0-1032.33 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 19:08 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1863287
  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/1863289

Title:
  bionic/linux-gcp: 5.0.0-1032.33 -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:
  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 verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 19:08 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1863287
  variant: debs

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

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


[Kernel-packages] [Bug 1863290] Re: eoan/linux-oracle: 5.3.0-1010.11 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 17:26 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  trackers:
bionic/linux-oracle-5.3: bug 1863286
  variant: debs

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

Title:
  eoan/linux-oracle: 5.3.0-1010.11 -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:
  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 verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle 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 --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 17:26 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  trackers:
bionic/linux-oracle-5.3: bug 1863286
  variant: debs

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

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


[Kernel-packages] [Bug 1851340] Re: [mgag200] Ubuntu 19.10 upgrade results in invisible mouse cursor on Matrox G200eR2

2020-02-17 Thread John Hartley
Hi Po-Hsu Lin & others,

got fix via latest update, which was applied to 2 machines and confirmed
cursor working again now on console:

$ uname -a
Linux blue 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

$ uname -a
Linux green 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux


Thank you again for working on this bug,

Cheers,

Zebity.

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

Title:
  [mgag200] Ubuntu 19.10 upgrade results in invisible mouse cursor on
  Matrox G200eR2

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

Bug description:
  == SRU Justification ==
  The cursor on Matrox G200eR2 will disappear after upgrading kernel from
  Disco to Eoan, this is caused by this commit that got applied in Eoan:
  4dc57b10 (drm/mgag200: Rewrite cursor handling)

  == Fix ==
  * a9c342ab (drm/mgag200: Don't unpin the current cursor image's buffer.)
  * cf578c8c (drm/mgag200: Set cursor scanout address to correct BO)
  * e61576c4 (drm/mgag200: add in missing { } around if block)
  * a0fd72d2 (drm/mgag200: Pin displayed cursor BO to video memory)

  Focal got these patches already and it does not have this issue.

  == Test ==
  Test kernel could be found here:
    https://people.canonical.com/~phlin/kernel/lp-1851340-mgag200-cursor/

  Verified by the bug reporter, John Hartley, the patched kernel can fix
  this issue.

  == Regression Potential ==
  Low, change limited to mgag200 cursor itself, and it's already been
  applied on newer releases.


  == Original Bug Report ==
  Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have visible 
cursor with my Gnone desktop.

  I have found the same problem when upgrading 2 machines from Ubuntu
  19.04 -> 19.10.

  Reproducing problem is easy:

  1. Open Ubuntu Update Window
  2. Select "Upgrade"
  3. On completion of update (after reboot) cursor is no longer visible.
  4. This applies to display connected to VGA port on host with USB Keyboard + 
Mouse

  While the connected display has no visible cursor and so is usable, I
  have always used X11VNC Server to provide network GUI access. On the
  remote X11VNC display I see and can use the cursor.

  This bug report is being sent via Remote X11VNC window, as I cannot
  use the main VGA display window (due to lack of visible cursor)

  I have done search online and thought that maybe issue was with my USB
  Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
  result, no visible mouse cursor.

  I have done: "grep usb /var/log/syslog" and can see many USB events,
  including both Apple and Logitech mouse detection events.

  NOTE:

  Due to compatibility issue with X11VNC, I have disable Wayland on both
  machines by adding the following option to: /etc/gdm3/custom.conf

  WaylandEnable=false

  Regards,

  John Hartley.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 18:25:23 2019
  DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo G200eR2 [1d49:0a01]
  InstallationDate: Installed on 2018-12-17 (322 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO System x3650 M5: -[8871AC1]-
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash 
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: -[TCE140H-2.91]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 01KN179
  dmi.board.vendor: LENOVO
  dmi.board.version: NULL
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
  dmi.product.family: System X
  dmi.product.name: System x3650 M5: -[8871AC1]-
  dmi.product.sku: (none)
  dmi.product.version: 13
  dmi.sys.vendor: LENOVO
  

[Kernel-packages] [Bug 1863285] Re: bionic/linux-azure: 5.0.0-1033.35 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 18:16 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  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/1863285

Title:
  bionic/linux-azure: 5.0.0-1033.35 -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:
  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: 1863297
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 18:16 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  variant: debs

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

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


[Kernel-packages] [Bug 1861925] Re: BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range 0..255

2020-02-17 Thread Ecker Sandor
I have tried the the points 1-16 in the document  
https://wiki.ubuntu.com/Kernel/Debugging/Backlight 
but I think in the latest kernel (5.5++) some parameters are removed. 
https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html

Point 10: use_bios_initial_backlight is not found in:
https://www.kernel.org/doc/html/latest/search.html?q=use_bios_initial_backlight_keywords=yes=default

Point 11:
https://www.kernel.org/doc/html/latest/search.html?q=use_native_backlight_keywords=yes=default#

On 5.6.rc1 the parameters for vide are under: /sys/module/video/parameters/
report_key_events
only_lcd
hw_changes_brightness
disable_backlight_sysfs_if
device_id_scheme
brightness_switch_enabled
allow_duplications

The problem is I have not found any documentation to these parameters
too... :(

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

Title:
  BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range
  0..255

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have a acer aspire a315-41 laptop, it has BIOS 1.15, Ubuntu 19.10,
  Kernel stock 5.3, and 5.5.0. I have a problem with the Backlight. I
  can not control.

  According to: https://wiki.ubuntu.com/Kernel/Debugging/Backlight

  It is : Backlight control does not work, but there are entries in
  /sys/class/backlight.

  The problem is as far I could find:

  sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat brightness
  135
  sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat actual_brightness
  43500
  sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat max_brightness
  255

  The brightness read from the HW is not in the range, and when I change
  the brightness by the keys the value in the brightness file changes
  too, but the actual_brightness is stuck at the value 43500...

  I have tried all the steps mentioned in
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight

  Actually I have tried all these kernel startup parameter variants
  without luck:

  GRUB_CMDLINE_LINUX_DEFAULT=""
  #GRUB_CMDLINE_LINUX_DEFAULT="video.use_native_backlight=1"
  #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi="
  #GRUB_CMDLINE_LINUX_DEFAULT="video.use_bios_initial_backlight=0"
  #GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dcfeaturemask=0x4 amdgpu.abmlevel=2"
  #GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=video amdgpu.abmlevel=1"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=Linux acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=video"
  #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"

  I guess the fwts has found also this as an error:

  autobrightness: Automated LCD brightness test.
  

  Test 1 of 2: Test for maximum and actual brightness.
  PASSED: Test 1, Maximum brightness for amdgpu_bl0 is 255 which is sane.
  FAILED [HIGH] BrightnessOutofRange: Test 1, Actual brightness for amdgpu_bl0 
not
  in range 0..255.

  Test 2 of 2: Change actual brightness.
  FAILED [MEDIUM] BrightnessMismatch: Test 2, 256 brightness levels did not 
match
  the brightnesss level just set for backlight amdgpu_bl0.
  The failed brightness levels were: 0-255.

  It would be great if someone could help set the HW brightness back to
  the normal range.

  If you need any more debug files please let me know!

  Thanks,
  Regards,
  Sandor

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

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


[Kernel-packages] [Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels

2020-02-17 Thread Tim Sweeney
This is still present in the focal daily release. 
5.4.0-14-generic #17-Ubuntu

** Tags added: focal

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

Title:
  ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent
  kernels

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New

Bug description:
  Short version
  =
  I'm experiencing a 50-second hang each time I resume from a "deep" 
(suspend-to-RAM) sleep.

  It happens with the newer kernel (5.3 series; I'm currently running
  the version from eoan-proposed), but not with the version from the
  Ubuntu 18.04.3 LTS (uname says "5.0.0-31-generic #33~18.04.1-Ubuntu
  SMP").

  [I haven't yet tried to test the mainline builds, nor to find/confirm
  the regression range, as this seems like something that will take me
  another week, and I'm not sure if it would be helpful.]

  I narrowed the problem down to what I believe is a broken USB Type-C
  controller on the NVIDIA GPU: the ucsi_ccg driver for
  /sys/devices/pci:00/:00:01.0/:01:00.3/i2c-0/0-0008 reports
  a timeout for both the initial PPM_RESET command (on system startup)
  and for the SET_NOTIFICATION_ENABLE command the driver runs on resume.

  I guess the hang is the driver waiting for a response to
  SET_NOTIFICATION_ENABLE; it appears to have been added recently in
  
https://github.com/torvalds/linux/commit/a94ecde41f7e51e2742e53b5f151aee662c54d39,
  which could explain why I don't see the hang with 5.0.x.

  Creating /etc/modprobe.d/dell.conf with a `blacklist ucsi_ccg` line
  (and rebooting) makes the hang go away.


  Steps to reproduce
  ==
  (these are not the actual steps one can take to reproduce, starting from a 
new install; let me know if those will be useful)

  1. Boot Ubuntu 19.10 with NVIDIA GPU drivers uninstalled and the following 
kernel parameters 
:
nouveau.modeset=0 nouveau.runpm=0   # force using integrated graphics
  # (the problem can be reproduced 
using NVIDIA's proprietary driver too, but I
  # guessed it's better to avoid 
it, and nouveau prints lots of errors with this GPU)
mem_sleep_default=deep  # suspend to RAM; suspend-to-idle 
has its own problems on this system

  2. Run `dmesg -w` and wait a minute or two until a message like the
  following is printed:

[  175.611346] ucsi_ccg 0-0008: failed to reset PPM!
[  175.611355] ucsi_ccg 0-0008: PPM init failed (-110)

  (attempting to suspend before the PPM init timeout will fail to enter sleep 
at all.)
  (if your system doesn't report PPM init timeout, you probably won't see the 
hang on resume either)

  3. Run `sudo pm-suspend` (using the power button to suspend causes
  other problems)

  ...wait for the laptop to go to sleep and the fans to turn off.

  4. Press Enter on the built-in keyboard to resume. (Although the way
  we wake up the system doesn't seem to matter.)

  5. Observe a hang lasting for almost a minute before the system is
  operational, with dmesg reporting:

[  299.331393] ata1.00: configured for UDMA/100


[  346.133024] ucsi_ccg 0-0008: PPM NOT RESPONDING
[  346.133039] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 
[ucsi_ccg] returns -110
[  346.133042] PM: Device 0-0008 failed to resume: error -110
...
[  346.141504] Restarting tasks ... done.
[  346.340221] PM: suspend exit

  
  System info
  ===

  My Dell G3 3590 laptop has an NVIDIA "GeForce GTX 1660 Ti with Max-Q Design" 
GPU.
  NVIDIA's "Turing" chips include USB Type-C controller on the GPU (I read 
future VR headsets are supposed to use it 
),
 and indeed I'm seeing:

  # lspci -tv
  -[:00]-+-00.0  Intel Corporation 8th Gen Core Processor Host Bridge/DRAM 
Registers
 +-01.0-[01]--+-00.0  NVIDIA Corporation TU116M [GeForce GTX 1660 
Ti Mobile]
 |+-00.1  NVIDIA Corporation Device 1aeb
 |+-00.2  NVIDIA Corporation Device 1aec
 |\-00.3  NVIDIA Corporation Device 1aed
  ...

  Where the '1aed' device is detected as "NVIDIA USB Type-C Port Policy
  Controller" in Windows.

  I'm not sure if it's serving any useful purpose on this laptop, and it
  certainly doesn't seem to function properly:

  If I enable UCSI logging on startup (root's crontab):

  @reboot bash -c 'echo 1 >
  /sys/kernel/debug/tracing/events/ucsi/enable'

  ..the steps to reproduce above result in the following 
/sys/kernel/debug/tracing/trace:
  # tracer: 

[Kernel-packages] [Bug 1863269] Re: eoan/linux-raspi2: 5.3.0-1019.21 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-eoan

** 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: 1863294
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Holding before Promote to Proposed
- phase-changed: Monday, 17. February 2020 14:52 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Monday, 17. February 2020 19:53 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1019.21 -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:
  New
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:
  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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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: 1863294
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 17. February 2020 19:53 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
  variant: debs

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

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


[Kernel-packages] [Bug 1863289] Re: bionic/linux-gcp: 5.0.0-1032.33 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 19:08 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1863287
  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/1863289

Title:
  bionic/linux-gcp: 5.0.0-1032.33 -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:
  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 verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 19:08 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1863287
  variant: debs

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

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


[Kernel-packages] [Bug 1863350] Re: bionic/linux: 4.15.0-89.89 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 13:46 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-aws: bug 1863325
bionic/linux-fips: bug 1863341
bionic/linux-gke-4.15: bug 1863330
bionic/linux-ibm-gt: bug 1863335
bionic/linux-kvm: bug 1863332
bionic/linux-oem: bug 1863312
bionic/linux-oracle: bug 1863339
bionic/linux-raspi2: bug 1863305
bionic/linux-snapdragon: bug 1863310
bionic/linux/pc-kernel: bug 1863301
bionic/linux/pc-lowlatency-kernel: bug 1863302
xenial/linux-azure: bug 1863344
xenial/linux-gcp: bug 1863347
xenial/linux-hwe: bug 1863349
  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/1863350

Title:
  bionic/linux: 4.15.0-89.89 -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:
  New
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 Committed
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 verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 13:46 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-aws: bug 1863325
bionic/linux-fips: bug 1863341
bionic/linux-gke-4.15: bug 1863330
bionic/linux-ibm-gt: bug 1863335
bionic/linux-kvm: bug 1863332
bionic/linux-oem: bug 1863312
bionic/linux-oracle: bug 1863339
bionic/linux-raspi2: bug 1863305
bionic/linux-snapdragon: bug 1863310
bionic/linux/pc-kernel: bug 1863301
bionic/linux/pc-lowlatency-kernel: bug 1863302
xenial/linux-azure: bug 1863344
xenial/linux-gcp: bug 1863347
xenial/linux-hwe: bug 1863349
  variant: debs

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

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


[Kernel-packages] [Bug 1861300] Re: Data Corruption with Sil 3114 and 3124 controlleurs

2020-02-17 Thread xenoxis
After somes tests, seems that some data through Samba are copied well,
but some fail every time I try to copy them, the checksum change at
every copies.

I don't know if there's consecutive bits that failed the transfer or
something else, but the fact is there : the bug is still there (even if
Disabling NCQ made a difference).

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

Title:
  Data Corruption with Sil 3114 and 3124 controlleurs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Silicon Image 3114 and 3124 seem to have data corruption at writing data 
(particularly with big files or when the writing concern lot of files).
  I used a PCI card with the Sil 3114 chip; when copying files and directories 
from a HDD to an other, data corruption appears and seems to be random in files.
  But every checks about the computer (RAM, HDD ...) have gone right.
  Don't know what happening really, but I supposed that the module which 
control the Sil 3114 (and so the Sil 3124, cause this module was written from 
the 3114's module) contain a bug.
  I've tried to enable the Sil 3114 module's option called "slow_down" which 
should solve some "problems", no difference with and without this option 
activated. The Sil 3124 module's doesn't have this option.

  Drives connected to Sil3124 controller seems to be affected by data
  corruption when at least 2 process attempts to writing at the same
  drive (obviously not in the same directory nor the same file), against
  Sil3114 which the bug seems to appears anytime.

  I have already posted a question :
  https://unix.stackexchange.com/questions/564067/file-corruption-
  between-2-hdd with more precisions about what have done until now.

  Now i use a PCI card based on the Sil 3124 controller, seems to have
  the same data corruption issue as the Sil 3114, but less pronounced
  (less often).

  Running Ubuntu 16.04 server i386 with Linux Kernel 4.4.211.

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

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


[Kernel-packages] [Bug 1863269] Re: eoan/linux-raspi2: 5.3.0-1019.21 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863294
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 14:52 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa main:queued
+   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1019.21 -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:
  New
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:
  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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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 --
  kernel-stable-master-bug: 1863294
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 14:52 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
  variant: debs

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

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


[Kernel-packages] [Bug 1863294] Re: eoan/linux: 5.3.0-41.33 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 10:59 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed 
signed:retry-needed
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-hwe: bug 1863292
eoan/linux-aws: bug 1863272
eoan/linux-azure: bug 1863274
eoan/linux-gcp: bug 1863280
eoan/linux-kvm: bug 1863283
eoan/linux-oracle: bug 1863290
eoan/linux-raspi2: bug 1863269
  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/1863294

Title:
  eoan/linux: 5.3.0-41.33 -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:
  New
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 Committed
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 verification-testing series:
  New
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
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 10:59 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-hwe: bug 1863292
eoan/linux-aws: bug 1863272
eoan/linux-azure: bug 1863274
eoan/linux-gcp: bug 1863280
eoan/linux-kvm: bug 1863283
eoan/linux-oracle: bug 1863290
eoan/linux-raspi2: bug 1863269
  variant: debs

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

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


[Kernel-packages] [Bug 1863338] Re: xenial/linux: 4.4.0-175.205 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 14:48 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
trusty/linux-aws: bug 1863334
trusty/linux-lts-xenial: bug 1863336
xenial/linux-aws: bug 1863311
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1863331
xenial/linux-kvm: bug 1863319
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1863304
xenial/linux/pc-kernel: bug 1863306
xenial/linux/stlouis-kernel: bug 1863307
  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/1863338

Title:
  xenial/linux: 4.4.0-175.205 -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:
  New
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 Committed
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 verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 14:48 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
trusty/linux-aws: bug 1863334
trusty/linux-lts-xenial: bug 1863336
xenial/linux-aws: bug 1863311
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1863331
xenial/linux-kvm: bug 1863319
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1863304
xenial/linux/pc-kernel: bug 1863306
xenial/linux/stlouis-kernel: bug 1863307
  variant: debs

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

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


[Kernel-packages] [Bug 1863269] Re: eoan/linux-raspi2: 5.3.0-1019.21 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863294
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 14:52 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
+   promote-to-proposed: Pending -- builds not complete in ppa main:queued
  trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1019.21 -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:
  New
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:
  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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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 --
  kernel-stable-master-bug: 1863294
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 14:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa main:queued
  trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
  variant: debs

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

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


[Kernel-packages] [Bug 1858811] Re: Linux 5.3.0-26-generic kernel

2020-02-17 Thread Gerald Rozner
Yes the desktop can be reached but the kernels beyond 5.3.0-24 including
the latest one 5.3.0-40 loop twice including POST before continuing. Its
a bug not a cosmetic change. I'm pretty confident it affects many Intel
Nucs, not just my two listed above. Since these machines boot in about 7
seconds it could be easily missed. Note that this does not affect my
Asus Z77 with legacy boot as mentioned above. Not a problem because I've
modified GRUB to boot from 5.3.0-24.

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

Title:
  Linux 5.3.0-26-generic kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just after installation and reboot of Linux 5.3.0-26 kernel and reboot
  on two NUC machines UEFI they displayed the normal Intel splash screen
  followed by the normal grub menu. Then went back to the Intel splash
  screen again and continued to the desktop. I have another machine Asus
  Z77 with legacy boot and the same kernel update with no such issue.

  It should be noted that both NUC machines have been running since
  October last year with Ubuntu 18.10 without kernel issues up until
  now. As a result I have rolled back to Linux 5.3.0-24 and no such
  behavior is displayed.

  The NUCs involved are NUC7i7BNH and NUC5i7RYH.

  Thanks,
  Gerald Rozner

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gerald  915 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  8 10:08:41 2020
  InstallationDate: Installed on 2018-11-08 (426 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation NUC7i7BNH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=0e89ac23-8213-483e-9102-240ad3cfe107 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-21 (78 days ago)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-310
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-311:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-310:cvnIntelCorporation:ct3:cvr2:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC7i7BNH
  dmi.product.version: J31153-311
  dmi.sys.vendor: Intel Corporation

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

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


[Kernel-packages] [Bug 1863289] Re: bionic/linux-gcp: 5.0.0-1032.33 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** 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-lrm
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-lrm
   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: 1863297
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Packaging
- phase-changed: Monday, 17. February 2020 18:01 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Monday, 17. February 2020 19:08 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
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:building,signed:depwait
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1863287
  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/1863289

Title:
  bionic/linux-gcp: 5.0.0-1032.33 -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:
  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 verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 19:08 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:building,signed:depwait
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1863287
  variant: debs

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

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


[Kernel-packages] [Bug 1863280] Re: eoan/linux-gcp: 5.3.0-1013.14 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 16:16 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  trackers:
bionic/linux-gcp-5.3: bug 1863275
bionic/linux-gke-5.3: bug 1863278
  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/1863280

Title:
  eoan/linux-gcp: 5.3.0-1013.14 -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:
  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 verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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 --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 16:16 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  trackers:
bionic/linux-gcp-5.3: bug 1863275
bionic/linux-gke-5.3: bug 1863278
  variant: debs

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

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


[Kernel-packages] [Bug 1863274] Re: eoan/linux-azure: 5.3.0-1014.15 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 16:57 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
lrm:depwait,main:queued,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  trackers:
bionic/linux-azure-5.3: bug 1863273
  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/1863274

Title:
  eoan/linux-azure: 5.3.0-1014.15 -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:
  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 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 --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 16:57 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  trackers:
bionic/linux-azure-5.3: bug 1863273
  variant: debs

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

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


[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT

2020-02-17 Thread Eugene Batogov
My alsa info: http://alsa-
project.org/db/?f=9f087f5038e450cf77cdf21d21f86af763626d787

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

Title:
  No sound on ASUS UX534FT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  after instal Ubuntu in dual boot alongside Windows 10, I've realised
  there is no sound coming out of mine new ASUS Zenbook 15 UX534FT-
  AA024R in Ubuntu. In Windows there is no problem. Found this topic
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had
  the same problem with driver for Realtek ALC294 which is also mine
  sound card. But even with this fix it is not working on UX534FT. Can
  you please add fix also for this newer model?

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 15:11:25 2019
  InstallationDate: Installed on 2019-10-29 (0 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/1850439/+subscriptions

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


[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT

2020-02-17 Thread Eugene Batogov
correct link: http://alsa-
project.org/db/?f=9f087f5038e450cf77cdf21d21f86af763626d78

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

Title:
  No sound on ASUS UX534FT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  after instal Ubuntu in dual boot alongside Windows 10, I've realised
  there is no sound coming out of mine new ASUS Zenbook 15 UX534FT-
  AA024R in Ubuntu. In Windows there is no problem. Found this topic
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had
  the same problem with driver for Realtek ALC294 which is also mine
  sound card. But even with this fix it is not working on UX534FT. Can
  you please add fix also for this newer model?

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 15:11:25 2019
  InstallationDate: Installed on 2019-10-29 (0 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/1850439/+subscriptions

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


[Kernel-packages] [Bug 1863350] Re: bionic/linux: 4.15.0-89.89 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 13:46 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:building
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-aws: bug 1863325
bionic/linux-fips: bug 1863341
bionic/linux-gke-4.15: bug 1863330
bionic/linux-ibm-gt: bug 1863335
bionic/linux-kvm: bug 1863332
bionic/linux-oem: bug 1863312
bionic/linux-oracle: bug 1863339
bionic/linux-raspi2: bug 1863305
bionic/linux-snapdragon: bug 1863310
bionic/linux/pc-kernel: bug 1863301
bionic/linux/pc-lowlatency-kernel: bug 1863302
xenial/linux-azure: bug 1863344
xenial/linux-gcp: bug 1863347
xenial/linux-hwe: bug 1863349
  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/1863350

Title:
  bionic/linux: 4.15.0-89.89 -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:
  New
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 Committed
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 verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 13:46 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-aws: bug 1863325
bionic/linux-fips: bug 1863341
bionic/linux-gke-4.15: bug 1863330
bionic/linux-ibm-gt: bug 1863335
bionic/linux-kvm: bug 1863332
bionic/linux-oem: bug 1863312
bionic/linux-oracle: bug 1863339
bionic/linux-raspi2: bug 1863305
bionic/linux-snapdragon: bug 1863310
bionic/linux/pc-kernel: bug 1863301
bionic/linux/pc-lowlatency-kernel: bug 1863302
xenial/linux-azure: bug 1863344
xenial/linux-gcp: bug 1863347
xenial/linux-hwe: bug 1863349
  variant: debs

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

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


[Kernel-packages] [Bug 1863276] Re: bionic/linux-hwe-5.0: 5.0.0-42.46~18.04.1 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-hwe-5.0
main: linux-hwe-5.0
meta: linux-meta-hwe-5.0
signed: linux-signed-hwe-5.0
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 14:53 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
  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/1863276

Title:
  bionic/linux-hwe-5.0: 5.0.0-42.46~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:
  New
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:
  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 verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-hwe-5.0
main: linux-hwe-5.0
meta: linux-meta-hwe-5.0
signed: linux-signed-hwe-5.0
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 14:53 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
  variant: debs

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

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


[Kernel-packages] [Bug 1863274] Re: eoan/linux-azure: 5.3.0-1014.15 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 16:57 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
lrm:depwait,main:queued,meta:building,signed:depwait
+   promote-to-proposed: Pending -- builds not complete in ppa 
lrm:depwait,main:queued,signed:depwait
  trackers:
bionic/linux-azure-5.3: bug 1863273
  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/1863274

Title:
  eoan/linux-azure: 5.3.0-1014.15 -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:
  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 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 --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 16:57 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
lrm:depwait,main:queued,signed:depwait
  trackers:
bionic/linux-azure-5.3: bug 1863273
  variant: debs

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

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


[Kernel-packages] [Bug 1863285] Re: bionic/linux-azure: 5.0.0-1033.35 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 18:16 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  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/1863285

Title:
  bionic/linux-azure: 5.0.0-1033.35 -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:
  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: 1863297
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 18:16 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  variant: debs

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

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


[Kernel-packages] [Bug 1863297] Re: disco/linux: 5.0.0-42.46 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

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

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

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

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

** 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: Promote to Proposed
- phase-changed: Monday, 17. February 2020 13:46 UTC
+ phase: Testing
+ phase-changed: Monday, 17. February 2020 18:32 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:building
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1863281
bionic/linux-azure: bug 1863285
bionic/linux-bluefield: bug 1863295
bionic/linux-gcp: bug 1863289
bionic/linux-gke-5.0: bug 1863293
bionic/linux-hwe-5.0: bug 1863276
bionic/linux-oem-osp1: bug 1863279
bionic/linux-oracle-5.0: bug 1863296
  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/1863297

Title:
  disco/linux: 5.0.0-42.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  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 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: Monday, 17. February 2020 18:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1863281
bionic/linux-azure: bug 1863285
bionic/linux-bluefield: bug 1863295
bionic/linux-gcp: bug 1863289
bionic/linux-gke-5.0: bug 1863293
bionic/linux-hwe-5.0: bug 1863276
bionic/linux-oem-osp1: bug 1863279
bionic/linux-oracle-5.0: bug 1863296
  variant: debs

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

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


[Kernel-packages] [Bug 1863285] Re: bionic/linux-azure: 5.0.0-1033.35 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** 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-lrm
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-lrm
   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: 1863297
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Packaging
- phase-changed: Monday, 17. February 2020 15:56 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Monday, 17. February 2020 18:16 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
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:building,signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  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/1863285

Title:
  bionic/linux-azure: 5.0.0-1033.35 -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:
  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: 1863297
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 18:16 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  variant: debs

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

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


[Kernel-packages] [Bug 1863274] Re: eoan/linux-azure: 5.3.0-1014.15 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 16:57 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:building,main:building,meta:building,signed:building
+   promote-to-proposed: Pending -- builds not complete in ppa 
lrm:depwait,main:queued,meta:building,signed:depwait
  trackers:
bionic/linux-azure-5.3: bug 1863273
  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/1863274

Title:
  eoan/linux-azure: 5.3.0-1014.15 -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:
  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 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 --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 16:57 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
lrm:depwait,main:queued,signed:depwait
  trackers:
bionic/linux-azure-5.3: bug 1863273
  variant: debs

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

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


[Kernel-packages] [Bug 1863290] Re: eoan/linux-oracle: 5.3.0-1010.11 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 17:26 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:building,main:building,meta:building,signed:building
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
  trackers:
bionic/linux-oracle-5.3: bug 1863286
  variant: debs

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

Title:
  eoan/linux-oracle: 5.3.0-1010.11 -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:
  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 verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle 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 --
  kernel-stable-master-bug: 1863294
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 17. February 2020 17:26 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
  trackers:
bionic/linux-oracle-5.3: bug 1863286
  variant: debs

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

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


[Kernel-packages] [Bug 1863294] Re: eoan/linux: 5.3.0-41.33 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 10:59 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
+   promote-to-proposed: Pending -- package copied to Proposed 
signed:retry-needed
  trackers:
bionic/linux-hwe: bug 1863292
eoan/linux-aws: bug 1863272
eoan/linux-azure: bug 1863274
eoan/linux-gcp: bug 1863280
eoan/linux-kvm: bug 1863283
eoan/linux-oracle: bug 1863290
eoan/linux-raspi2: bug 1863269
  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/1863294

Title:
  eoan/linux: 5.3.0-41.33 -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:
  New
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 Committed
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 verification-testing series:
  New
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
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 10:59 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed 
signed:retry-needed
  trackers:
bionic/linux-hwe: bug 1863292
eoan/linux-aws: bug 1863272
eoan/linux-azure: bug 1863274
eoan/linux-gcp: bug 1863280
eoan/linux-kvm: bug 1863283
eoan/linux-oracle: bug 1863290
eoan/linux-raspi2: bug 1863269
  variant: debs

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

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


[Kernel-packages] [Bug 1863350] Re: bionic/linux: 4.15.0-89.89 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 13:46 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:building
  trackers:
bionic/linux-aws: bug 1863325
bionic/linux-fips: bug 1863341
bionic/linux-gke-4.15: bug 1863330
bionic/linux-ibm-gt: bug 1863335
bionic/linux-kvm: bug 1863332
bionic/linux-oem: bug 1863312
bionic/linux-oracle: bug 1863339
bionic/linux-raspi2: bug 1863305
bionic/linux-snapdragon: bug 1863310
bionic/linux/pc-kernel: bug 1863301
bionic/linux/pc-lowlatency-kernel: bug 1863302
xenial/linux-azure: bug 1863344
xenial/linux-gcp: bug 1863347
xenial/linux-hwe: bug 1863349
  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/1863350

Title:
  bionic/linux: 4.15.0-89.89 -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:
  New
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 Committed
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 verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 13:46 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:building
  trackers:
bionic/linux-aws: bug 1863325
bionic/linux-fips: bug 1863341
bionic/linux-gke-4.15: bug 1863330
bionic/linux-ibm-gt: bug 1863335
bionic/linux-kvm: bug 1863332
bionic/linux-oem: bug 1863312
bionic/linux-oracle: bug 1863339
bionic/linux-raspi2: bug 1863305
bionic/linux-snapdragon: bug 1863310
bionic/linux/pc-kernel: bug 1863301
bionic/linux/pc-lowlatency-kernel: bug 1863302
xenial/linux-azure: bug 1863344
xenial/linux-gcp: bug 1863347
xenial/linux-hwe: bug 1863349
  variant: debs

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

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


[Kernel-packages] [Bug 1863338] Re: xenial/linux: 4.4.0-175.205 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 14:48 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:building
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
trusty/linux-aws: bug 1863334
trusty/linux-lts-xenial: bug 1863336
xenial/linux-aws: bug 1863311
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1863331
xenial/linux-kvm: bug 1863319
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1863304
xenial/linux/pc-kernel: bug 1863306
xenial/linux/stlouis-kernel: bug 1863307
  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/1863338

Title:
  xenial/linux: 4.4.0-175.205 -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:
  New
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 Committed
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 verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 17. February 2020 14:48 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
trusty/linux-aws: bug 1863334
trusty/linux-lts-xenial: bug 1863336
xenial/linux-aws: bug 1863311
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1863331
xenial/linux-kvm: bug 1863319
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1863304
xenial/linux/pc-kernel: bug 1863306
xenial/linux/stlouis-kernel: bug 1863307
  variant: debs

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

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


[Kernel-packages] [Bug 1853303] Re: [20.04 FEAT] Enhanced handling of secure keys and protected keys

2020-02-17 Thread Frank Heimes
Patch request submitted:
https://lists.ubuntu.com/archives/kernel-team/2020-February/107542.html
changing status to 'In Progress'.


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

** Information type changed from Private to Public

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

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

Title:
  [20.04 FEAT] Enhanced handling of secure keys and protected keys

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Enhanced handling of secure keys and protected keys in kernel.

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

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


[Kernel-packages] [Bug 1863289] Re: bionic/linux-gcp: 5.0.0-1032.33 -proposed tracker

2020-02-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Ready for Packaging
- phase-changed: Saturday, 15. February 2020 01:39 UTC
+ phase: Packaging
+ phase-changed: Monday, 17. February 2020 18:01 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   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
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1863287
  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/1863289

Title:
  bionic/linux-gcp: 5.0.0-1032.33 -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 verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1863297
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Packaging
  phase-changed: Monday, 17. February 2020 18:01 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
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1863287
  variant: debs

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

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


<    1   2   3   4   5   6   >