[Group.of.nepali.translators] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume

2020-10-20 Thread Balint Reczey 
** Changed in: ec2-hibinit-agent (Ubuntu Xenial)
   Status: Incomplete => Invalid

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

Title:
  xen_netfront devices unresponsive after hibernation/resume

Status in ec2-hibinit-agent package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in ec2-hibinit-agent source package in Xenial:
  Invalid
Status in linux-aws source package in Xenial:
  New
Status in ec2-hibinit-agent source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  New
Status in ec2-hibinit-agent source package in Eoan:
  Fix Released
Status in linux-aws source package in Eoan:
  Won't Fix
Status in ec2-hibinit-agent source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  New

Bug description:
  [Impact]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  [Test Case]

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.

  [Regression Potential]

  The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel 
module before restarting systemd-networkd. If the kernel module is removed (for 
example when hitting LP: #1615381) the module reloading fails and
  the instance can not restore network connections. This is expected to a be 
very rare situation and the module reload is the best workaround the Kernel 
Team found to mitigate the original issue.

  The workaround also adds a 2 second delay before reloading the modules
  to let things settle a bit after resuming. The 2 seconds is very short
  compared to the overall time needed resuming an instance.

  [Original Bug Text]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  A workaround is to build the xen_netfront module separately and
  restart the module and networking during the resume handler. For
  example:

  modprobe -r xen_netfront
  modprobe xen_netfront
  systemctl restart systemd-networkd

  With this workaround in place, the unresponsive issue is no longer
  observed.

  To reproduce this problem:

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-0edf3b95e26a682df
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: m4.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: linux-aws 4.15.0.1058.59
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21
  Tags:  bionic ec2-images
  Uname: Linux 5.0.0-1025-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+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 1899629] Re: [SRU] Please update to upstream release 20200925.00

2020-10-20 Thread Launchpad Bug Tracker 
This bug was fixed in the package google-compute-engine-oslogin -
20200925.00-0ubuntu3

