[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-06 Thread Dan Streetman
** Patch added: "lp1647485-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788140/+files/lp1647485-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-06 Thread Dan Streetman
** Patch added: "lp1647485-yakkety.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788138/+files/lp1647485-yakkety.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-06 Thread Dan Streetman
** Patch added: "lp1647485-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788139/+files/lp1647485-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-06 Thread Dan Streetman
debdiffs added for t/x/y/z that add all 3 patches proposed in the upstream bug, that: -change udev to replace spaces in all SYMLINK values by default (unless option string_escape=none is used by a rule) -update test/udev-test.pl test case to use string_escape=none option for test cases that use

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-12 Thread Dan Streetman
> Note that there is not much point with debdiffs, it's easier to cherry-pick > the fix directly into > the packaging branches with gbp pq and debian/git-cherry-pick. ok, I removed the debdiffs as they're not needed. I did attach a single patch, that works around the bug in a simple way, by

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-12 Thread Dan Streetman
** Patch removed: "lp1647485-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788261/+files/lp1647485-trusty.debdiff ** Patch removed: "lp1647485-xenial.debdiff"

[Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

2016-12-12 Thread Dan Streetman
> Note that there is a current SRU in trusty which blocks this. is that current SRU for bug 1562344? > But this being "wishlist" it's not > that urgent anyway, This isn't really wishlist, this is needed to persistently identify NVMe drives on systems with multiple drives. > and my gut feeling

[Bug 1372368] Re: VM creation fails on Utopic/Trusty

2016-12-14 Thread Dan Streetman
> Please fix. fixed ** Description changed: [impact] "uvt-kvm create foo" produces the error: uvt-kvm: error: libvirt: internal error: process exited while connecting to monitor: 2014-09-22T09:27:46.422743Z qemu-system-x86_64: -drive

[Bug 1647887] Re: NVMe driver accidentally reverted to use GSI instead of MSIX

2016-12-14 Thread Dan Streetman
I verified kernel linux-image-generic 4.4.0.57.60 (uname 4.4.0-57-generic #78-Ubuntu) does fix this. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1648449] Re: NVMe drives in Amazon AWS instance fail to initialize

2016-12-14 Thread Dan Streetman
I verified kernel linux-image-generic 4.4.0.57.60 (uname 4.4.0-57-generic #78-Ubuntu) does fix this. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1639920] Re: NVMe detection failed during bootup

2016-12-14 Thread Dan Streetman
*** This bug is a duplicate of bug 1647887 *** https://bugs.launchpad.net/bugs/1647887 Please note, this is fixed in kernel 4.4.0.57.60, which is in -proposed right now. See bug 1647887 for more details. -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1640275] Re: move nvme driver to linux-image

2016-12-12 Thread Dan Streetman
I upgraded to kernel 3.13.0-106-generic and verified the nvme module is included in the linux-image package. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1649635] [NEW] export nvme drive model/serial strings via sysfs (trusty)

2016-12-13 Thread Dan Streetman
file creation using device_create_file(), which the upstream code never did. This is by far the simplest way to update this very old kernel with the functionality. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Dan Streetman (ddstreet) Status: Incomplete ** Tags

[Bug 1649635] Re: export nvme drive model/serial strings via sysfs

2016-12-13 Thread Dan Streetman
This is relevant for trusty only; the nvme driver in xenial and later already exports the model/serial strings via sysfs. ** Summary changed: - export nvme drive model/serial strings via sysfs + export nvme drive model/serial strings via sysfs (trusty) -- You received this bug notification

[Bug 1647887] [NEW] NVMe driver accidentally reverted to use GSI instead of MSIX

2016-12-06 Thread Dan Streetman
Public bug reported: [Impact] These commit ids are in the xenial kernel branch. Commit 90c9712fbb388077b5e53069cae43f1acbb0102a ("NVMe: Always use MSI/MSI-x interrupts") changed the NVMe driver to always use MSI/MSI-x interrupts. However, later commit 30d6592fce71beabe18460252c3823747c4742f6

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-06 Thread Dan Streetman
** Patch added: "lp1647485-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788261/+files/lp1647485-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-06 Thread Dan Streetman
This tarball contains debdiffs for x/y/z that *workaround* - not fix - the problem, by adding the string_escape=replace option to the NVMe rules that create the model/serial symlinks. This is possible as a temporary alternative to the real fix to udev. Unlike the real fix, which will change the

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-06 Thread Dan Streetman
** Patch added: "lp1647485-yakkety.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788263/+files/lp1647485-yakkety.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-06 Thread Dan Streetman
debdiffs updated to include (LP: #1647485) in changelog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647485 Title: NVMe symlinks broken by devices with spaces in model or serial strings To

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-06 Thread Dan Streetman
** Patch added: "lp1647485-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788262/+files/lp1647485-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-06 Thread Dan Streetman
** Patch added: "lp1647485-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788264/+files/lp1647485-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-06 Thread Dan Streetman
https://github.com/systemd/systemd/issues/4833 ** Bug watch added: github.com/systemd/systemd/issues #4833 https://github.com/systemd/systemd/issues/4833 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1640293] Re: Backport graphical-session{,-pre}.target to xenial

2016-12-14 Thread Dan Streetman
I verified this does add the targets, without enabling them. with systemd 229-4ubuntu7: ubuntu@lp1640293:~$ systemctl --user status graphical-session{,-pre}.target ● graphical-session.target Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) ●

[Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

2016-12-14 Thread Dan Streetman
I added the 2 commits referenced in the docker thread: https://github.com/docker/docker/issues/5618#issuecomment-262081488 which is building right now in the test ppa: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1403152 kernel version 4.4.0-53.74+hf1403152v20161214b1 is the latest xenial

[Bug 1518457] Re: kswapd0 100% CPU usage

2016-12-14 Thread Dan Streetman
> I can see it every now and then with Yakkety and linux 4.8.0-27. > Can you advice any action? what do you mean by "every now and then"? you mean kswapd runs at 100% for a short time, occasionally? that's normal. > kswapd0 no longer takes 100% CPU, but it still emerges to the top of the list

[Bug 1647887] Re: NVMe driver accidentally reverted to use GSI instead of MSIX

2016-12-07 Thread Dan Streetman
Note: this problem isn't in yakkety or zesty, no backporting of these particular NVMe patches was needed for those kernels, as the commits were already included in the kernel they are based on. This is an issue only in the xenial kernel. (of course the precise/trusty kernels are far too old for

[Bug 1648449] Re: NVMe drives in Amazon AWS instance fail to initialize

2017-01-13 Thread Dan Streetman
** Changed in: linux (Ubuntu Zesty) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648449 Title: NVMe drives in Amazon AWS instance fail to initialize To

[Bug 1648449] Re: NVMe drives in Amazon AWS instance fail to initialize

2017-01-13 Thread Dan Streetman
It appears these workaround patches introduced NVMe initialization problems on some non-Xen systems, see bug 1626894. I sent patches to revert this for xenial and yakkety. Instead, this problem should be fixed by a patch to Xen kernel code, in bug 1656831. ** Changed in: linux (Ubuntu)

[Bug 1626894] Re: nvme drive probe failure

2017-01-13 Thread Dan Streetman
Guillaume, roots, Stéphane, can you also test with my PPA kernel from comment 30? It would help to know if your NVMe failures are also due to the patches we're reverting, or some other problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1656381] [NEW] Xen MSI setup code incorrectly re-uses cached pirq

2017-01-13 Thread Dan Streetman
. That should restore functionality for non-Xen systems, and should allow Xen systems with multiple NVMe controllers to work. ** Affects: linux (Ubuntu) Importance: High Assignee: Dan Streetman (ddstreet) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) =>

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-13 Thread Dan Streetman
Yakkety: with udev 231-9ubuntu2, the /dev/disk/by-id/ NVMe symlinks were not created correctly: $ ls -l /dev/disk/by-id/ total 0 lrwxrwxrwx 1 root root 13 Jan 13 22:34 nvme-Amazon -> ../../nvme2n1 and with udev 231-9ubuntu3, the /dev/disk/by-id/ NVMe symlinks are created correctly: $ ls -l

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-13 Thread Dan Streetman
Xenial: with udev 229-4ubuntu13, the /dev/disk/by-id/ NVMe symlinks were not correctly created: $ ls -l /dev/disk/by-id/ total 0 lrwxrwxrwx 1 root root 13 Jan 13 22:01 nvme-Amazon -> ../../nvme0n1 and with udev 229-4ubuntu15 from -proposed, the /dev/disk/by-id/ NVMe symlinks were correctly

[Bug 1626894] Re: nvme drive probe failure

2017-01-13 Thread Dan Streetman
** Changed in: linux (Ubuntu Xenial) Assignee: Kamal Mostafa (kamalmostafa) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-09 Thread Dan Streetman
Regarding the workaround patch from comment 17, I should note that the workaround involves replacing all whitespace in the NVMe model or serial string with underscores. This matches what is done for the by-id symlinks for scsi, ata, and all other buses. However, another possibility is instead of

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-12 Thread Dan Streetman
My pull request has been merged upstream, the commits are: 0a10235 udev-rules: perform whitespace replacement for symlink subst values e20a917 udev-event: add replace_whitespace param to udev_event_apply_format a9d99b3 libudev-util: change util_replace_whitespace to return number of chars in

[Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

2017-01-12 Thread Dan Streetman
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642903 Title: introduce disk/by-id (model_serial) symlinks for NVMe drives To

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-12 Thread Dan Streetman
** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851164 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647485

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-12 Thread Dan Streetman
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851164 ** Bug watch added: Debian Bug tracker #851164 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851164 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-12 Thread Dan Streetman
Pull request for trusty: https://code.launchpad.net/~ddstreet/+git/systemd/+ref/trusty Pull request for xenial: https://code.launchpad.net/~ddstreet/+git/systemd/+ref/xenial Yakkety can use the same patches as Xenial. Zesty can use the same patches as upstream (from github, listed in comment

[Bug 1626894] Re: nvme drive probe failure

2017-01-12 Thread Dan Streetman
Alternately, as this may have been caused by my recent NVMe patches, can those affeected by this please test with this kernel PPA which is 4.4.0-59 with my patches reverted: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1626894 -- You received this bug notification because you are a member

[Bug 1651602] Re: NVMe driver regression for non-smp/1-cpu systems

2017-01-12 Thread Dan Streetman
> 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

[Bug 1639920] Re: NVMe detection failed during bootup

2016-11-30 Thread Dan Streetman
. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639920 Title: NVMe detection failed during bootup To man

[Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

2016-12-02 Thread Dan Streetman
for NetworkManager, this is fixed starting in wily (see comment 13) and so should work in xenial/yakkety; and in trusty, dhclient still works (per description stating dhclient works in isc-dhcp-client 4.2.4-7ubuntu14). I'm not sure if NetworkManager using dhcpv6 works in precise (but who is using

[Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

2016-12-05 Thread Dan Streetman
I verified that the -proposed package does create the NVMe disk/by-id/ serial number symlink for each drive. However, there's unfortunately a bug in the way it does it, which still exists upstream. I opened this upstream udev bug for the problem: https://github.com/systemd/systemd/issues/4833

[Bug 1647485] [NEW] NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-05 Thread Dan Streetman
Public bug reported: [Impact] After including the patch from bug 1642903, NVMe devices that include spaces in their model or serial strings result in incorrect symlinks, e.g. if the model string is "XYZ Corp NVMe drive" then instead of creating: /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL

[Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

2016-12-05 Thread Dan Streetman
I opened bug 1647485 to track the spaces-in-symlink-value problem. Separate from that bug, I have verified the -proposed udev package creates the /dev/disk/by-id/ model/serial string symlinks. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-05 Thread Dan Streetman
** Tags added: sts sts-sponsor sts-sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647485 Title: NVMe symlinks broken by devices with spaces in model or serial strings To manage notifications

[Bug 1639920] Re: NVMe detection failed during bootup

2016-12-02 Thread Dan Streetman
Hi Dexter, before I jump onto the system to debug, can you try this test kernel: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1639920 I think that might fix the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1651602] Re: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails

2017-01-03 Thread Dan Streetman
> What should be the focus of the new bug? I don't know why it doesn't work on your system, as it does work on mine, so I can't tell you what to put in the new bug. Since your system is smp with 2 or more cpus, it doesn't appear to be the same as this bug (since this bug was taken over after you

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-03 Thread Dan Streetman
** Patch removed: "workaround-use-string_escape-release-for-nvme-symlin.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4790906/+files/workaround-use-string_escape-release-for-nvme-symlin.patch ** Patch added:

[Bug 1518457] Re: kswapd0 100% CPU usage

2017-01-03 Thread Dan Streetman
This bug is fixed released already, any new problems should be opened in a new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518457 Title: kswapd0 100% CPU usage To manage notifications

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-03 Thread Dan Streetman
patch filename and Subject: had 'string_escape=release', fixed to 'string_escape=replace'. Actual patch contents were correct and aren't changed in this patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-05 Thread Dan Streetman
Note: the workaround patch from comment 17 *will not* conflict with whatever fix is implemented upstream. The patch changes *only* the NVMe rules to force whitespace replacement. If upstream changes the default behavior, to replace whitespace, then this workaround patch becomes

[Bug 1651602] Re: NVMe driver regression for non-smp/1-cpu systems

2017-01-09 Thread Dan Streetman
** 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

[Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

2017-01-09 Thread Dan Streetman
** Description changed: [Impact] NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme-SERIAL symlinks. [Test Case] On a system with an NVMe drive, check the /dev/disk/by-id/ directory; with the patch, it will contain link(s) named by the drive serial number.

[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-09 Thread Dan Streetman
** Description changed: [Impact] After including the patch from bug 1642903, NVMe devices that include spaces in their model or serial strings result in incorrect symlinks, e.g. if the model string is "XYZ Corp NVMe drive" then instead of creating: /dev/disk/by-id/nvme-XYZ Corp NVMe

[Bug 1651602] Re: Intel NVMe driver does not expose consistent links in /dev/disk/by-id

2017-01-06 Thread Dan Streetman
> But mostly, I would argue that this is a bug in the Intel NVMe driver. You're commenting in the wrong bug. This bug is already being addressed. Please go over to bug 1653797 ** Changed in: curtin Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Incomplete =>

[Bug 1651602] Re: NVMe driver regression for non-smp/1-cpu systems

2017-01-09 Thread Dan Streetman
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

[Bug 1651602] Re: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails

2016-12-23 Thread Dan Streetman
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) -- 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: [2.1.1] MAAS has nvme0n1 set as boot d

[Bug 1651602] Re: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails

2016-12-23 Thread Dan Streetman
I tested on my nvme system with the boot param 'maxcpus=0' (i.e. UP mode), the boot fails with kernel 4.4.0-57, because the nvme drive fails enumeration, with the error from comment 2. With the 4.4.0-57 kernel including my nvme patch, and using boot param 'maxcpus=0', the boot succeeds. The

[Bug 1651602] Re: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails

2016-12-23 Thread Dan Streetman
Chris, as your specific problem seems different than the 1-cpu NVMe bug that the rest of this bug describes, and my patch fixes, can you open a new bug please. ** Changed in: maas Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1651602] Re: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails

2016-12-23 Thread Dan Streetman
I built a test kernel with this fix applied to the 4.4.0-57 kernel, available here: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1651602 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651602

[Bug 1649635] Re: export nvme drive model/serial strings via sysfs (trusty)

2016-12-22 Thread Dan Streetman
:47 nvme0n4/device/serial ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs, wh

[Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

2016-12-20 Thread Dan Streetman
Scott, while this is a linux-specific change (and not applicable to upstream isc-dhcp itself), it doesn't look like this fix is upstream in debian; have you opened a bug there and/or are you planning to push it up? -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-03-21 Thread Dan Streetman
Ok, I figured out the problem. You're using the yakkety kernel, 4.8. In the Xenial 4.4 kernel, memory hotplug auto-onlining is disabled; however in the 4.8 kernel, memory hotplug auto-onlining is enabled, so disabling the udev rule with the 4.8 kernel does nothing - the kernel's already onlined

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-03-30 Thread Dan Streetman
Marking this as 'invalid' for ifupdown, as the problem is in the vlan package's script. ** Also affects: vlan (Ubuntu) Importance: Undecided Status: New ** Changed in: vlan (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: vlan (Ubuntu) Importa

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-03-30 Thread Dan Streetman
Thanks everyone, I'll work on getting the patch upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot To

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-03-30 Thread Dan Streetman
** Description changed: - Expectation: After reboot, route for default gateway specified on - bonded interface is installed according to "gateway x.x.x.x" (where - x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or - files sourced per /etc/network/interfaces + [Impact] +

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-03-30 Thread Dan Streetman
I created a PPA with fixed vlan packages: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1573272 ** Tags removed: bot-comment patch xenial ** Tags added: sts-sponsor ** Tags added: patch ** Also affects: vlan (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-03-30 Thread Dan Streetman
** Patch added: "lp1573272-yakkety.debdiff" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850619/+files/lp1573272-yakkety.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-03-30 Thread Dan Streetman
** Patch added: "lp1573272-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850617/+files/lp1573272-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-03-30 Thread Dan Streetman
** Patch added: "lp1573272-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850618/+files/lp1573272-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-03-30 Thread Dan Streetman
** Patch added: "lp1573272-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850620/+files/lp1573272-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-03-30 Thread Dan Streetman
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127 ** Bug watch added: Debian Bug tracker #859127 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1453330] Re: pull-{lp, debian}-source not getting source for binary because DDE is dead

2017-03-29 Thread Dan Streetman
Yep, I just changed it to work-in-progress, until i finish updating it so pull-debian-* works also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453330 Title: pull-{lp,debian}-source not getting

[Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-03-29 Thread Dan Streetman
** Changed in: linux-aws (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668129 Title: Amazon I3 Instance Buffer I/O error on dev nvme0n1 To

[Bug 1453330] Re: pull-{lp, debian}-source not getting source for binary because DDE is dead

2017-03-17 Thread Dan Streetman
** Tags removed: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453330 Title: pull-{lp,debian}-source not getting source for binary because DDE is dead To manage notifications about

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-03-16 Thread Dan Streetman
ifup $IF_VLAN_RAW_DEVICE vconfig add $IF_VLAN_RAW_DEVICE $VLANID fi fi ** Changed in: ifupdown (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-03-16 Thread Dan Streetman
I set up a default xenial vm with 2 extra interfaces, and configured them with exactly the config you listed in the description, and left it in a reboot loop checking for the default gateway each time, and it hasn't seen the problem at all, after hours of rebooting. Is there a something else

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-03-16 Thread Dan Streetman
Ok I've reproduced this by introducing a delay by changing /lib/systemd/system/ifup@.service -ExecStart=/bin/sh -ec 'ifup --allow=hotplug %I; ifup --allow=auto %I; \ +ExecStart=/bin/sh -ec '/usr/bin/test %I == bond0 && echo found bond0 && sleep 3 ; ifup --allow=hotplug %I; ifup --allow=auto %I;

[Bug 1453330] Re: pull-{lp, debian}-source not getting source for binary because DDE is dead

2017-03-17 Thread Dan Streetman
Iain, you created pull-lp-source, can you review this merge request? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453330 Title: pull-{lp,debian}-source not getting source for binary because DDE

[Bug 1453330] Re: pull-{lp, debian}-source not getting source for binary because DDE is dead

2017-03-14 Thread Dan Streetman
Merge proposal created: https://code.launchpad.net/~ddstreet/ubuntu-dev-tools/lp1453330/+merge/319865 ** Branch linked: lp:~ddstreet/ubuntu-dev-tools/lp1453330 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1453330] Re: pull-{lp, debian}-source not getting source for binary because DDE is dead

2017-03-14 Thread Dan Streetman
Dmitry, as you're following this bug and you have devel access to merge it, can you review/merge the change? ** Tags added: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453330 Title:

[Bug 1672470] Re: ip_rcv_finish() NULL pointer kernel panic

2017-03-17 Thread Dan Streetman
** Description changed: + [Impact] + + When using iptables rules affecting bridge traffic, and if affected + traffic is flowing through bridge while br_netfilter module is loaded or + unloaded, a kernel panic may occur. + + [Test Case] + + It's difficult to reproduce because of a very small

[Bug 1672470] Re: ip_rcv_finish() NULL pointer kernel panic

2017-03-17 Thread Dan Streetman
Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubu

[Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-03-21 Thread Dan Streetman
Patrick, does this command return any results: $ grep 0 /sys/devices/system/memory/memory*/online -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668129 Title: Amazon I3 Instance Buffer I/O error

[Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-03-21 Thread Dan Streetman
Also, $ grep memory /lib/udev/rules.d/* /etc/udev/rules.d/* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668129 Title: Amazon I3 Instance Buffer I/O error on dev nvme0n1 To manage notifications

[Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-03-21 Thread Dan Streetman
And, rebuild your initramfs, to make sure it doesn't have a stale udev rule in it (although mine doesn't contain the memory hotadd udev rule): $ sudo update-initramfs -u -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

2017-04-04 Thread Dan Streetman
> I don't know if it's related but since the I'm using this vlan package I have this issue: it's hard to tell just from that output, what does your interfaces file(s) look like? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1453330] Re: pull-{lp, debian}-source not getting source for binary because DDE is dead

2017-03-31 Thread Dan Streetman
in my git repo in the branch 'pull-lp': https://code.launchpad.net/~ddstreet/+git/ubuntu-dev-tools/+ref/pull-lp ** Changed in: ubuntu-dev-tools (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs, wh

[Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-04-06 Thread Dan Streetman
I'm not sure when a new AMI build is scheduled, but you can 'sudo apt install linux-aws' currently in an existing xenial instance to upgrade to the AWS-specific kernel that has xen ballooning disabled, which fixes this problem. -- You received this bug notification because you are a member of

[Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-04-17 Thread Dan Streetman
> Is there any intention of backporting either linux-aws or any of the NVMe bug > fixes from > linux-aws into linux-image-virtual-lts-xenial for Ubuntu 14.04 since they're > both > 4.4.0 kernels? the fix for this bug is to change the kernel config param CONFIG_XEN_BALLOON from y to n, disabling

[Bug 1453330] Re: pull-{lp, debian}-source not getting source for binary because DDE is dead

2017-04-20 Thread Dan Streetman
Also, I have pkgs built for xenial/yakkety/zesty with the latest merge proposal code, in this ppa: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1453330 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1453330] Re: pull-{lp, debian}-source not getting source for binary because DDE is dead

2017-04-20 Thread Dan Streetman
Ok, I updated my merge request to a git-based merge request: https://code.launchpad.net/~ddstreet/ubuntu-dev-tools/+git/ubuntu-dev-tools/+merge/322863 also, I consolidated the script naming; so it's now: pull-lp-source pull-lp-debs pull-lp-ddebs pull-lp-udebs which I think is more obvious, as

[Bug 1672470] Re: ip_rcv_finish() NULL pointer kernel panic

2017-04-17 Thread Dan Streetman
With a virsh guest installed with standard xenial, using the 4.4.0-72-generic kernel, I created a bridge and attached the virtio interface to it. I then started iperf3 -s on the guest, and started iperf3 -c GUESTIP -t 300 on the host, to create continuous traffic to the guest. Then I added a

[Bug 1672470] Re: ip_rcv_finish() NULL pointer kernel panic

2017-04-17 Thread Dan Streetman
Same test setup as above, but using yakkety with kernel 4.8.0-46-generic, reproduces the kernel oops. After upgrading to kernel 4.8.0-48-generic, the kernel oops no longer happens when modprobing or rmmoding br_netfilter. ** Tags removed: verification-needed-xenial verification-needed-yakkety **

[Bug 1372368] Re: VM creation fails on Utopic/Trusty

2017-04-17 Thread Dan Streetman
With a standard trusty install, the versions installed are: uvtool 0~bzr92-0ubuntu1 libvirt0 1.2.2-0ubuntu13.1.20 this combination does not have this problem, as libvirt hasn't yet changed to use type 'iso'. After apt-add-repository cloud-archive:mitaka, and upgrading libvirt, the versions

[Bug 1672470] [NEW] ip_rcv_finish() NULL pointer kernel panic

2017-03-13 Thread Dan Streetman
2/0x82 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Tags: sts ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu) Importance: Undecided => Medi

[Bug 1672470] Re: ip_rcv_finish() NULL pointer kernel panic

2017-03-13 Thread Dan Streetman
** No longer affects: linux (Ubuntu Vivid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672470 Title: ip_rcv_finish() NULL pointer kernel panic To manage notifications about this bug go to:

[Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

2017-03-01 Thread Dan Streetman
> We see an address of 0xfc7ffb000 Hi Matt, I don't think you're accounting for the additional pages due to the Xen balloon, are you? That increases physical memory, after boot. If you check the /proc/zoneinfo file, look at the Normal zone's spanned pages and start pfn, e.g.: Node 0, zone

<    1   2   3   4   5   6   7   8   9   10   >