Escalated to Field Critical as it now happens often enough to block our
ability to test proposed product releases. We are unable to test
openstack-next at the moment because our test runs fail behind this bug.
--
You received this bug notification because you are a member of Kernel
Packages,
It does seem to have improved in the last update
--
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/1829399
Title:
Lid switch triggered suspend takes much longer than UI triggered
suspend
May 25 08:50:46 Thermia microk8s.daemon-apiserver[7167]: I0525 08:50:46.182335
7167 wrap.go:47] PUT
/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s:
(3.332254ms) 200 [kube-controller-manager/v1.14.1 (linux/amd64)
kubernetes/b739410/leader-election
CEST - state: closed
Fri 17 May 2019 09:49:00 AM CEST - state: open
Fri 17 May 2019 09:49:02 AM CEST - state: open
Fri 17 May 2019 09:49:03 AM CEST - state: open
^C
On Fri, May 17, 2019 at 9:52 AM Chris Gregan
wrote:
> This is interesting.
>
> `echo mem > /sys/power/state`
&g
suspend
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions
>
--
Chris Gregan
Engineering Manager
Solutions QA/Techops
cgre...@irc.canonical.com
--
You received this bug notification because you are a member of Ke
Public bug reported:
IBM T460
5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64
x86_64 GNU/Linux
When triggering a suspend even from the lid switch of my Lenovo T460 it takes
30 seconds to reach suspend state. Several others with different models of
Lenovo laptops
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+attachment/5264256/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Andrei
Since the driver is now part of the kernel, any changes to the driver, and as a
result, the kernel will need to follow the standard upstream kernel patch
process found here:
https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html
--
You received this bug notification
@jsalsbury We are still seeing the issue, given ridsaim has not replied
lets move forward. I'd like to get some movement on this issue without
marking as a Field Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Mark is pressing to potentially change dist upgrade to detect older
firmware versions prior to upgrade to ensure the latest is in place
before Ubuntu upgrade
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
We need to continue to investigate this issue as anyone upgrading a
certified hardware with older firware will be stuck. This will be a bad
user experience.
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member
@Drew
Do you have an update to the request above?
--
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/1757277
Title:
soft lockup from bcache leading to high load and lockup on trusty
Status
** Tags added: cdo-qa-blocker
--
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/1753662
Title:
[i40e] LACP bonding start up race conditions
Status in linux package in Ubuntu:
Triaged
Moved to field critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
bridge activaction error: bridge activation failed | unconfigured
interfaces cause ifup
Kernel 4.4.0-59.80 pushed to cloud and MAAS images and retested on
failing systems.
Failing systems continue to fail
Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: b"no disk with serial 'CVMD51530020400AGN' found\n"
Stderr: ''
Dan,
Bug above, but since you say it is only happening to me, have other tests been
run using MAAS 2.1.2?
--
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/1651602
Title:
[2.1.1] MAAS has
Additional bug opened: https://bugs.launchpad.net/maas/+bug/1653797
--
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/1651602
Title:
[2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails
Dan,
What should be the focus of the new bug? Split off the fact that Denial
cannot be deployed by MAAS? Or is it still related to nvme, just
differently?
On Dec 23, 2016 19:05, "Dan Streetman" <
dan.streetman+launch...@canonical.com> wrote:
> Chris, as your specific problem seems different than
** Attachment added: "syslog_kern.tar.gz"
https://bugs.launchpad.net/maas/+bug/1651602/+attachment/4795854/+files/syslog_kern.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "curtin_config.tar.gz"
https://bugs.launchpad.net/maas/+bug/1651602/+attachment/4795743/+files/curtin_config.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: cdo-qa-blocker
--
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/1651602
Title:
[2.1.1] Yakkety - MAAS has nvme0n1 set as boot disk, curtin fails
Status in MAAS:
New
Public bug reported:
Build Version/Date: Xenial upgraded on 19/2
Environment used for testing: Xenial upgraded from Wily
Summary:
Packages fail to install. The upgrade must be cleaned up manually.
Steps to Reproduce:
1) Install Wily
2) Open terminal and type "update-manager -d"
3) Proceed
22 matches
Mail list logo
