[Group.of.nepali.translators] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

2017-09-15 Thread Steve Langasek 
** Changed in: crash (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: kexec-tools (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1712867

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in crash source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

2017-09-15 Thread Launchpad Bug Tracker 
This bug was fixed in the package kexec-tools - 1:2.0.10-1ubuntu2.4

---
kexec-tools (1:2.0.10-1ubuntu2.4) xenial; urgency=medium

  [Marcelo Henrique Cerri]
  * [Hyper-V] 16.04 kexec-tools doesn't match linux-azure (LP: #1712867)
- [PATCH] build_mem_phdrs(): check if p_paddr is invalid
- [PATCH] kexec-tools/x86: get_kernel_vaddr_and_size off-by-one fix
- Increase crashkernel size to 256M for machines with 2G or more of memory.

 -- Stefan Bader   Tue, 12 Sep 2017 09:12:32
+0200

** Changed in: kexec-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1712867

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in crash source package in Xenial:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

2017-09-15 Thread Launchpad Bug Tracker 
This bug was fixed in the package crash - 7.1.4-1ubuntu4.2

---
crash (7.1.4-1ubuntu4.2) xenial; urgency=medium

  [ Marcelo Henrique Cerri ]
  * [Hyper-V] 16.04 kexec-tools doesn't match linux-azure (LP: #1712867)
d/p/0011-Fix-for-Linux-commit-0100301bfdf56a2a370c7157b5ab0fb.patch
d/p/0012-Fix-for-the-ps-t-option-in-3.17-and-later-kernels-th.patch
d/p/0013-Fix-for-the-irq-s-option-for-Linux-4.2-and-later-ker.patch
d/p/0014-Improvement-of-the-accuracy-of-the-allocated-objects.patch
d/p/0015-When-reading-a-task-s-task_struct.flags-field-check-.patch
d/p/0016-Fix-for-Linux-4.8-rc1-commit-500462a9de657f86edaa102.patch
d/p/0017-Improvement-of-the-dev-d-option-to-display-I-O-stati.patch
d/p/0018-Introduction-of-a-new-bt-v-option-that-checks-the-ke.patch
d/p/0019-Fix-for-Linux-4.9-rc1-commits-15f4eae70d365bba26854c.patch
d/p/0020-Fix-for-Linux-4.10-commit-7fd8329ba502ef76dd91db561c.patch
d/p/0021-Prepare-for-the-kernel-s-taint_flag.true-and-taint_f.patch
d/p/0022-Prevent-the-livepatch-taint-flag-check-during-the-sy.patch

 -- Stefan Bader   Tue, 12 Sep 2017 09:15:25
+0200

** Changed in: crash (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1712867

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in crash source package in Xenial:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1715755] Re: linux-azure: persistent memory is not working

2017-09-15 Thread Steve Langasek 
** Also affects: linux-azure (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1715755

Title:
  linux-azure: persistent memory is not working

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Xenial:
  New

Bug description:
  When running opengcs with the linux-azure kernel (4.11.0-1008.8),
  persistent memory doesn't seem to be working.

  A known issue was introduced by 4.11.2, and that might be related to
  the problem:

  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
  stable.git/commit/?h=linux-4.11.y=5a3651b4a92cbc5230d67d2ce87fb3f7373c7665

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1717477] Re: cloud-init generates ordering cycle via After=cloud-init in systemd-fsck

2017-09-15 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init - 0.7.9-280-ge626966e-
0ubuntu1

---
cloud-init (0.7.9-280-ge626966e-0ubuntu1) artful; urgency=medium

  * debian/rules: install rsyslog file with 0644 mode instead of 0755.
  * debian/rules, debian/apport-launcher.py: add an apport hook. (LP: #1607345)
  * New upstream snapshot.
- cmdline: add collect-logs subcommand. [Chad Smith] (LP: #1607345)
- CloudStack: consider dhclient lease files named with a hyphen.
  (LP: #1717147)
- resizefs: Drop check for read-only device file, do not warn on
  overlayroot. [Chad Smith]
- Do not provide systemd-fsck drop-in which could cause ordering cycles.
  [Balint Reczey] (LP: #1717477)
- tests: Enable the NoCloud KVM platform [Joshua Powers]
- resizefs: pass mount point to xfs_growfs [Dusty Mabe]
- vmware: Enable nics before sending the SUCCESS event. [Sankar Tanguturi]
- cloud-config modules: honor distros definitions in each module
  [Chad Smith] (LP: #1715738, #1715690)
- chef: Add option to pin chef omnibus install version
  [Ethan Apodaca] (LP: #1462693)
- tests: execute: support command as string [Joshua Powers]
- schema and docs: Add jsonschema to resizefs and bootcmd modules
  [Chad Smith]
- tools: Add xkvm script, wrapper around qemu-system [Joshua Powers]
- vmware customization: return network config format
  [Sankar Tanguturi] (LP: #1675063)

 -- Scott Moser   Fri, 15 Sep 2017 16:09:07 -0400

** Changed in: cloud-init (Ubuntu Artful)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1717477

Title:
  cloud-init generates ordering cycle via After=cloud-init in systemd-
  fsck

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress
Status in cloud-init source package in Zesty:
  In Progress
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  http://pad.lv/1717477
  https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1717477

  === Begin SRU Template ===
  [Impact]
  Cloud-init's inclusion of a systemd drop-in file
/lib/systemd/system/systemd-fsck@.service.d/cloud-init.conf
  Caused a regression on systems that had entries in /etc/fstab
  that were not authored by cloud-init (specifically that did not have
  something like 'x-systemd.requires=cloud-init.service' in their
  filesystem options.

  [Test Case]
  The test can be done on any cloud that has space to put a non-root
  filesystem.

  a.) launch instance
  b.) upgrade to cloud-init to -updates pocket
  c.) create a filesystem and put it in /etc/fstab
  bdev="/dev/sdb1"
  mkdir -p /mnt
  mkfs.ext4 -F "$bdev"
  echo "$bdev /mnt auto defaults 0 2" >> /etc/fstab

  reboot
  d.) see mention of 'ordering cycle' in journal

  $ journalctl -o short-precise  | grep -i ordering.cycle
  Sep 15 14:08:48.331033 xenial-20170911-174122 systemd[1]: 
local-fs.target: Found ordering cycle on local-fs.target/start
  Sep 15 14:08:48.331097 xenial-20170911-174122 systemd[1]: 
local-fs.target: Breaking ordering cycle by deleting job mnt.mount/start
  Sep 15 14:08:48.331108 xenial-20170911-174122 systemd[1]: mnt.mount: Job 
mnt.mount/start deleted to break ordering cycle starting with 
local-fs.target/start

  e.) upgrade to proposed
  f.) reboot
  g.) expect no mention of ordering cycle as seen in 'd'
  $ journalctl -o short-precise  | grep -i ordering.cycle || echo "no 
cycles"
  no cycles

  [Regression Potential]
  This change will mean that bug 1691489 is present again.
  That bug is much less severe and affects a much smaller set of users.

  [Other Info]
  Upstream commit at
https://git.launchpad.net/cloud-init/commit/?id=a2f8ce9c80

  === End SRU Template ===


  We're running several machines with

    cloud-init_0.7.9-153-g16a7302f-0ubuntu1~16.04.2

  without problems.

  Just upgraded all machines to

    cloud-init_0.7.9-233-ge586fe35-0ubuntu1~16.04.1

  and rebooted them all.

  All machines report ordering cycles in their dmesg, resulting in systemd 
breaking the
  loop by NOT starting some important services, e.g. mouting local filesystems:

  Sep 14 15:43:52.487945 noname systemd[1]: networking.service: Found ordering 
cycle on networking.service/start
  Sep 14 15:43:52.487952 noname systemd[1]: networking.service: Found 
dependency on local-fs.target/start
  Sep 14 15:43:52.487960 noname systemd[1]: networking.service: Found 
dependency on home.mount/start
  Sep 14 15:43:52.487968 noname systemd[1]: networking.service: Found 
dependency on systemd-fsck@dev-disk-by\x2dlabel-Home.service/start
  Sep 14 15:43:52.487975 noname systemd[1]: networking.service: Found 
dependency on

[Group.of.nepali.translators] [Bug 1716620] Re: linux-aws: 4.4.0-1035.44 -proposed tracker

2017-09-15 Thread Stefan Bader 
Manual override, ignoring regression of snapd test (>=2.27.5) which
looks to fail with some ALSA subtest (not sure this ever was supposed to
work on AWS).

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1716620

Title:
  linux-aws: 4.4.0-1035.44 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1716613
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1691489] Re: fstab entries written by cloud-config may not be mounted

2017-09-15 Thread Scott Moser 
** Changed in: cloud-init (Ubuntu Yakkety)
   Status: Confirmed => Won't Fix

** Description changed:

  === Begin SRU Template ===
  [Impact]
  There is a race condition on a re-deployment of cloud-init on Azure
  where /mnt will not get properly formatted or mounted.  This is due to
  "dirty" entries in /etc/fstab that cause a device to be busy when
  cloud-init goes to format it.  This shows itself usually as 'mkfs'
  complaining that the device is busy.  The cause is that systemd
  starts an fsck and collides with cloud-init re-formatting the disk.
  
  The problem can be seen other places but seemed to be most reproducible
  and originally found on Azure.
  
  [Test Case]
  1.) Launch a Azure vm, ideally size L32S.
  2.) Log in and verify the system properly mounted /mnt.
  3.) Re-deploy the vm through the web ui and try again.
  
  [Regression Potential]
