[Bug 1665613] Re: kpatch-dkms 0.3.2-1ubuntu4.2: kpatch kernel module failed to build

2017-10-05 Thread goldyfruit
Still not building with 4.11.0-14 kernel. cc1: some warnings being treated as errors scripts/Makefile.build:294: recipe for target '/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.o' failed make[3]: *** [/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.o] Error 1 Makefile:1698: recipe for target '

[Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

2017-07-20 Thread goldyfruit
@Joseph, I don't know, we are just using the Ubuntu LTS versions. You point is valid, maybe it's better to check if Zesty has this issue. Thanks for the follow up! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad

[Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

2017-07-17 Thread goldyfruit
Do you have an update about 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/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel To manage notifications about this bug go

[Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

2017-06-20 Thread goldyfruit
Same issue. ** Attachment added: "kdump-trace2.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+attachment/4899716/+files/kdump-trace2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.ne

[Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

2017-06-09 Thread goldyfruit
Sorry for the late answer. Please find the log in attachment. ** Attachment added: "kdump-trace.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+attachment/4893178/+files/kdump-trace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1665613] Re: kpatch-dkms 0.3.2-1ubuntu4.2: kpatch kernel module failed to build

2017-06-09 Thread goldyfruit
No more maintainer ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665613 Title: kpatch-dkms 0.3.2-1ubuntu4.2: kpatch kernel module failed to build To manage notifications about this bug go to: ht

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

2017-05-10 Thread goldyfruit
@Thiago, same for us. Hope it will be fixed soon ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial

[Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

2017-05-04 Thread goldyfruit
I'm even not able to boot the operating system with the kernel in comment #6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel To

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

2017-05-04 Thread goldyfruit
@Thiago, yes I confirm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe) To manage notificati

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

2017-05-04 Thread goldyfruit
Downgraded to 4.4 series. :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe) To manage notif

[Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

2017-05-03 Thread goldyfruit
I'm able to boot this OS with this kernel I got a kernel panic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel To manage notifi

[Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

2017-05-03 Thread goldyfruit
@Louis, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel To manage notifications about this bug go to: https://bugs.launc

[Bug 1665613] Re: kpatch-dkms 0.3.2-1ubuntu4.2: kpatch kernel module failed to build

2017-05-02 Thread goldyfruit
Any updates ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665613 Title: kpatch-dkms 0.3.2-1ubuntu4.2: kpatch kernel module failed to build To manage notifications about this bug go to: https://b

[Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

2017-05-02 Thread goldyfruit
** Description changed: - I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 - kernel. + I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel. + This issue seems to be fixed mainstream: https://lkml.org/lkml/2017/1/9/77 + kdump-tools

[Bug 1687779] [NEW] Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

2017-05-02 Thread goldyfruit
Public bug reported: I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel. kdump-tools 1:1.5.9-5ubuntu0.4 makedumpfile1:1.5.9-5ubuntu0.4 linux-image-4.8.0-46-generic4.8.0-46.49~16.04.1 # kdump-config show DUMP_MODE:

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-05-02 Thread goldyfruit
@michal did you try this kernel: https://people.canonical.com/~jesse/lp1679823v2/ ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with k

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-05-02 Thread goldyfruit
Success. #38 works with ixgbe @Jesse thanks and good job ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-4

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-05-02 Thread goldyfruit
Hi Jesse, Same behavior for me as @Henning. Kernel: ii linux-image-4.8.0-52-generic4.8.0-52.55~16.04.1 Error: kernel: [ 53.900687] ha-4fbfe106-23: Invalid MTU 8950 requested, hw max 1500 ixgbe NIC driver. -- You received this bug notification because you are a member of Ubuntu Bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-04-25 Thread goldyfruit
It affects Neutron, qr-* and ha-* interfaces can be set with a MTU higher than 1500. Look the output in #13 comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-04-25 Thread goldyfruit
@Joseph, I tried with 4.10.0-20-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49) To manage notifi

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-04-25 Thread goldyfruit
Still having and issue, for the physical interface it's working as expected but for virtual interfaces I got the same error. I'm trying to change MTU on an OpenVswitch interface in a kernel namespace. If I switch back to 4.8.0-46 everything is OK. Apr 25 19:44:11 controller003 kernel: [ 58.2551

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-04-25 Thread goldyfruit
@Joseph, 4.10.0-20-generic works for me. Thanks ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49) To man

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10

2017-04-25 Thread goldyfruit
I had a kernel upgrade 4.8.0-46 to 4.8.0.49 and I had the same issue. # ip l set eno49 mtu 9000 RTNETLINK answers: Invalid argument # tail -1 /var/log/kern.log Apr 25 14:10:20 controller001 kernel: [64170.180920] eno49: Invalid MTU 9000 requested, hw max 68 # dpkg -l | grep linux-image-4.8 ii

[Bug 1665613] Re: kpatch-dkms 0.3.2-1ubuntu4.2: kpatch kernel module failed to build

2017-04-10 Thread goldyfruit
It seems to be fixed in Debian Stretch. http://metadata.ftp-master.debian.org/changelogs/main/k/kpatch/kpatch_0.3.2-3.1_changelog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665613 Title: kpatch-

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10

2017-04-05 Thread goldyfruit
@Joseph, nop. :/ In the Bugzilla it seems tagged for 4.10.1 release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 To

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

2017-04-04 Thread goldyfruit
@Dan, I filled a bug about it, seems to be an issue with kernel 4.10: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679823 -- 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: defaul

[Bug 1679823] [NEW] bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10

2017-04-04 Thread goldyfruit
Public bug reported: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux- image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu

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

2017-04-04 Thread goldyfruit
Only few of them still down: # ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:5e:

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

2017-04-04 Thread goldyfruit
I don't know if it's related but since the I'm using this vlan package I have this issue: Apr 04 17:08:30 compute001 ifup[2396]: Waiting for a slave to join bond0 (will timeout after 60s) Apr 04 17:08:30 compute001 ifup[2396]: ifquery: recursion detected for interface bond0 in pre-up phase Apr 0

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

2017-03-31 Thread goldyfruit
The patch fixes the issue for me as well. Thanks ! -- 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 manage noti

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

2017-03-08 Thread goldyfruit
Any idea if an upstream fix will be applied on Xenial ? It's a very annoying issue :/ -- 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 interf

[Bug 1665613] Re: kpatch-dkms 0.3.2-1ubuntu4.2: kpatch kernel module failed to build

2017-02-27 Thread goldyfruit
Same issue here, Ubuntu Xenial 16.04.2 ** Attachment added: "/var/lib/dkms/kpatch/0.3.2/build/make.log" https://bugs.launchpad.net/ubuntu/+source/kpatch/+bug/1665613/+attachment/4827722/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is su

[Bug 1119428] Re: stack.sh failing giving error "g-api did not start"

2013-06-19 Thread goldyfruit
** Also affects: ubuntu Importance: Undecided Status: New ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1119428 Title: stack.sh failing giving error "g-api di

[Bug 1187613] Re: nova-novncproxy crashes on Debian Wheezy

2013-06-19 Thread goldyfruit
I published the patch here : http://blog.incloudus.com/2013/nova- novncproxy-et-debian-gnulinux-wheezy/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187613 Title: nova-novncproxy crashes on Debian

[Bug 1187613] Re: nova-novncproxy crashes on Debian Wheezy

2013-06-05 Thread goldyfruit
om oslo.config import cfg” instead." Package informations :    - Package: novnc    - Version: 1:0.4+dfsg+1-7    - Architecture: amd64 So i did a patch which solves the issue for me, you will find it in attachment. Gaëtan (goldyfruit) -- You received this bug notificati

[Bug 1187613] [NEW] nova-novncproxy crashes on Debian Wheezy

2013-06-04 Thread goldyfruit
Package informations :    - Package: novnc    - Version: 1:0.4+dfsg+1-7    - Architecture: amd64 So i did a patch which solves the issue for me, you will find it in attachment. Gaëtan (goldyfruit) ** Affects: nova Importance: Undecided Status: New ** Affects: novnc (Ubuntu) I