This bug was fixed in the package linux - 4.8.0-37.39
---
linux (4.8.0-37.39) yakkety; urgency=low
[ Thadeu Lima de Souza Cascardo ]
* Release Tracking Bug
- LP: #1659381
* Mouse cursor invisible or does not move (LP: #1646574)
- drm/nouveau/disp/nv50-: split chid into
** Changed in: linux (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Title:
NVMe driver regression for non-smp/1-cpu systems
To manage notific
** Changed in: linux (Ubuntu)
Status: Invalid => Fix Committed
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Project changed: curtin => ubuntu-translations
** No longer affects: ubuntu-translations
** Project changed: maas => ubuntu-translations
** No longer affe
Booted the 4.8.0-36-generic kernel with maxcpus=0 parameter and verified
all NVMe drives were initialized.
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
> Kernel 4.4.0-59.80 pushed to cloud and MAAS images and retested on
failing systems.
Chris, this isn't the right bug for you. Please use your new bug
1653797.
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a
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: ''
This bug was fixed in the package linux - 4.4.0-59.80
---
linux (4.4.0-59.80) xenial; urgency=low
[ John Donnelly ]
* Release Tracking Bug
- LP: #1654282
* [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails (LP: #1651602)
- (fix) nvme: only require 1 interrupt vec
Verified on physical box also, using maxcpus=0, with 4.4.0-58 nvme drive
fails to initialize, with 4.4.0-59 nvme initializes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Title:
NVMe driver
To verify this is fixed, I have done the following.
For good measure, I've also successfully booted the above
with additional parameter '-smp cpus=2'. That verifies that there is no
obvious regression on SMP system.
$
img_url="http://cloud-images.ubuntu.com/daily/server/xenial/current/xenial-ser
** Changed in: maas
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Title:
NVMe driver regression for non-smp/1-cpu systems
To manage notifications about t
** Description changed:
MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.10.1)
Deploying Xenial Nodes
1) Deploy MAAS 2.1.1 on Yakkety
2) Associate Juju 2.1 beta3
3) Juju deploy Kubernetes Core
Nodes begin to deploy but fail
Installation failed with exception: Unexpected error while r
** Summary changed:
- Intel NVMe driver does not expose consistent links in /dev/disk/by-id
+ NVMe driver regression for non-smp/1-cpu systems
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Ti
13 matches
Mail list logo