- Worst case scenario, these changes unnecessarily slow down boot and 
+ Worst case scenario, these changes unnecessarily slow down boot and
  do not fix the problem.
+ 
+ [Regression]
+ This SRU change caused bug 1717477.
  
  [Other Info]
  Upstream commit at
-   https://git.launchpad.net/cloud-init/commit/?id=1f5489c258
+   https://git.launchpad.net/cloud-init/commit/?id=1f5489c258
  
  === End SRU Template ===
  
- 
- As reported in bug 1686514, sometimes /mnt will not get mounted when 
re-delpoying or stopping-then-starting a Azure vm of L32S.  This is probably a 
more generic issue, I suspect shown due to the speed of disks on these systems.
+ As reported in bug 1686514, sometimes /mnt will not get mounted when re-
+ delpoying or stopping-then-starting a Azure vm of L32S.  This is
+ probably a more generic issue, I suspect shown due to the speed of disks
+ on these systems.
  
  Related bugs:
   * bug 1686514: Azure: cloud-init does not handle reformatting GPT partition 
ephemeral disks
+  * bug 1717477: cloud-init generates ordering cycle via After=cloud-init in 
systemd-fsck

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1691489

Title:
  fstab entries written by cloud-config may not be mounted

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Won't Fix
Status in cloud-init source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  There is a race condition on a re-deployment of cloud-init on Azure
  where /mnt will not get properly formatted or mounted.  This is due to
  "dirty" entries in /etc/fstab that cause a device to be busy when
  cloud-init goes to format it.  This shows itself usually as 'mkfs'
  complaining that the device is busy.  The cause is that systemd
  starts an fsck and collides with cloud-init re-formatting the disk.

  The problem can be seen other places but seemed to be most reproducible
  and originally found on Azure.

  [Test Case]
  1.) Launch a Azure vm, ideally size L32S.
  2.) Log in and verify the system properly mounted /mnt.
  3.) Re-deploy the vm through the web ui and try again.

  [Regression Potential]
  Worst case scenario, these changes unnecessarily slow down boot and
  do not fix the problem.

  [Regression]
  This SRU change caused bug 1717477.

  [Other Info]
  Upstream commit at
    https://git.launchpad.net/cloud-init/commit/?id=1f5489c258

  === End SRU Template ===

  As reported in bug 1686514, sometimes /mnt will not get mounted when
  re-delpoying or stopping-then-starting a Azure vm of L32S.  This is
  probably a more generic issue, I suspect shown due to the speed of
  disks on these systems.

  Related bugs:
   * bug 1686514: Azure: cloud-init does not handle reformatting GPT partition 