---
google-compute-engine-oslogin (20200925.00-0ubuntu3) groovy; urgency=medium

  * New upstream version 20200925.00 (LP: #1899629)
- Support security key generated OTP challenges
  * Update shared library symlinks

 -- Balint Reczey   Tue, 13 Oct 2020 15:26:47 +0200

** Changed in: google-compute-engine-oslogin (Ubuntu)
   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/1899629

Title:
  [SRU] Please update to upstream release 20200925.00

Status in gce-compute-image-packages package in Ubuntu:
  New
Status in google-compute-engine-oslogin package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Xenial:
  New
Status in google-compute-engine-oslogin source package in Xenial:
  New
Status in gce-compute-image-packages source package in Bionic:
  New
Status in google-compute-engine-oslogin source package in Bionic:
  New
Status in gce-compute-image-packages source package in Focal:
  New
Status in google-compute-engine-oslogin source package in Focal:
  New

Bug description:
  [Impact]

  Google-compute-engine-oslogin is provided by Google for installation
  within guests that run on Google Compute Engine. It part of the
  collection of tools and daemons originally packaged as gce-compute-
  image-packages, that ensure that the Ubuntu images published to GCE
  run properly on their platform.

  Cloud platforms evolve at a rate that can't be handled in six-month
  increments, and they will often develop features that they would like
  to be available to customers who don't want to upgrade from earlier
  Ubuntu releases. As such, updating google-compute-engine-oslogin to
  more recent upstream releases is required within all Ubuntu releases,
  so they continue to function properly in their environment.

  [Test Case]

  When a new version of google-compute-engine-oslogin is uploaded to
  -proposed, the following will be done:

   * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
   * the CPC team will write new automated tests to cover new testable 
functionality (if any) in the new package
   * the automated testing that the CPC team normally runs against GCE images 
before they are published will be run against the -proposed image
   * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

  If all the testing indicates that the image containing the new package
  is acceptable, verification will be considered to be done.

  [Other Information]

  Since google-compute-engine-oslogin is split off from gce-compute-
  image-packages, gce-compute-image-packages should also be updated to
  not build the OS Login package.

  This bug is used for tracking of releasing the new upstream version
  for all supported series, as per the approved policy mentioned in the
  following MRE:

  https://wiki.ubuntu.com/gce-compute-image-packages-Updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1899629/+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 1863242] Re: [SRU] OOM errors with new kernels on resuming

2020-10-20 Thread Balint Reczey 
@fginther Xenial does not need the backport, right?

** Also affects: ec2-hibinit-agent (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: ec2-hibinit-agent (Ubuntu Xenial)
   Status: New => Incomplete

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

Title:
  [SRU] OOM errors with new kernels on resuming

Status in ec2-hibinit-agent package in Ubuntu:
  Fix Released
Status in ec2-hibinit-agent source package in Xenial:
  Incomplete
Status in ec2-hibinit-agent source package in Bionic:
  Fix Released
Status in ec2-hibinit-agent source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * During resuming EC2 instances from hibernation sometimes processes
  are killed OOM manager.

  [Test Case]

   * Set up an EC2 instance to allow hibernation as the stop instance action.
   * Start the attached Python script in a screen session to reserve 85% of the 
memory:
python3 mem-waster-pct.py -p 85

   * Log out, hibernate, then resume the instance.
   * Observe the Python script still running after resuming

  [Regression Potential]

   * The fix is setting memory overcommit policy to 'always overcommit'
  while removing the swap file. This helps dealing with the shrinking
  swap space during the swap removal. There is no expected side effect,
  since processes trying to allocate excessive amount of memory would
  fail with stricter policies, too.

  The fix introduces a potential race condition with processes detecting
  the overcommit policy:

  The policy used when the hibernation took place is saved shortly after
  resuming and it is restored after the swap file is removed. In this
  time window other processes detect the policy as 'always overcommit',
  despite it may not have been set as such before hibernation and may be
  restored to a different policy after removing the swap file. Hitting
  this race condition seems to be unlikely and there seem to be no good
  way of avoiding it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1863242/+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 1864041] Re: xen_netfront devices unresponsive after hibernation/resume

2020-10-20 Thread Balint Reczey 
@fginther Xenial does not need the backport, right?

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

** Also affects: ec2-hibinit-agent (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: ec2-hibinit-agent (Ubuntu Xenial)
   Status: New => Incomplete

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

Title:
  xen_netfront devices unresponsive after hibernation/resume

Status in ec2-hibinit-agent package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in ec2-hibinit-agent source package in Xenial:
  Incomplete
Status in linux-aws source package in Xenial:
  New
Status in ec2-hibinit-agent source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  New
Status in ec2-hibinit-agent source package in Eoan:
  Fix Released
Status in linux-aws source package in Eoan:
  Won't Fix
Status in ec2-hibinit-agent source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  New

Bug description:
  [Impact]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  [Test Case]

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.

  [Regression Potential]

  The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel 
module before restarting systemd-networkd. If the kernel module is removed (for 
example when hitting LP: #1615381) the module reloading fails and
  the instance can not restore network connections. This is expected to a be 
very rare situation and the module reload is the best workaround the Kernel 
Team found to mitigate the original issue.

  The workaround also adds a 2 second delay before reloading the modules
  to let things settle a bit after resuming. The 2 seconds is very short
  compared to the overall time needed resuming an instance.

  [Original Bug Text]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  A workaround is to build the xen_netfront module separately and
  restart the module and networking during the resume handler. For
  example:

  modprobe -r xen_netfront
  modprobe xen_netfront
  systemctl restart systemd-networkd

  With this workaround in place, the unresponsive issue is no longer
  observed.

  To reproduce this problem:

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-0edf3b95e26a682df
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: m4.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: linux-aws 4.15.0.1058.59
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21
  Tags:  bionic ec2-images
  Uname: Linux 5.0.0-1025-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions

___

[Group.of.nepali.translators] [Bug 1890835] Re: secureboot-db 2020 update

2020-10-20 Thread Steve Langasek 
The focal SRU has been rolled back for the time being from focal-updates
to focal-proposed, due to compatibility concerns with current Fedora.

They will be re-released at a later date.  For the time being I am
marking verification-failed to block promotion, but this does not mean
they should be removed from -proposed.

** Changed in: secureboot-db (Ubuntu Focal)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done-focal verification-needed-bionic 
verification-needed-xenial
** Tags added: verification-failed-bionic verification-failed-focal 
verification-failed-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/1890835

Title:
  secureboot-db 2020 update

Status in secureboot-db package in Ubuntu:
  Fix Released
Status in secureboot-db source package in Trusty:
  New
Status in secureboot-db source package in Xenial:
  Fix Committed
Status in secureboot-db source package in Bionic:
  Fix Committed
Status in secureboot-db source package in Focal:
  Fix Committed
Status in secureboot-db source package in Groovy:
  Fix Released

Bug description:
  NB! do not release this update to -updates, until slow phasing is
  available, at 4% per day.

  NB! ideally phase one series at the time, to ensure we can deal with a
  flood of support requests if any arise.

  [Impact]

   * Ship 2020 dbxupdate from MS

  [Test Case]

   * In case of multi-boot systems, please plan to boot into every
  operating system on your multi-boot systems and install updates as
  soon as your other operating system distributions publish updates for
  BootHole vulnerability.

   * Install package on Secureboot UEFI enabled system
   * Reboot
   * Observe that it still reboots

  [Regression Potential]

   * Installing this package even once will update DBX variable in the
  UEFI firmware and will prevent booting:

   - All Ubuntu, Debian, RHEL, Fedora, OpenSUSE, SUSE, Oracle Linux milestones 
/ media released before August 2020
   - Certain version of Kaspersky Labs UEFI protect software
   - Certain version of HPE Inc ProLiant automatic OS provisioning

  As they are all vulnerable to the BootHole vunlerability.

  For example, one will have to use 16.04.7 LTS, 18.04.5 LTS, 20.04.1
  LTS installer media if they want to reinstall.

  If any dual boot configurations are failing to boot, one must
  navigated to UEFI BIOS settings and either reset DBX variables to
  stock values, or disable secureboot. Upgrade any systems that are now
  prohibited to boot. And then re-enable secureboot & reinstall
  secureboot-db package to reapply dbx updates.

  Please note simple downgrade of secureboot-db package will not achieve
  anything, as downgrading the package does not revert the firmware
  changes.

  [Other Info]

   * For more inforamtion please see
  https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1890835/+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 1845178] Re: watchdog bug: soft lockup

2020-10-20 Thread Juerg Haefliger 
** Also affects: linux-raspi2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

Title:
  watchdog bug: soft lockup

Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

Bug description:
  Hello

  I have a Ubuntu Core 16 device (RPi CM3) which sometimes (at random)
  loses ethernet connection.

  Core snap is 16-2.40
  Kernel snap is pi2-kernel 4.4.0-1120.129

  Now I’ve managed to capture serial data from it and it seems it
  crashes completely, however it never restores (or full resets).

  [18037.433255] INFO: rcu_sched self-detected stall on CPU
  [18037.441257] INFO: rcu_sched detected stalls on CPUs/tasks:
  [18037.441264] e[12;17H1-...: (3708966 ticks this GP) 
idle=78d/141/0 softirq=7574/7589 fqs=1588 
  [18037.441270] e[13;17H(detected by 3, t=4495427 jiffies, g=2096, c=2095, 
q=35614)
  [18037.441272] Task dump for CPU 1:
  [18037.441278] manager-control R running  0  2310   2308 0x0082
  [18037.441285] rcu_sched kthread starved for 4493705 jiffies! g2096 c2095 
f0x2 s3 ->state=0x0
  [18037.720278] e[17;17H1-...: (3708966 ticks this GP) 
idle=78d/141/0 softirq=7574/7589 fqs=1588 
  [18037.782050] e[18;17H (t=4495512 jiffies g=2096 c=2095 q=35615)
  [18037.813311] rcu_sched kthread starved for 4493798 jiffies! g2096 c2095 
f0x2 s3 ->state=0x0
  [18037.873341] Task dump for CPU 1:
  [18037.901730] manager-control R running  0  2310   2308 0x0082
  [18037.933017] [<80112554>] (unwind_backtrace) from [<8010d7dc>] 
(show_stack+0x20/0x24)
  [18037.990378] [<8010d7dc>] (show_stack) from [<801571bc>] 
(sched_show_task+0xb8/0x110)
  [18038.048268] [<801571bc>] (sched_show_task) from [<80159a00>] 
(dump_cpu_task+0x48/0x4c)
  [18038.107812] [<80159a00>] (dump_cpu_task) from [<801919b8>] 
(rcu_dump_cpu_stacks+0x9c/0xd4)
  [18038.168554] [<801919b8>] (rcu_dump_cpu_stacks) from [<80195fec>] 
(rcu_check_callbacks+0x5c0/0x8bc)
  [18038.230663] [<80195fec>] (rcu_check_callbacks) from [<8019c3cc>] 
(update_process_times+0x4c/0x74)
  [18038.294469] [<8019c3cc>] (update_process_times) from [<801b04dc>] 
(tick_sched_handle+0x64/0x70)
  [18038.358337] [<801b04dc>] (tick_sched_handle) from [<801b0550>] 
(tick_sched_timer+0x68/0xbc)
  [18038.423493] [<801b0550>] (tick_sched_timer) from [<8019d1b0>] 
(__hrtimer_run_queues+0x188/0x364)
  [18038.490259] [<8019d1b0>] (__hrtimer_run_queues) from [<8019db4c>] 
(hrtimer_interrupt+0xd8/0x244)
  [18038.557715] [<8019db4c>] (hrtimer_interrupt) from [<80743e5c>] 
(arch_timer_handler_phys+0x40/0x48)
  [18038.626525] [<80743e5c>] (arch_timer_handler_phys) from [<8018bd2c>] 
(handle_percpu_devid_irq+0x80/0x194)
  [18038.696876] [<8018bd2c>] (handle_percpu_devid_irq) from [<80186f64>] 
(generic_handle_irq+0x34/0x44)
  [18038.768565] [<80186f64>] (generic_handle_irq) from [<80187270>] 
(__handle_domain_irq+0x6c/0xc4)
  [18038.840084] [<80187270>] (__handle_domain_irq) from [<801096f4>] 
(handle_IRQ+0x28/0x2c)
  [18038.910902] [<801096f4>] (handle_IRQ) from [<801015e4>] 
(bcm2836_arm_irqchip_handle_irq+0xb8/0xbc)
  [18038.982964] [<801015e4>] (bcm2836_arm_irqchip_handle_irq) from 
[<808a3678>] (__irq_svc+0x58/0x78)
  [18039.055005] Exception stack(0xaea2b9d0 to 0xaea2ba18)
  [18039.091313] b9c0: b9e3e01c  
0025 0024
  [18039.161335] b9e0: ae800040  aea2bae4 00011000 aea2bae4 80e0355c 
000b aea2ba2c
  [18039.230628] ba00: aea2ba30 aea2ba20 8027a628 808a2c30 200f0013 
  [18039.267788] [<808a3678>] (__irq_svc) from [<808a2c30>] 
(_raw_spin_lock+0x40/0x54)
  [18039.335854] [<808a2c30>] (_raw_spin_lock) from [<8027a628>] 
(unmap_single_vma+0x1e8/0x64c)
  [18039.404789] [<8027a628>] (unmap_single_vma) from [<8027bab4>] 
(unmap_vmas+0x64/0x78)
  [18039.473309] [<8027bab4>] (unmap_vmas) from [<80282e38>] 
(exit_mmap+0x110/0x214)
  [18039.511274] [<80282e38>] (exit_mmap) from [<80122264>] (mmput+0x6c/0x138)
  [18039.548375] [<80122264>] (mmput) from [<80128a74>] (do_exit+0x32c/0xb38)
  [18039.585148] [<80128a74>] (do_exit) from [<8010db5c>] (die+0x37c/0x38c)
  [18039.621494] [<8010db5c>] (die) from [<8011bee0>] 
(__do_kernel_fault.part.0+0x74/0x1f4)
  [18039.688470] [<8011bee0>] (__do_kernel_fault.part.0) from [<808a40d8>] 
(do_page_fault+0x244/0x3c4)
  [18039.756059] [<808a40d8>] (do_page_fault) from [<80101284>] 
(do_DataAbort+0x58/0xe8)
  [18039.822179] [<80101284>] (do_DataAbort) from [<808a35e4>] 
(__dabt_svc+0x44/0x80)
  [18039.887651] Exception stack(0xaea2bd00 to 0xaea2bd48)
  [18039.921312] bd00: b9f55fc0 0037 0038  b9036000 ad5f32a0 
b9f55fc0 00017000
  [18039.987397] bd20: ae80005c b8af3eec 80e0354c aea2bd6c aea2bd70

[Group.of.nepali.translators] [Bug 1899950] Re: xenial/linux-hwe: 4.15.0-122.124~16.04.1 -proposed tracker

2020-10-20 Thread Ubuntu Kernel Bot 
All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   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/1899950

Title:
  xenial/linux-hwe: 4.15.0-122.124~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
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:
  Invalid
Status in linux-hwe source package in Xenial:
  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: 1899941
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Complete
  phase-changed: Tuesday, 20. October 2020 08:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason: {}
  variant: debs
  versions:
main: 4.15.0-122.124~16.04.1
meta: 4.15.0.122.122
signed: 4.15.0-122.124~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1899950/+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 1899950] Re: xenial/linux-hwe: 4.15.0-122.124~16.04.1 -proposed tracker

2020-10-20 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/promote-to-security
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1899941
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
- phase: Promote to Security
- phase-changed: Tuesday, 20. October 2020 07:48 UTC
+ phase: Complete
+ phase-changed: Tuesday, 20. October 2020 08:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Ongoing -- packages not yet published
+ reason: {}
  variant: debs
  versions:
main: 4.15.0-122.124~16.04.1
meta: 4.15.0.122.122
signed: 4.15.0-122.124~16.04.1

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

Title:
  xenial/linux-hwe: 4.15.0-122.124~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
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:
  Invalid
Status in linux-hwe source package in Xenial:
  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: 1899941
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Complete
  phase-changed: Tuesday, 20. October 2020 08:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason: {}
  variant: debs
  versions:
main: 4.15.0-122.124~16.04.1
meta: 4.15.0.122.122
signed: 4.15.0-122.124~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1899950/+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