[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-07 Thread Dan Streetman
I should note that this is marked as Fix Released in debian, but from the debian bug comments it just looks like Chris asked for that bug to be closed as a configuration issue (which this is not). This is actually only a VLAN issue with higher-than-default mtu. The bond does not have anything to

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-07 Thread Dan Streetman
** Also affects: vlan (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224007 Title: mtu not always set properly on bond/vlan interface To manage

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-09 Thread Dan Streetman
** Patch added: "patch to yakkety debian/network/if-pre-up.d/vlan script" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1224007/+attachment/4737642/+files/lp1224007-yakkety.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-09 Thread Dan Streetman
pls ignore patch from above comment; i have a simpler one i'll attach. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224007 Title: mtu not always set properly on bond/vlan interface To manage

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-09 Thread Dan Streetman
** Patch added: "debdiff for yakkety vlan" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1224007/+attachment/4737643/+files/lp1224007-yakkety.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1622567] [NEW] kernel does not calculate correct total memory size

2016-09-12 Thread Dan Streetman
Public bug reported: [Impact] On virtual systems under Xen, the kernel does not correctly calculate the total amount of memory. This results in the system having slightly less memory available for use than the actual amount provided by Xen. [Test Case] Load a virtual Xen guest with the latest

[Bug 1622567] Re: kernel does not calculate correct total memory size

2016-09-12 Thread Dan Streetman
This is fixed by commit: c275a57f5ec3056f732843b11659d892235faff7 (xen/balloon: Set balloon's initial state to number of existing RAM pages) which requires part of commit: 7ee3d4e8cd560500192d80ca84d7f15d6dee0807 (mm: introduce helper function mem_init_print_info() to simplify mem_init()) **

[Bug 1609367] Re: ifupdown does not set ipv6-only large mtu

2016-09-09 Thread Dan Streetman
> I believe the decision is to add the scripts to ifupdown in y or z only (no SRU) or, we can just close this as wontfix and explain how to work around this by adding a manual inet section with the increased mtu value, since that's quite easy to do when manually configuring ifupdown. -- You

[Bug 1609367] Re: ifupdown does not set ipv6-only large mtu

2016-09-09 Thread Dan Streetman
To follow up, I believe the decision is to add the scripts to ifupdown in y or z only (no SRU), and fix this for older releases in curtin via bug 1609861. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-12 Thread Dan Streetman
tested on yakkety: using isc-dhcp-client 4.3.3-5ubuntu13, bug exists; dhcpv6 prefix is set to /64. using isc-dhcp-client 4.3.3-5ubuntu13.1, bug is fixed; dhcpv6 prefix is set correctly to /128. ** Tags added: verification-done-yakkety -- You received this bug notification because you are a

[Bug 1622567] Re: Xen guest total memory size smaller than specified in virtual configuration due to Xen balloon driver

2016-09-12 Thread Dan Streetman
** Summary changed: - kernel does not calculate correct total memory size + Xen guest total memory size smaller than specified in virtual configuration due to Xen balloon driver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

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

2016-09-12 Thread Dan Streetman
There are upstream commits that may fix this problem, I've updated the same ppa with a new test build (with only the commits, and without any debug). If anyone can still reproduce this problem, please try the latest kernel in the ppa and report if it fixes the problem or not:

[Bug 1622567] Re: kernel does not calculate correct total memory size

2016-09-12 Thread Dan Streetman
** Description changed: [Impact] On virtual systems under Xen, the kernel does not correctly calculate the total amount of memory. This results in the system having slightly less memory available for use than the actual amount provided by Xen. + + [Fix] + + See first comment.

[Bug 1622567] Re: Xen guest total memory size smaller than specified in virtual configuration due to Xen balloon driver

2016-09-12 Thread Dan Streetman
I verified this using an Amazon AWS HVM (Xen) precise medium instance; it had the full amount of memory only after booting a precise kernel with these patches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-12 Thread Dan Streetman
** Patch added: "patchv2 to yakkety debian/network/if-pre-up.d/vlan script" https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1224007/+attachment/4739533/+files/lp1224007-yakkety-v2.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-12 Thread Dan Streetman
** Patch added: "debdiffv2 for yakkety vlan" https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1224007/+attachment/4739534/+files/lp1224007-yakkety-v2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-12 Thread Dan Streetman
sorry, the first patch had an issue where it didn't raise the device mtu if the vlan already existed. the v2 checks and increases if needed the dev mtu, even if the vlan already exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags

2016-09-15 Thread Dan Streetman
** Patch added: "debdiff for trusty" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+attachment/4741483/+files/lp1624014-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags

2016-09-15 Thread Dan Streetman
** Patch added: "debdiff for xenial" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+attachment/4741484/+files/lp1624014-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags

2016-09-15 Thread Dan Streetman
PPA containing fixed klibc pkg: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1624014 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624014 Title: Wrong bit set in klibc PXE dhcp/bootp flags

[Bug 1624014] [NEW] Wrong bit set in klibc PXE dhcp/bootp flags

2016-09-15 Thread Dan Streetman
Public bug reported: [Description] The patch for bug 1327412 set the wrong bit in the bootp flags field. It set flags to 0x800, but the correct value is 0x8000. That sets the "broadcast" bit, and the spec requires all other bits to be 0. Setting one of the "must be zero" bits in the flags

[Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags

2016-09-15 Thread Dan Streetman
** Patch added: "patch to correct the bootp flags broadcast bit position" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+attachment/4741482/+files/lp1624014.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up

2016-09-15 Thread Dan Streetman
Opened bug 1624014 to patch the wrong-bit regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug

[Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags

2016-09-15 Thread Dan Streetman
** Patch added: "debdiff for yakkety" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+attachment/4741485/+files/lp1624014-yakkety.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-15 Thread Dan Streetman
I assume you mean these 2 failing tests, below; that's correct behavior now, the tests should be changed to expect a /128 DHCPv6 address instead of a /64 DHCPv6 address. == FAIL: test_open_b_ip6_dhcp (__main__.T) Open network,

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-15 Thread Dan Streetman
tested on precise: using isc-dhcp-client 4.1.ESV-R4-0ubuntu5.10, bug exists; dhcpv6 prefix is set to /64. using isc-dhcp-client 4.1.ESV-R4-0ubuntu5.11, bug is fixed; dhcpv6 prefix is set correctly to /128. ** Tags added: verification-done-precise -- You received this bug notification because

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-15 Thread Dan Streetman
tested on trusty: using isc-dhcp-client 4.2.4-7ubuntu12.6, bug exists; dhcpv6 prefix is set to /64. using isc-dhcp-client 4.2.4-7ubuntu12.7, bug is fixed; dhcpv6 prefix is set correctly to /128. ** Tags removed: verification-needed ** Tags added: verification-done-trusty -- You received this

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-15 Thread Dan Streetman
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Precise) Status: New => Invalid ** Patch added: "debdiff to fix network manager test in trusty"

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-15 Thread Dan Streetman
** Patch added: "lp1609898-nm-xenial.debdiff" https://bugs.launchpad.net/ubuntu/precise/+source/network-manager/+bug/1609898/+attachment/4741542/+files/lp1609898-nm-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-15 Thread Dan Streetman
** Patch added: "lp1609898-nm-yakkety.debdiff" https://bugs.launchpad.net/ubuntu/precise/+source/network-manager/+bug/1609898/+attachment/4741543/+files/lp1609898-nm-yakkety.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-15 Thread Dan Streetman
The attached debdiffs lp1609898-nm-[trusty|xenial|yakkety].debdiff patch network-manager's debian/tests/wpa-dhclient test to use /128 instead of /64 for its DHCPv6 address test. Note it leaves the ipv6 Router Advertisement provided addresses with /64, as that prefix length is provided to the

[Bug 1497428] Re: kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

2016-09-09 Thread Dan Streetman
That is very definitely not the same bug as this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1497428 Title: kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968 To manage

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-12 Thread Dan Streetman
tested on xenial: using isc-dhcp-client 4.3.3-5ubuntu12.1, bug exists; dhcpv6 prefix is set to /64. using isc-dhcp-client 4.3.3-5ubuntu12.2, bug is fixed; dhcpv6 prefix is correctly set to /128. ** Tags removed: verification-needed ** Tags added: verification-done-xenial -- You received this

[Bug 1510098] Re: /etc/network/interfaces ipv6 static gateway not set

2016-09-24 Thread Dan Streetman
15.10 is EOL, and this does seem to work in 16.04. Please reopen if you still have this problem in 16.04. ** Changed in: ifupdown (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind

2016-09-24 Thread Dan Streetman
This is being worked in bug 1447715. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind To

[Bug 1013597] Re: No default route for stateful DHCPv6

2016-09-24 Thread Dan Streetman
** Changed in: ifupdown (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: ifupdown (Ubuntu Precise) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

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

2016-09-26 Thread Dan Streetman
> I've tried your PPA with the included patch (4.4.0-36-generic > #55hf1403152v20160916b1-Ubuntu). > As I've also reported on the Github docker issue [1], this does not fix the > issue for me. that's unfortunate. > Would it help you test again with this patch, and with your debug patches

[Bug 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind

2016-09-24 Thread Dan Streetman
@jacob11, I understand your frustration. All I can do is fix the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-10-06 Thread Dan Streetman
@racb i changed the version numbers in the debdiffs for precise and trusty, i think the xenial debdiff number is already ok. thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224007 Title:

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-10-06 Thread Dan Streetman
** Patch added: "lp1224007-trusty.debdiff" https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4755717/+files/lp1224007-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-10-06 Thread Dan Streetman
** Patch removed: "lp1224007-precise.debdiff" https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4750476/+files/lp1224007-precise.debdiff ** Patch removed: "lp1224007-trusty.debdiff"

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

2016-09-21 Thread Dan Streetman
** Patch added: "lp1447715-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1447715/+attachment/4745626/+files/lp1447715-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

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

2016-09-21 Thread Dan Streetman
This is fixed in debian ifupdown 0.8.11 by this patch: --- ifupdown-0.8.10/wait-for-ll6.sh 2015-12-01 16:50:26.0 -0500 +++ ifupdown-0.8.11/wait-for-ll6.sh 2016-04-20 08:57:37.0 -0400 @@ -4,7 +4,7 @@ delay=${IF_LL_INTERVAL:-0.1} for attempt in $(seq 1 $attempts); do -

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

2016-09-16 Thread Dan Streetman
Ah, you need a patched test kernel on xenial...I'll upload one to the PPA for testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become

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

2016-09-16 Thread Dan Streetman
Alexandre, please see my last comment, that links to a test kernel PPA with EXACTLY that upstream commit, 751eb6b6042a596b0080967c1a529a9fe98dac1d ("ipv6: addrconf: fix dev refcont leak when DAD failed") If you can reproduce this, please test with the PPA and report if it fixes the problem. --

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

2016-09-16 Thread Dan Streetman
PPA updated with patched test kernels for xenial as well as trusty lts-xenial. https://launchpad.net/~ddstreet/+archive/ubuntu/lp1403152 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title:

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-19 Thread Dan Streetman
** Patch added: "lp1224007-trusty.debdiff" https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4743649/+files/lp1224007-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-19 Thread Dan Streetman
** Patch added: "lp1224007-precise.debdiff" https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4743648/+files/lp1224007-precise.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-19 Thread Dan Streetman
** Patch added: "lp1224007-xenial.debdiff" https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4743650/+files/lp1224007-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-23 Thread Dan Streetman
Also note that dnsmasq can act as both a dhcpv6 server as well as serving router advertisements. The ISC dhcp server only does dhcpv6, it does not have support (that I know of) for serving router advertisements. If you do want your clients to use slaac addresses in addition to the dhcpv6

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

2016-09-23 Thread Dan Streetman
And yakkety has ifupdown 0.8.13 which contains the fix already. ** Tags added: 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/1447715 Title: dhclient -6: Can't bind to dhcp address: Cannot

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

2016-09-23 Thread Dan Streetman
I tested on precise and trusty, and this problem doesn't appear there, so only xenial requires the ifupdown SRU. ** Changed in: ifupdown (Ubuntu Trusty) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-23 Thread Dan Streetman
For anyone reading this because the isc-dhcp-client update broke their DHCPv6 network: First, I assume you're running a DHCPv6 server to provide the ipv6 addresses to your clients. If you do not have any Router Advertisement service configured on your server, the easiest thing to do is use

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-21 Thread Dan Streetman
@arges, yep the attached lp1609898-nm-[trusty|xenial|yakkety].debdiff patches update network-manager's test script to the new behavior. I can pull the patches out of the debdiffs, if that's easier. I did a brief search in the network-manager tests and didn't find any other place that looks like

[Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-21 Thread Dan Streetman
Unfortunately, while I initially put in the bug description that there was no regresssion potential, I've been made aware that some network configurations rely on the previous (incorrect) behavior of the dhcp client to set a prefix len of /64. Such configurations will break when the dhcp clients

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

2016-09-22 Thread Dan Streetman
** Changed in: ifupdown (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: ifupdown (Ubuntu Precise) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: ifupdown (Ubuntu Trusty) Assignee: (unassigned) => Dan Streetman

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

2016-09-21 Thread Dan Streetman
ng in wily. ** 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 Ubuntu. https://bugs.launchpad.net/bugs/1447715 Title: dhclient -6: Can't bind to

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

2016-09-21 Thread Dan Streetman
** Description changed: - After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6 - address via DHCPv6. The root cause is that dhclient is exiting with the - following message: + (Original bug description follows SRU info) + + [Description] + + When using dhcpv6 configured via

[Bug 1609367] Re: ifupdown does not set ipv6-only large mtu

2016-08-26 Thread Dan Streetman
Ryan are you working on adding the script to ifupdown in ubuntu and/or debian? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609367 Title: ifupdown does not set ipv6-only large mtu To manage

[Bug 1609367] Re: ifupdown does not set ipv6-only large mtu

2016-08-29 Thread Dan Streetman
> While we could see about getting the script included in yakkety (or y+1); > curtin will still need to > handle this unless we want to SRU ifdowndown in precise, trusty and > xenial. This has an enormous > impact; so it's not something we should take lightly. As long as curtin handles it

[Bug 1609367] Re: ifupdown does not set ipv6-only large mtu

2016-08-22 Thread Dan Streetman
> if we have a higher mtu onthe ipv6 link, like 4800, then the inet section > mtu setting clobbers it and they both end up at 1500. > > Now, that case I still believe is *invalid* configuration; I agree - if the ifupdown config has the inet mtu set lower than the inet6 mtu, that's a

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-28 Thread Dan Streetman
** Patch added: "lp1224007-yakkety.debdiff" https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4750479/+files/lp1224007-yakkety.debdiff ** Patch removed: "debdiff for yakkety vlan"

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-28 Thread Dan Streetman
** Patch added: "lp1224007-trusty.debdiff" https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4750477/+files/lp1224007-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-28 Thread Dan Streetman
** Patch removed: "lp1224007-precise.debdiff" https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4743648/+files/lp1224007-precise.debdiff ** Patch removed: "lp1224007-trusty.debdiff"

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-28 Thread Dan Streetman
** Patch added: "lp1224007-xenial.debdiff" https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4750478/+files/lp1224007-xenial.debdiff ** Patch removed: "debdiffv2 for yakkety vlan"

[Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-28 Thread Dan Streetman
@sakishrist, thanks, I updated all the debdiffs to add the missing space. ** Tags added: 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/1224007 Title: mtu not always set properly on

[Bug 1622567] Re: Xen guest total memory size smaller than specified in virtual configuration due to Xen balloon driver

2016-09-27 Thread Dan Streetman
Verified fix using kernel 3.2.0-111. Before patched kernel: ubuntu@lp1622567:~$ uname -a Linux lp1622567 3.2.0-110-virtual #151-Ubuntu SMP Tue Aug 30 14:46:28 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ubuntu@lp1622567:~$ free total used free sharedbuffers

[Bug 1518457] Re: kswapd0 100% CPU usage

2016-10-01 Thread Dan Streetman
anges kswapd memory balancing to "per node" instead of "per zone": https://marc.info/?l=linux-mm=146797052519026 That's a rather large patchset to backport to the xenial kernel, but I'll give it a try. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dan Stre

[Bug 1518457] Re: kswapd0 100% CPU usage

2016-10-01 Thread Dan Streetman
The patch series that fixes this is included in yakkety (if anyone reproduces this on a yakkety kernel, please let me know), so this only needs fixing in xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1518457] Re: kswapd0 100% CPU usage

2016-10-02 Thread Dan Streetman
On review of the patch series, it's simply too large and complex to backport for this situation; it makes, and depends on, a rather large amount of change to the mm subsystem, and there are easier and smaller ways to work around this bug in the xenial kernel. Specifically, a comparison of the Xen

[Bug 1587265] Re: ubuntu not work with tickless kernel boot option

2016-10-26 Thread Dan Streetman
What specific kernel version had the problem? You can check with: uname -a The CONFIG_NO_HZ_FULL kernel param was turned off at some point between trusty's 3.13 and xenial's 4.4, and without that kernel param enabled the nohz_full boot param has no effect. -- You received this bug

[Bug 1609861] Re: IPv6 MTU not applied correctly for pure IPv6 interfaces

2016-10-28 Thread Dan Streetman
** Changed in: curtin (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: curtin (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: curtin Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1640275] [NEW] move nvme driver to linux-image

2016-11-08 Thread Dan Streetman
Public bug reported: The nvme driver is in the -extra package but should be in the linux- image package, to avoid the overhead of having to install the -extra package just to get the nvme driver. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: sts-sru --

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

2016-11-08 Thread Dan Streetman
> lib/modules/4.4.0-46-generic/kernel/drivers/nvme/host/nvme.ko Sorry, this is for trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640275 Title: move nvme driver to linux-image To manage

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

2016-11-07 Thread Dan Streetman
update for this: this patch is already included upstream in debian, and is already included in yakkety. It's not yet in xenial. It's not required in trusty (bug doesn't exist there). additionally, bug 1633479 (which fixes this by putting the DAD wait in isc-dhcp-client) is in proposed for

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

2016-11-07 Thread Dan Streetman
** 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/1447715 Title: dhclient -6: Can't bind to dhcp address: Cannot assign requested address To manage notifications about

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

2016-10-14 Thread Dan Streetman
> Well, if that made it into Ubuntu's kernel before and including 4.4.0-42, it > didn't fix it > (I still get the bug on many machines & VMs). No, it's not in the released xenial kernel yet, the upstream 4.4.22 stable commits are still in the xenial master-next branch kernel; it'll be a bit

[Bug 1628552] Re: on startup gateway & dns- options in /etc/network/interfaces are not always set

2016-10-20 Thread Dan Streetman
> well i've now been able to restart 3 of the 4 systems about 5-10x each > through the day. all have > had their gateway and dns- settings from /e/n/i reliably set. that is, until > now. i've got one > system that did not get gateway or dns- settings. The gateway is set directly from ifup (by

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

2016-10-20 Thread Dan Streetman
> The use case I found was in initramfs-tools, which recently SRU'd a change > that uses dhclient to > support 'ip=' command lines and dhcpv6. aha, and busybox ip doesn't support the -tentative param that the ifupdown change uses. +1 on fixing isc-dhcp then (as well as leaving this fix in

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

2016-10-24 Thread Dan Streetman
> From the logs it looks like the patch is now a part of > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627730 which hit > 4.4.0-46.67~14.04.1 > (proposed) on 22nd Oct? yes, the patch is included in the 4.4.0-46.67 kernel (both linux-lts- xenial on trusty, and regular linux on xenial).

[Bug 1639920] Re: NVMe detection failed during bootup

2016-11-22 Thread Dan Streetman
I bisected to the commit that introduces the failing behavior which is: df00a7683b417a15a6e695f9a3b200a799b787fa ("nvme: only add a controller to dev_list after it's been fully initialized") -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1639920] Re: NVMe detection failed during bootup

2016-11-23 Thread Dan Streetman
I should also note, the latest upstream kernel has similar timeout problems while probing, so this isn't restricted to only the xenial kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639920

[Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags

2016-11-16 Thread Dan Streetman
to clarify, tcpdump with klibc-utils 2.0.3-0ubuntu1.14.04.1 shows the flag is 0x0800 (incorrect) while tcpdump with klibc-utils 2.0.3-0ubuntu1.14.04.2 (from -proposed) shows the flag is 0x8000 (correct). -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags

2016-11-16 Thread Dan Streetman
I confirmed the fix is correct in trusty by tcpdumping a run of /usr/lib/klibc/bin/ipconfig ** 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 Ubuntu.

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

2016-11-16 Thread Dan Streetman
** Patch removed: "lp1372368-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/1372368/+attachment/4730232/+files/lp1372368-trusty.debdiff ** Patch added: "lp1372368-trusty.debdiff"

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

2016-11-16 Thread Dan Streetman
> The debdiff in comment #5 looks fine, but it's odd that you didn't use your > own name in the > changelog while still giving credit to Robie. ha, oops! :) I fixed the debdiff and re-attached, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is

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

2016-11-18 Thread Dan Streetman
** Patch added: "lp1642903-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903/+attachment/4779388/+files/lp1642903-trusty.debdiff ** Tags added: sts sts-sponsor sts-sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is

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

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

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

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

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

2016-11-18 Thread Dan Streetman
This is fixed with commit a5110c90303cf455db5062faef34d5724d12e2e9 from upstream systemd, which is already included in zesty. -- 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

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

2016-11-18 Thread Dan Streetman
Public bug reported: [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. [Regression Potential]

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

2016-10-13 Thread Dan Streetman
> Apparently the fix is in: > > https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.22 Hopefully the commit does fix things, although Paul's comment above indicated it may not, at least not for everyone. -- You received this bug notification because you are a member of Ubuntu Bugs, which

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

2016-10-14 Thread Dan Streetman
> The fix i intended was to dhclient, so that dhclient would wait in PREINIT6 dhclient-script. Looks good to me, fixing dhclient as well is a good idea. > I think that is generally more functional as it would mean ifupdown or any > other user of dhclient > would get the fix. What other users

[Bug 1639920] Re: NVMe detection failed during bootup

2016-11-29 Thread Dan Streetman
> Is there any update on this issue? I'm still debugging, but can give a summary of the problem, at least on the system I'm working on. First, to address: > One is the vfree WARNING which indicates that the error paths are not quite > right this is a trival fix to the error handling path; it's

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

2016-12-08 Thread Dan Streetman
the polling kthread (as it was never actually needed), and do use MSIX interrupts for the admin queue and I/O queues. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscri

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

2016-12-08 Thread Dan Streetman
Public bug reported: [Impact] On an Amazon AWS instance that has NVMe drives, the NVMe drives fail to initialize, and so aren't usable by the system. If one of the NVMe drives contains the root filesystem, the instance won't boot. [Test Case] Boot an AWS instance with a NVMe drive. It will

[Bug 1639920] Re: NVMe detection failed during bootup

2016-12-08 Thread Dan Streetman
*** This bug is a duplicate of bug 1647887 *** https://bugs.launchpad.net/bugs/1647887 > I'd also like to know how or what we need to do in order to proceed and getting this fix for GA? I opened bug 1647887 separately for this (I'm working on this problem for a separate situation and I

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

2016-12-08 Thread Dan Streetman
Note: bug 1639920 is also affected by this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647887 Title: NVMe driver accidentally reverted to use GSI instead of MSIX To manage notifications about

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

2016-12-06 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 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/4788137/+files/lp1647485-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

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