ephemeral disks
   * bug 1717477: cloud-init generates ordering cycle via After=cloud-init in 
systemd-fsck

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1691489/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1715586] Re: Fix shrinking behavior in rrCheckPixmapBounding

2017-09-15 Thread Brian Murray 
Hello Kai-Heng, or anyone else affected,

Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.5 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: xorg-server (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: xorg-server (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: xorg-server (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1715586

Title:
  Fix shrinking behavior in rrCheckPixmapBounding

Status in HWE Next:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  When using extended mode on an slave-output connected external monitor, 
RRSetCrtc calls rrCheckPixmapBounding, which shrinks the output area. It makes 
the slave-output configured to scan-out an area which completely falls outside 
of the screen-pixmap, and end up with
  a black display on the external monitor.

  We need these two commits:
  a46afee84d45fbff4e4dad9376afc95bbcc31d7c randr: rrCheckPixmapBounding: do not 
shrink the screen_pixmap
  3b624aa9a9df86dc7d48149e0f18ca223b4355f1 randr: rrCheckPixmapBounding: Do not 
substract crtc non 0 x,y from screen size

  [Test Case]
  Enable NVIDIA PRIME, plug an external monitor, and change to extended mode.

  [Regression Potential]
  There should be none, the shrinking behavior wasn't right at the first place.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1713884] Re: [CIFS] Fix maximum SMB2 header size

2017-09-15 Thread Stefan Bader 
** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1713884

Title:
  [CIFS] Fix maximum SMB2 header size

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  In Progress

Bug description:
  Currently the maximum size of SMB2/3 header is set incorrectly which
  leads to hanging of directory listing operations on encrypted SMB3
  connections. Fix this by setting the maximum size to 170 bytes that
  is calculated as RFC1002 length field size (4) + transform header
  size (52) + SMB2 header size (64) + create response size (56).

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de

  This applies across the board 3.16, 4.4, 4.10, artful, and azure.
  Microsoft would be happy to help test.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1716608] Re: linux-hwe: 4.10.0-35.39~16.04.1 -proposed tracker

2017-09-15 Thread Brad Figg 
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1716608

Title:
  linux-hwe: 4.10.0-35.39~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1716606
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1626984] Re: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!

2017-09-15 Thread Stefan Bader 
For Zesty the change was already applied as "UBUNTU: SAUCE: apparmor: fix 
parameters so that the permission test is bypas
sed at boot" (see bug #1678048) in 4.10.0-17.19 (pre release).

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1626984

Title:
  kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-
  xenial-4.4.0/security/apparmor/include/context.h:69!

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with
  cat /sys/module/apparmor/parameters/audit.

  [  213.174092] [ cut here ]
  [  213.174130] kernel BUG at 
/build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
  [  213.174187] invalid opcode:  [#1] SMP 
  [  213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc 
parport psmouse virtio_scsi floppy
  [  213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic 
#57~14.04.1-Ubuntu
  [  213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
  [  213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 
8800399c4000
  [  213.174419] RIP: 0010:[]  [] 
aa_current_raw_label.part.6+0x4/0x6
  [  213.174478] RSP: 0018:8800399c7d60  EFLAGS: 00010246
  [  213.174506] RAX:  RBX: 88003a426000 RCX: 
88003e3802a0
  [  213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 
88003a426000
  [  213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: 

  [  213.174614] R10: 1000 R11: 0246 R12: 
81e44ae0
  [  213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 
88003c2b2e40
  [  213.174702] FS:  7f7bea106740() GS:88003fc0() 
knlGS:
  [  213.174743] CS:  0010 DS:  ES:  CR0: 80050033
  [  213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 
06f0
  [  213.174819] Stack:
  [  213.174832]  8800399c7d88 8136d58a 88003a426000 
88003a426000
  [  213.174885]  88003e3802a0 8800399c7da0 8136fda2 
88003e39c5f0
  [  213.174928]  8800399c7dd0 8109a7e4 88003c2b2e40 
81a170c0
  [  213.174971] Call Trace:
  [  213.174996]  [] policy_view_capable+0x1ba/0x220
  [  213.175030]  [] param_get_audit+0x12/0x50
  [  213.175062]  [] param_attr_show+0x54/0xa0
  [  213.175092]  [] module_attr_show+0x1d/0x30
  [  213.175130]  [] sysfs_kf_seq_show+0xc2/0x1a0
  [  213.175162]  [] kernfs_seq_show+0x23/0x30
  [  213.175199]  [] seq_read+0xe5/0x350
  [  213.175227]  [] kernfs_fop_read+0x10d/0x170
  [  213.176170]  [] __vfs_read+0x18/0x40
  [  213.177101]  [] vfs_read+0x7f/0x130
  [  213.178016]  [] SyS_read+0x46/0xa0
  [  213.178932]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  213.179814] Code: 80 3d 1a 7f b8 00 00 75 1d 55 be 2e 00 00 00 48 c7 c7 f0 
2f cb 81 48 89 e5 e8 7c 50 cf ff 5d c6 05 fb 7e b8 00 01 c3 55 48 89 e5 <0f> 0b 
b8 01 00 00 00 3e 0f c1 07 ff c0 ff c8 7f 26 80 3d df 7e 
  [  213.182634] RIP  [] aa_current_raw_label.part.6+0x4/0x6
  [  213.183528]  RSP 

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1714420] Re: kernel oops - kvm guest started at boot time

2017-09-15 Thread Stefan Bader 
*** This bug is a duplicate of bug 1710646 ***
https://bugs.launchpad.net/bugs/1710646

Was fixed in upstream stable 4.4.80 as "KVM: PPC: Book3S HV: Reload HTM
registers explicitly". I will mark this bug as duplicate of the stable
tracking bug for reference.

** This bug has been marked a duplicate of bug 1710646
   Xenial update to 4.4.80 stable release

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1714420

Title:
  kernel oops -  kvm guest started at boot time

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

Bug description:
  [SRU Justification]

  [Impact]
  ppc64le system OOPSes shortly after boot when KVM guests are started.

  [Fix]
  Cherry-pick patch e47057151422a67ce08747176fa21cb3b526a2c9

  [Testcase]
  Tested at IBM - boot a machine with a KVM guest configured to start at boot. 
Without this patch, observe OOPS, with this patch, observe no OOPS.

  [Regression Potential]
  Patch is contained in arch/powerpc; so regression potential limited to that 
arch. Patch accepted to kernel stable trees, suggesting others also believe it 
to be of low risk.

  [Original Report]

  [0.00] Linux version 4.4.0-93-generic
  (buildd@bos01-ppc64el-025) (gcc version 5.4.0 20160609 (Ubuntu/IBM
  5.4.0-6ubuntu1~16.04.4) ) #116-Ubuntu SMP Fri Aug 11 16:30:16 UTC 2017
  (Ubuntu 4.4.0-93.116-generic 4.4.79)

  ...
  [  380.184554] KVM guest htab at c0799900 (order 29), LPID 2
  [  380.527576] Facility 'TM' unavailable, exception at 0xd0003aad7f10, 
MSR=90009033
  [  380.527717] Oops: Unexpected facility unavailable exception, sig: 6 [#2]
  [  380.527775] SMP NR_CPUS=2048 NUMA PowerNV
  [  380.527823] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM 
iptable_mangle ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables 
ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user 
xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter 
overlay binfmt_misc bridge stp llc kvm_hv uio_pdrv_genirq uio leds_powernv 
ipmi_powernv ibmpowernv vmx_crypto powernv_rng ipmi_msghandler kvm_pr kvm 
autofs4 xfs btrfs raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 raid10 ses 
enclosure mlx4_en be2net lpfc vxlan mlx4_core scsi_transport_fc ip6_udp_tunnel 
udp_tunnel ipr
  [  380.528781] CPU: 24 PID: 4277 Comm: qemu-system-ppc Tainted: G  D  
   4.4.0-93-generic #116-Ubuntu
  [  380.528861] task: c3c389b0 ti: c01fb2428000 task.ti: 
c01fb2428000
  [  380.528929] NIP: d0003aad7f10 LR: d00037d52a14 CTR: 
d0003aad7e40
  [  380.528997] REGS: c01fb242b7b0 TRAP: 0f60   Tainted: G  D  
(4.4.0-93-generic)
  [  380.529076] MSR: 90009033   CR: 22024848  
XER: 
  [  380.529247] CFAR: d0003aad7ea4 SOFTE: 1
     GPR00: d00037d52a14 c01fb242ba30 d0003aaec018 
c01fdbf6
     GPR04: c01f8580 c01fb242bbc0  

     GPR08: 0001 c3c389b0 0001 
d00037d578f8
     GPR12: d0003aad7e40 cfb4e400  
001f
     GPR16: 3fff7206 0080 3fff892c4390 
3fff7285f200
     GPR20: 010009988430 0100099affd0 3fff7285eb60 
100c1ff0
     GPR24: 3bcf4e10 3fff72040028  
c01fdbf6
     GPR28:  c01f8580 c01fdbf6 
c01f8580
  [  380.530119] NIP [d0003aad7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv]
  [  380.530188] LR [d00037d52a14] kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  380.530245] Call Trace:
  [  380.530270] [c01fb242ba30] [c01fb242bab0] 0xc01fb242bab0 
(unreliable)
  [  380.530353] [c01fb242bb70] [d00037d52a14] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  380.530436] [c01fb242bba0] [d00037d4f674] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
  [  380.530519] [c01fb242bbe0] [d00037d43918] 
kvm_vcpu_ioctl+0x528/0x7b0 [kvm]
  [  380.530602] [c01fb242bd40] [c02fff60] do_vfs_ioctl+0x480/0x7d0
  [  380.530671] [c01fb242bde0] [c0300384] SyS_ioctl+0xd4/0xf0
  [  380.530742] [c01fb242be30] [c0009204] system_call+0x38/0xb4
  [  380.530837] Instruction dump:
  [  380.530904] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 
e9290108
  [  380.531126] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 
e92d02a0 7d4122a6
  [  380.531350] ---[ end trace 8f9b3b82f9a07d76 ]---

  Needs kernel patch

[Group.of.nepali.translators] [Bug 1717306] Re: waalinuxagent 2.2.17

2017-09-15 Thread Launchpad Bug Tracker 
This bug was fixed in the package walinuxagent - 2.2.17-0ubuntu1

---
walinuxagent (2.2.17-0ubuntu1) artful; urgency=medium

  * New upstream release (LP: #1717306).

 -- Łukasz 'sil2100' Zemczak   Fri, 15 Sep
2017 12:42:50 +0200

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1717306

Title:
  waalinuxagent 2.2.17

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  New
Status in walinuxagent source package in Xenial:
  New
Status in walinuxagent source package in Zesty:
  New

Bug description:
  [Impact]
  This release contains both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/walinuxagentUpdates

  The Microsoft Azure Linux Agent team will execute their testsuite, which
  includes extension testing , against the walinuxagent that is in
  -proposed. A successful run will be required before the proposed walinuxagent
  can be let into -updates.

  The CPC team will be in charge of attaching a summary of testing to the bug. 
CPC team members will not
  mark ‘verification-done’ until this has happened.

  [Original Description]

  Hi,
  Please can you take the 2.2.17 release, package and merge into images.

  https://github.com/Azure/WALinuxAgent/releases

  This includes one fix to address:
  https://github.com/Azure/WALinuxAgent/issues/879

  Thanks,

  Dan

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1708852] Re: Touchpad not detected

2017-09-15 Thread Stefan Bader 
** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

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

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

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1708852

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justifications:

  [Impact] 
  Touchpad on Lenovo ideapad 320-14IKB does not work.

  [Test Case]
  After adding the ID to the elan_i2c driver, the touchpad works.

  
  [Regression Potential]
  Very low.
  It only adds device ID to the driver, no functional changes.

  ---

  The touchpad is not working in any linux distribution, but works in
  Windows. It is not getting detected. Seems like a kernel bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-30-generic 4.10.0-30.34
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matheus1504 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Aug  5 12:58:21 2017
  InstallationDate: Installed on 2017-08-05 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:1127 Acer, Inc
   Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc.
   Bus 001 Device 002: ID 0101:0007
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80YF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed 
root=UUID=d7c89f65-c9a7-4e7f-9bce-ed58751f0619 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-30-generic N/A
   linux-backports-modules-4.10.0-30-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN16WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 4A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-14IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN16WW:bd02/22/2017:svnLENOVO:pn80YF:pvrLenovoideapad320-14IKB:rvnLENOVO:rnCairo4A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14IKB:
  dmi.product.name: 80YF
  dmi.product.version: Lenovo ideapad 320-14IKB
  dmi.sys.vendor: LENOVO

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1713553] Re: Intel i40e PF reset due to incorrect MDD detection

2017-09-15 Thread Stefan Bader 
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1713553

Title:
  Intel i40e PF reset due to incorrect MDD detection

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

Bug description:
  [Impact]

  Using an Intel i40e network device, under heavy traffic load with
  TSO enabled, the device will spontaneously reset itself and issue errors
  similar to the following:

  Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX 
driver issue detected, PF reset issued

   This causes a full reset of the PF, which causes an interruption
  in traffic flow.

  This was partially fixed by Xenial commit
  12f8cc59d5886b86372f45290166deca57a60d7a, however there is one
  additional upstream commit required to fully fix the issue:

  commit 841493a3f64395b60554afbcaa17f4350f90e764
  Author: Alexander Duyck 
  Date:   Tue Sep 6 18:05:04 2016 -0700

  i40e: Limit TX descriptor count in cases where frag size is
  greater than 16K

   This fix was never backported into the Xenial 4.4 kernel series, but
  is already present in the Xenial HWE (and Zesty) 4.10 kernel.

  [Testcase]

   In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled. Under heavy load, the card will
  reset itself as described.

  [Regression Potential]

  As with any change to a network card driver, this may cause
  regressions with network I/O through i40e card(s).  However, this
  specific change only increases the likelyhood that any specific large
  TSO tx will need to be linearized, which will avoid the PF reset.
  Linearizing a TSO tx that did not need to be linearized will not cause
  any failures, it may only decrease performance slightly.  However this
  patch should only cause linearization when required to avoid the MDD
  detection and PF reset.

  [Other Info]

  The previous bug for this issue is bug 1700834.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1716622] Re: linux-kvm: 4.4.0-1007.12 -proposed tracker

2017-09-15 Thread Po-Hsu Lin 
Not testing this in this cycle.

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1716622

Title:
  linux-kvm: 4.4.0-1007.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-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1716613
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1716618] Re: linux-raspi2: 4.4.0-1074.82 -proposed tracker

2017-09-15 Thread Brad Figg 
** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1716618

Title:
  linux-raspi2: 4.4.0-1074.82 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1716613
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1715812] Re: Neighbour confirmation broken, breaks ARP cache aging

2017-09-15 Thread Stefan Bader 
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1715812

Title:
  Neighbour confirmation broken, breaks ARP cache aging

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New

Bug description:
  [SRU Justification]

  [Impact]
  A host can lose access to another host whose MAC address changes if they have 
active connections to other hosts that share a route. The ARP cache does not 
time out as expected - instead the old MAC address is continuously reconfirmed.

  [Fix]
  Apply series [1], which changes the algorithm for neighbour confirmation.
  That is, from upstream:
  51ce8bd4d17a net: pending_confirm is not used anymore 
  0dec879f636f net: use dst_confirm_neigh for UDP, RAW, ICMP, L2TP 
  63fca65d0863 net: add confirm_neigh method to dst_ops 
  c3a2e8370534 tcp: replace dst_confirm with sk_dst_confirm 
  c86a773c7802 sctp: add dst_pending_confirm flag 
  4ff0620354f2 net: add dst_pending_confirm flag to skbuff 
  9b8805a32559 sock: add sk_dst_pending_confirm flag 

  [Test case]
  Create 3 real or virtual systems, all hooked up to a switch.
  One system needs an active-backup bond with fail_over_mac=1 num_grat_arp=0.

  Put all the systems in the same subnet, e.g. 192.168.200.0/24

  Call the system with the bond A, and the other two systems B and C.

  On B, run in 3 shells:
   - netperf -t TCP_RR to C
   - ping -f A
   - watch 'ip -s neigh show 192.168.200.0/24'

  On A, cause the bond to fail over.

  Observe that:

   - without the patches, B intermittently fails to notice the change in
  A's MAC address. This presents as the ping failing and not recovering,
  and the arp table showing the old mac address never timing out and
  never being replace with a new mac address.

   - with the patches, the arp cache times out and B sends another mac
  probe and detects A's new address.

  It helps to use taskset to put ping and netperf on the same CPU, or
  use single-CPU vms.

  See [2] for more details.

  [References]
  [2] Original report: 
https://www.mail-archive.com/netdev@vger.kernel.org/msg138762.html
  [1]: https://www.spinics.net/lists/linux-rdma/msg45907.html

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp