[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
@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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: 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 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:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2b00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz The kernel trace [ 10.738064] BUG: unable to handle kernel NULL pointer dereference at 0088 [ 10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.743571] PGD 0 [ 10.744482] Oops: [#1] SMP [ 10.745615] Modules linked in: [ 10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic #49~16.04.1-Ubuntu [ 10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [ 10.752574] task: 8f16b2938ec0 task.stack: 8f16b294 [ 10.754892] RIP: 0010:[] [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.758371] RSP: 0018:8f16b2943e40 EFLAGS: 00010206 [ 10.760337] RAX: 0050 RBX: RCX: 238a [ 10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: [ 10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 89231a97 [ 10.767968] R10: eac07000 R11: R12: 89c1a030 [ 10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 8f16b2c19300 [ 10.772894] FS: () GS:8f16b2c0() knlGS: [ 10.775945] CS: 0010 DS: ES: CR0: 80050033 [ 10.777935] CR2: 0088 CR3: 2d806000 CR4: 001406f0 [ 10.780398] Stack: [ 10.781154] 8f16b2943e50 df388e 8f16b2943e88 89d8b292 [ 10.884602] 0105 89d8b196 89c0daf8 [ 10.887394] 8f16b2c19300 8f16b2943f08 88e02190 88ea377f [ 10.890699] Call Trace: [ 10.891596] [] intel_uncore_init+0xfc/0x2d6 [ 10.893587] [] do_one_initcall+0x50/0x1a0 [ 11.397431] [] ? parse_args+0x2cf/0x490 [ 11.399313] [] kernel_init_freeable+0x178/0x217 [ 11.402112] [] kernel_init+0xe/0x100 [ 11.404013] [] ret_from_fork+0x1f/0x40 [ 11.405895] [] ? rest_init+0x80/0x80 [ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00 [ 11.422367] RIP [] hswep_uncore_cpu_init+0x52/0xa0 [ 11.425174] RSP [ 11.426588] CR2: 0088 [ 11.427978] ---[ end trace d8adbfe4355f5160 ]--- [ 11.430006] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.430006] [ 11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.433354] Please find the full kernel trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
Do you have an update about this bug ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: 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 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:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2b00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz The kernel trace [ 10.738064] BUG: unable to handle kernel NULL pointer dereference at 0088 [ 10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.743571] PGD 0 [ 10.744482] Oops: [#1] SMP [ 10.745615] Modules linked in: [ 10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic #49~16.04.1-Ubuntu [ 10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [ 10.752574] task: 8f16b2938ec0 task.stack: 8f16b294 [ 10.754892] RIP: 0010:[] [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.758371] RSP: 0018:8f16b2943e40 EFLAGS: 00010206 [ 10.760337] RAX: 0050 RBX: RCX: 238a [ 10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: [ 10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 89231a97 [ 10.767968] R10: eac07000 R11: R12: 89c1a030 [ 10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 8f16b2c19300 [ 10.772894] FS: () GS:8f16b2c0() knlGS: [ 10.775945] CS: 0010 DS: ES: CR0: 80050033 [ 10.777935] CR2: 0088 CR3: 2d806000 CR4: 001406f0 [ 10.780398] Stack: [ 10.781154] 8f16b2943e50 df388e 8f16b2943e88 89d8b292 [ 10.884602] 0105 89d8b196 89c0daf8 [ 10.887394] 8f16b2c19300 8f16b2943f08 88e02190 88ea377f [ 10.890699] Call Trace: [ 10.891596] [] intel_uncore_init+0xfc/0x2d6 [ 10.893587] [] do_one_initcall+0x50/0x1a0 [ 11.397431] [] ? parse_args+0x2cf/0x490 [ 11.399313] [] kernel_init_freeable+0x178/0x217 [ 11.402112] [] kernel_init+0xe/0x100 [ 11.404013] [] ret_from_fork+0x1f/0x40 [ 11.405895] [] ? rest_init+0x80/0x80 [ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00 [ 11.422367] RIP [] hswep_uncore_cpu_init+0x52/0xa0 [ 11.425174] RSP [ 11.426588] CR2: 0088 [ 11.427978] ---[ end trace d8adbfe4355f5160 ]--- [ 11.430006] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.430006] [ 11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.433354] Please find the full kernel trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: 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 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:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2b00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz The kernel trace [ 10.738064] BUG: unable to handle kernel NULL pointer dereference at 0088 [ 10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.743571] PGD 0 [ 10.744482] Oops: [#1] SMP [ 10.745615] Modules linked in: [ 10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic #49~16.04.1-Ubuntu [ 10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [ 10.752574] task: 8f16b2938ec0 task.stack: 8f16b294 [ 10.754892] RIP: 0010:[] [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.758371] RSP: 0018:8f16b2943e40 EFLAGS: 00010206 [ 10.760337] RAX: 0050 RBX: RCX: 238a [ 10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: [ 10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 89231a97 [ 10.767968] R10: eac07000 R11: R12: 89c1a030 [ 10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 8f16b2c19300 [ 10.772894] FS: () GS:8f16b2c0() knlGS: [ 10.775945] CS: 0010 DS: ES: CR0: 80050033 [ 10.777935] CR2: 0088 CR3: 2d806000 CR4: 001406f0 [ 10.780398] Stack: [ 10.781154] 8f16b2943e50 df388e 8f16b2943e88 89d8b292 [ 10.884602] 0105 89d8b196 89c0daf8 [ 10.887394] 8f16b2c19300 8f16b2943f08 88e02190 88ea377f [ 10.890699] Call Trace: [ 10.891596] [] intel_uncore_init+0xfc/0x2d6 [ 10.893587] [] do_one_initcall+0x50/0x1a0 [ 11.397431] [] ? parse_args+0x2cf/0x490 [ 11.399313] [] kernel_init_freeable+0x178/0x217 [ 11.402112] [] kernel_init+0xe/0x100 [ 11.404013] [] ret_from_fork+0x1f/0x40 [ 11.405895] [] ? rest_init+0x80/0x80 [ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00 [ 11.422367] RIP [] hswep_uncore_cpu_init+0x52/0xa0 [ 11.425174] RSP [ 11.426588] CR2: 0088 [ 11.427978] ---[ end trace d8adbfe4355f5160 ]--- [ 11.430006] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.430006] [ 11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.433354] Please find the full kernel trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: 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 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:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2b00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz The kernel trace [ 10.738064] BUG: unable to handle kernel NULL pointer dereference at 0088 [ 10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.743571] PGD 0 [ 10.744482] Oops: [#1] SMP [ 10.745615] Modules linked in: [ 10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic #49~16.04.1-Ubuntu [ 10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [ 10.752574] task: 8f16b2938ec0 task.stack: 8f16b294 [ 10.754892] RIP: 0010:[] [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.758371] RSP: 0018:8f16b2943e40 EFLAGS: 00010206 [ 10.760337] RAX: 0050 RBX: RCX: 238a [ 10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: [ 10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 89231a97 [ 10.767968] R10: eac07000 R11: R12: 89c1a030 [ 10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 8f16b2c19300 [ 10.772894] FS: () GS:8f16b2c0() knlGS: [ 10.775945] CS: 0010 DS: ES: CR0: 80050033 [ 10.777935] CR2: 0088 CR3: 2d806000 CR4: 001406f0 [ 10.780398] Stack: [ 10.781154] 8f16b2943e50 df388e 8f16b2943e88 89d8b292 [ 10.884602] 0105 89d8b196 89c0daf8 [ 10.887394] 8f16b2c19300 8f16b2943f08 88e02190 88ea377f [ 10.890699] Call Trace: [ 10.891596] [] intel_uncore_init+0xfc/0x2d6 [ 10.893587] [] do_one_initcall+0x50/0x1a0 [ 11.397431] [] ? parse_args+0x2cf/0x490 [ 11.399313] [] kernel_init_freeable+0x178/0x217 [ 11.402112] [] kernel_init+0xe/0x100 [ 11.404013] [] ret_from_fork+0x1f/0x40 [ 11.405895] [] ? rest_init+0x80/0x80 [ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00 [ 11.422367] RIP [] hswep_uncore_cpu_init+0x52/0xa0 [ 11.425174] RSP [ 11.426588] CR2: 0088 [ 11.427978] ---[ end trace d8adbfe4355f5160 ]--- [ 11.430006] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.430006] [ 11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.433354] Please find the full kernel trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)
@Thiago, same for us. Hope it will be fixed soon ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: Confirmed Status in linux-hwe-edge source package in Yakkety: Confirmed Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: 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 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:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2b00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz The kernel trace [ 10.738064] BUG: unable to handle kernel NULL pointer dereference at 0088 [ 10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.743571] PGD 0 [ 10.744482] Oops: [#1] SMP [ 10.745615] Modules linked in: [ 10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic #49~16.04.1-Ubuntu [ 10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [ 10.752574] task: 8f16b2938ec0 task.stack: 8f16b294 [ 10.754892] RIP: 0010:[] [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.758371] RSP: 0018:8f16b2943e40 EFLAGS: 00010206 [ 10.760337] RAX: 0050 RBX: RCX: 238a [ 10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: [ 10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 89231a97 [ 10.767968] R10: eac07000 R11: R12: 89c1a030 [ 10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 8f16b2c19300 [ 10.772894] FS: () GS:8f16b2c0() knlGS: [ 10.775945] CS: 0010 DS: ES: CR0: 80050033 [ 10.777935] CR2: 0088 CR3: 2d806000 CR4: 001406f0 [ 10.780398] Stack: [ 10.781154] 8f16b2943e50 df388e 8f16b2943e88 89d8b292 [ 10.884602] 0105 89d8b196 89c0daf8 [ 10.887394] 8f16b2c19300 8f16b2943f08 88e02190 88ea377f [ 10.890699] Call Trace: [ 10.891596] [] intel_uncore_init+0xfc/0x2d6 [ 10.893587] [] do_one_initcall+0x50/0x1a0 [ 11.397431] [] ? parse_args+0x2cf/0x490 [ 11.399313] [] kernel_init_freeable+0x178/0x217 [ 11.402112] [] kernel_init+0xe/0x100 [ 11.404013] [] ret_from_fork+0x1f/0x40 [ 11.405895] [] ? rest_init+0x80/0x80 [ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00 [ 11.422367] RIP [] hswep_uncore_cpu_init+0x52/0xa0 [ 11.425174] RSP [ 11.426588] CR2: 0088 [ 11.427978] ---[ end trace d8adbfe4355f5160 ]--- [ 11.430006] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.430006] [ 11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.433354] Please find the full kernel trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)
@Thiago, yes I confirm. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: Confirmed Status in linux-hwe-edge source package in Yakkety: Confirmed Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)
Downgraded to 4.4 series. :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: Confirmed Status in linux-hwe-edge source package in Yakkety: Confirmed Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: 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 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:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2b00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz The kernel trace [ 10.738064] BUG: unable to handle kernel NULL pointer dereference at 0088 [ 10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.743571] PGD 0 [ 10.744482] Oops: [#1] SMP [ 10.745615] Modules linked in: [ 10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic #49~16.04.1-Ubuntu [ 10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [ 10.752574] task: 8f16b2938ec0 task.stack: 8f16b294 [ 10.754892] RIP: 0010:[] [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.758371] RSP: 0018:8f16b2943e40 EFLAGS: 00010206 [ 10.760337] RAX: 0050 RBX: RCX: 238a [ 10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: [ 10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 89231a97 [ 10.767968] R10: eac07000 R11: R12: 89c1a030 [ 10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 8f16b2c19300 [ 10.772894] FS: () GS:8f16b2c0() knlGS: [ 10.775945] CS: 0010 DS: ES: CR0: 80050033 [ 10.777935] CR2: 0088 CR3: 2d806000 CR4: 001406f0 [ 10.780398] Stack: [ 10.781154] 8f16b2943e50 df388e 8f16b2943e88 89d8b292 [ 10.884602] 0105 89d8b196 89c0daf8 [ 10.887394] 8f16b2c19300 8f16b2943f08 88e02190 88ea377f [ 10.890699] Call Trace: [ 10.891596] [] intel_uncore_init+0xfc/0x2d6 [ 10.893587] [] do_one_initcall+0x50/0x1a0 [ 11.397431] [] ? parse_args+0x2cf/0x490 [ 11.399313] [] kernel_init_freeable+0x178/0x217 [ 11.402112] [] kernel_init+0xe/0x100 [ 11.404013] [] ret_from_fork+0x1f/0x40 [ 11.405895] [] ? rest_init+0x80/0x80 [ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00 [ 11.422367] RIP [] hswep_uncore_cpu_init+0x52/0xa0 [ 11.425174] RSP [ 11.426588] CR2: 0088 [ 11.427978] ---[ end trace d8adbfe4355f5160 ]--- [ 11.430006] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.430006] [ 11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.433354] Please find the full kernel trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
@Louis, thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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 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:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2b00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz The kernel trace [ 10.738064] BUG: unable to handle kernel NULL pointer dereference at 0088 [ 10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.743571] PGD 0 [ 10.744482] Oops: [#1] SMP [ 10.745615] Modules linked in: [ 10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic #49~16.04.1-Ubuntu [ 10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [ 10.752574] task: 8f16b2938ec0 task.stack: 8f16b294 [ 10.754892] RIP: 0010:[] [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.758371] RSP: 0018:8f16b2943e40 EFLAGS: 00010206 [ 10.760337] RAX: 0050 RBX: RCX: 238a [ 10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: [ 10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 89231a97 [ 10.767968] R10: eac07000 R11: R12: 89c1a030 [ 10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 8f16b2c19300 [ 10.772894] FS: () GS:8f16b2c0() knlGS: [ 10.775945] CS: 0010 DS: ES: CR0: 80050033 [ 10.777935] CR2: 0088 CR3: 2d806000 CR4: 001406f0 [ 10.780398] Stack: [ 10.781154] 8f16b2943e50 df388e 8f16b2943e88 89d8b292 [ 10.884602] 0105 89d8b196 89c0daf8 [ 10.887394] 8f16b2c19300 8f16b2943f08 88e02190 88ea377f [ 10.890699] Call Trace: [ 10.891596] [] intel_uncore_init+0xfc/0x2d6 [ 10.893587] [] do_one_initcall+0x50/0x1a0 [ 11.397431] [] ? parse_args+0x2cf/0x490 [ 11.399313] [] kernel_init_freeable+0x178/0x217 [ 11.402112] [] kernel_init+0xe/0x100 [ 11.404013] [] ret_from_fork+0x1f/0x40 [ 11.405895] [] ? rest_init+0x80/0x80 [ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00 [ 11.422367] RIP [] hswep_uncore_cpu_init+0x52/0xa0 [ 11.425174] RSP [ 11.426588] CR2: 0088 [ 11.427978] ---[ end trace d8adbfe4355f5160 ]--- [ 11.430006] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.430006] [ 11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.433354] Please find the full kernel trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
** 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 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:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2b00 -/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic - kdump initrd: -/var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic + /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic + kdump initrd: + /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic current state:ready to kdump kexec command: - /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz - + /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz The kernel trace [ 10.738064] BUG: unable to handle kernel NULL pointer dereference at 0088 [ 10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0 - [ 10.743571] PGD 0 + [ 10.743571] PGD 0 [ 10.744482] Oops: [#1] SMP [ 10.745615] Modules linked in: [ 10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic #49~16.04.1-Ubuntu [ 10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [ 10.752574] task: 8f16b2938ec0 task.stack: 8f16b294 [ 10.754892] RIP: 0010:[] [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.758371] RSP: 0018:8f16b2943e40 EFLAGS: 00010206 [ 10.760337] RAX: 0050 RBX: RCX: 238a [ 10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: [ 10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 89231a97 [ 10.767968] R10: eac07000 R11: R12: 89c1a030 [ 10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 8f16b2c19300 [ 10.772894] FS: () GS:8f16b2c0() knlGS: [ 10.775945] CS: 0010 DS: ES: CR0: 80050033 [ 10.777935] CR2: 0088 CR3: 2d806000 CR4: 001406f0 [ 10.780398] Stack: [ 10.781154] 8f16b2943e50 df388e 8f16b2943e88 89d8b292 [ 10.884602] 0105 89d8b196 89c0daf8 [ 10.887394] 8f16b2c19300 8f16b2943f08 88e02190 88ea377f [ 10.890699] Call Trace: [ 10.891596] [] intel_uncore_init+0xfc/0x2d6 [ 10.893587] [] do_one_initcall+0x50/0x1a0 [ 11.397431] [] ? parse_args+0x2cf/0x490 [ 11.399313] [] kernel_init_freeable+0x178/0x217 [ 11.402112] [] kernel_init+0xe/0x100 [ 11.404013] [] ret_from_fork+0x1f/0x40 [ 11.405895] [] ? rest_init+0x80/0x80 - [ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00 + [ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00 [ 11.422367] RIP [] hswep_uncore_cpu_init+0x52/0xa0 [ 11.425174] RSP [ 11.426588] CR2: 0088 [ 11.427978] ---[ end trace d8adbfe4355f5160 ]--- [ 11.430006] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 - [ 11.430006] + [ 11.430006] [ 11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 - [ 11.433354] + [ 11.433354] Please find the full kernel trace -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel Status in makedumpfile package in Ubuntu: Confirmed Bug description: I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.
[Kernel-packages] [Bug 1687779] [NEW] Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
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:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2b00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz The kernel trace [ 10.738064] BUG: unable to handle kernel NULL pointer dereference at 0088 [ 10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.743571] PGD 0 [ 10.744482] Oops: [#1] SMP [ 10.745615] Modules linked in: [ 10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic #49~16.04.1-Ubuntu [ 10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [ 10.752574] task: 8f16b2938ec0 task.stack: 8f16b294 [ 10.754892] RIP: 0010:[] [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.758371] RSP: 0018:8f16b2943e40 EFLAGS: 00010206 [ 10.760337] RAX: 0050 RBX: RCX: 238a [ 10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: [ 10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 89231a97 [ 10.767968] R10: eac07000 R11: R12: 89c1a030 [ 10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 8f16b2c19300 [ 10.772894] FS: () GS:8f16b2c0() knlGS: [ 10.775945] CS: 0010 DS: ES: CR0: 80050033 [ 10.777935] CR2: 0088 CR3: 2d806000 CR4: 001406f0 [ 10.780398] Stack: [ 10.781154] 8f16b2943e50 df388e 8f16b2943e88 89d8b292 [ 10.884602] 0105 89d8b196 89c0daf8 [ 10.887394] 8f16b2c19300 8f16b2943f08 88e02190 88ea377f [ 10.890699] Call Trace: [ 10.891596] [] intel_uncore_init+0xfc/0x2d6 [ 10.893587] [] do_one_initcall+0x50/0x1a0 [ 11.397431] [] ? parse_args+0x2cf/0x490 [ 11.399313] [] kernel_init_freeable+0x178/0x217 [ 11.402112] [] kernel_init+0xe/0x100 [ 11.404013] [] ret_from_fork+0x1f/0x40 [ 11.405895] [] ? rest_init+0x80/0x80 [ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00 [ 11.422367] RIP [] hswep_uncore_cpu_init+0x52/0xa0 [ 11.425174] RSP [ 11.426588] CR2: 0088 [ 11.427978] ---[ end trace d8adbfe4355f5160 ]--- [ 11.430006] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.430006] [ 11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.433354] Please find the full kernel trace ** Affects: makedumpfile (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: kdump-tools ** Attachment added: "full-kernel-trace" https://bugs.launchpad.net/bugs/1687779/+attachment/4871072/+files/kdump-kernel-trace.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel Status in makedumpfile package in Ubuntu: Confirmed Bug description: 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:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2b00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb sys
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
@michal did you try this kernel: https://people.canonical.com/~jesse/lp1679823v2/ ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: Confirmed Status in linux-hwe-edge source package in Yakkety: Confirmed Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
Success. #38 works with ixgbe @Jesse thanks and good job ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: Confirmed Status in linux-hwe-edge source package in Yakkety: Confirmed Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
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 Kernel Packages, which is subscribed to linux in 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) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: Confirmed Status in linux-hwe-edge source package in Yakkety: Confirmed Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
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 Kernel Packages, which is subscribed to linux in 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) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: New Status in linux-hwe-edge source package in Yakkety: New Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: New Status in linux-hwe-edge source package in Zesty: New Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
@Joseph, I tried with 4.10.0-20-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49) Status in Linux: Unknown Status in neutron: New Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: New Status in linux-hwe-edge source package in Yakkety: New Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: New Status in linux-hwe-edge source package in Zesty: New Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
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.255163] ha-b5c29032-6c: Invalid MTU 8950 requested, hw max 1500 Apr 25 19:44:13 controller003 kernel: [ 60.227413] ha-f1dd45e0-53: Invalid MTU 8950 requested, hw max 1500 Apr 25 19:44:14 controller003 kernel: [ 61.453602] ha-855d4750-e4: Invalid MTU 8950 requested, hw max 1500 Apr 25 19:44:30 controller003 kernel: [ 76.610249] ha-bd9574b4-21: Invalid MTU 8950 requested, hw max 1500 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49) Status in Linux: Unknown Status in neutron: New Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: New Status in linux-hwe-edge source package in Yakkety: New Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: New Status in linux-hwe-edge source package in Zesty: New Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
@Joseph, 4.10.0-20-generic works for me. Thanks ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49) Status in Linux: Unknown Status in neutron: New Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: New Status in linux-hwe-edge source package in Yakkety: New Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: New Status in linux-hwe-edge source package in Zesty: New Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10
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 linux-image-4.8.0-46-generic4.8.0-46.49~16.04.1 amd64Linux kernel image for version 4.8.0 on 64 bit x86 SMP ii linux-image-4.8.0-49-generic4.8.0-49.52~16.04.1 amd64Linux kernel image for version 4.8.0 on 64 bit x86 SMP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49) Status in Linux: Unknown Status in neutron: New Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10
@Joseph, nop. :/ In the Bugzilla it seems tagged for 4.10.1 release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] [NEW] bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10
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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-hwe-edge (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: linux-hwe-edge (Ubuntu) Importance: Undecided Status: New ** No longer affects: vlan (Ubuntu) ** Description changed: - Since I upgrade the kernel from linux-image-4.8.0-46-generic to linux- - image-extra-4.10.0-14-generic I'm facing when I want to change the MTU. + 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 - link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff + link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 - link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff + link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 - link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff + link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument - root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog + root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: 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 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 r
