[Kernel-packages] [Bug 1650635] Re: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled.
This bug was fixed in the package linux - 4.4.0-59.80 --- linux (4.4.0-59.80) xenial; urgency=low [ John Donnelly ] * Release Tracking Bug - LP: #1654282 * [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails (LP: #1651602) - (fix) nvme: only require 1 interrupt vector, not 2+ linux (4.4.0-58.79) xenial; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1651402 * Support ACPI probe for IIO sensor drivers from ST Micro (LP: #1650123) - SAUCE: iio: st_sensors: match sensors using ACPI handle - SAUCE: iio: st_accel: Support sensor i2c probe using acpi - SAUCE: iio: st_pressure: Support i2c probe using acpi - [Config] CONFIG_HTS221=m, CONFIG_HTS221_I2C=m, CONFIG_HTS221_SPI=m * Fix channel data parsing in ST Micro sensor IIO drivers (LP: #1650189) - SAUCE: iio: common: st_sensors: fix channel data parsing * ST Micro lng2dm 3-axis "femto" accelerometer support (LP: #1650112) - SAUCE: iio: st-accel: add support for lis2dh12 - SAUCE: iio: st_sensors: support active-low interrupts - SAUCE: iio: accel: Add support for the h3lis331dl accelerometer - SAUCE: iio: st_sensors: verify interrupt event to status - SAUCE: iio: st_sensors: support open drain mode - SAUCE: iio:st_sensors: fix power regulator usage - SAUCE: iio: st_sensors: switch to a threaded interrupt - SAUCE: iio: accel: st_accel: Add lis3l02dq support - SAUCE: iio: st_sensors: fix scale configuration for h3lis331dl - SAUCE: iio: accel: st_accel: add support to lng2dm - SAUCE: iio: accel: st_accel: inline per-sensor data - SAUCE: Documentation: dt: iio: accel: add lng2dm sensor device binding * ST Micro hts221 relative humidity sensor support (LP: #1650116) - SAUCE: iio: humidity: add support to hts221 rh/temp combo device - SAUCE: Documentation: dt: iio: humidity: add hts221 sensor device binding - SAUCE: iio: humidity: remove - SAUCE: iio: humidity: Support acpi probe for hts211 * crypto : tolerate new crypto hardware for z Systems (LP: #1644557) - s390/zcrypt: Introduce CEX6 toleration * Acer, Inc ID 5986:055a is useless after 14.04.2 installed. (LP: #1433906) - uvcvideo: uvc_scan_fallback() for webcams with broken chain * vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled. (LP: #1650635) - vmxnet3: segCnt can be 1 for LRO packets * system freeze when swapping to encrypted swap partition (LP: #1647400) - mm, oom: rework oom detection - mm: throttle on IO only when there are too many dirty and writeback pages * Kernel Fixes to get TCMU File Backed Optical to work (LP: #1646204) - target/user: Use sense_reason_t in tcmu_queue_cmd_ring - target/user: Return an error if cmd data size is too large - target/user: Fix comments to not refer to data ring - SAUCE: (no-up) target/user: Fix use-after-free of tcmu_cmds if they are expired * CVE-2016-9756 - KVM: x86: drop error recovery in em_jmp_far and em_ret_far * Dell Precision 5520 & 3520 freezes at login screent (LP: #1650054) - ACPI / blacklist: add _REV quirks for Dell Precision 5520 and 3520 * CVE-2016-9794 - ALSA: pcm : Call kill_fasync() in stream lock * Allow fuse user namespace mounts by default in xenial (LP: #1634964) - (namespace) mnt: Move the FS_USERNS_MOUNT check into sget_userns - (namespace) Revert "UBUNTU: SAUCE: fs: Refuse uid/gid changes which don't map into s_user_ns" - (namespace) fs: Refuse uid/gid changes which don't map into s_user_ns - (namespace) Revert "UBUNTU: SAUCE: fs: Update posix_acl support to handle user namespace mounts" - (namespace) vfs: Verify acls are valid within superblock's s_user_ns. - SAUCE: (namespace) posix_acl: Export posix_acl_fix_xattr_userns() to modules - SAUCE: (namespace) fuse: Translate ids in posix acl xattrs - (namespace) vfs: Don't modify inodes with a uid or gid unknown to the vfs - (namespace) vfs: Don't create inodes with a uid or gid unknown to the vfs - (namespace) Revert "UBUNTU: SAUCE: quota: Require that qids passed to dqget() be valid and map into s_user_ns" - (namespace) Revert "UBUNTU: SAUCE: quota: Convert ids relative to s_user_ns" - (namespace) quota: Ensure qids map to the filesystem - (namespace) quota: Handle quota data stored in s_user_ns in quota_setxquota - (namespace) dquot: For now explicitly don't support filesystems outside of init_user_ns - (namespace) Revert "UBUNTU: SAUCE: ima/evm: Allow root in s_user_ns to set xattrs" - SAUCE: (namespace) security/integrity: Harden against malformed xattrs - (namespace) Revert "UBUNTU: SAUCE: fs: Allow superblock owner to change ownership of inodes with unmappable ids" - SAUCE: (namespace) fs: Allow superblock owner to change ownership of inodes - (namespace) Revert "UBUNTU: SAUCE: fs: Don't remove suid for CAP_FSETID in
[Kernel-packages] [Bug 1650635] Re: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled.
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1650635 Title: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled. Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: [Impact] It has been brought to my attention that a Trusty Vmware Virtual Machine running kernel v4.4.0-36 crashed with the following stacktrace : PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" ... #0 [88042d683aa0] machine_kexec at 8105987c #1 [88042d683af8] crash_kexec at 81105d23 #2 [88042d683bc0] oops_end at 81030a79 #3 [88042d683be8] die at 81030f7b #4 [88042d683c18] do_trap at 8102e04d #5 [88042d683c68] do_error_trap at 8102e5a7 #6 [88042d683d20] do_invalid_op at 8102e840 #7 [88042d683d30] invalid_op at 817f900e [exception RIP: vmxnet3_rq_rx_complete+3016] RIP: c004e448 RSP: 88042d683de8 RFLAGS: 00010246 RAX: 0001 RBX: 880424099668 RCX: RDX: 05f2 RSI: 05f2 RDI: 88042a61f400 RBP: 88042d683e50 R8: R9: R10: 88042902b470 R11: 8804293406a8 R12: 880424098840 R13: 880424099580 R14: 88042a61ec00 R15: 88042933ae00 ORIG_RAX: CS: 0010 SS: #8 [88042d683de0] vmxnet3_rq_rx_complete at c004dcfa [vmxnet3] #9 [88042d683e58] vmxnet3_poll_rx_only at c004e60a [vmxnet3] #10 [88042d683e90] net_rx_action at 816f3544 #11 [88042d683f00] __do_softirq at 81081e7d #12 [88042d683f68] irq_exit at 81082255 #13 [88042d683f78] do_IRQ at 817f9ee6 --- --- #14 [880426c73f30] ret_from_intr at 817f7fc2 [exception RIP: unknown or invalid address] RIP: fffb RSP: 7fe17e59bf48 RFLAGS: 0001 RAX: 7fe18564ed58 RBX: 7fe2064ce848 RCX: 7fe185612d60 RDX: 7fe20b47eb30 RSI: 7fe185640d38 RDI: 7fe18564ed50 RBP: 817f7fe5 R8: 7fe185100068 R9: 00037ce0 R10: 00134ad8 R11: 7fe17e4b7028 R12: 7fe185100068 R13: 7fe185632380 R14: R15: 81003a64 ORIG_RAX: 0001 CS: 7fe185640d38 SS: ff91 bt: WARNING: possibly bogus exception frame RIP: 004e92bb RSP: 7fe20b47ea40 RFLAGS: 0283 RAX: 0001 RBX: 7fe18564ed58 RCX: fffb RDX: 7fe185640d38 RSI: 0001 RDI: 7fe17e59bf48 RBP: 7fe185100068 R8: 7fe18564ed50 R9: 7fe185640d38 R10: 7fe20b47eb30 R11: 7fe185612d60 R12: 00037ce0 R13: 00134ad8 R14: 7fe17e4b7028 R15: 7fe2064ce848 ORIG_RAX: ff91 CS: 0033 SS: 002b [Test Case] * There is no real reproducer, the problem occurred randomly if SegCnt == 1 on a Trusty VMware Virtual Machine using Xenial kernel with LRO enabled in the VMware environment. [Regression Potential] * none expected * Commit can be found in upstream linux stable * Yakkety and Zesty kernel has the patch already [Other Info] * Upstream commit : 5021953 vmxnet3: segCnt can be 1 for LRO packets [Original Description] It has been brought to my attention that a Trusty Vmware Virtual Machine running kernel v4.4.0-36 crashed with the following stacktrace : PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" ... #0 [88042d683aa0] machine_kexec at 8105987c #1 [88042d683af8] crash_kexec at 81105d23 #2 [88042d683bc0] oops_end at 81030a79 #3 [88042d683be8] die at 81030f7b #4 [88042d683c18] do_trap at 8102e04d #5 [88042d683c68] do_error_trap at 8102e5a7 #6 [88042d683d20] do_invalid_op at 8102e840 #7 [88042d683d30] invalid_op at 817f900e [exception RIP: vmxnet3_rq_rx_complete+3016] RIP: c004e448 RSP: 88042d683de8 RFLAGS: 00010246 RAX: 0001 RBX: 880424099668 RCX: RDX: 05f2 RSI: 05f2 RDI: 88042a61f400 RBP: 88042d683e50 R8: R9: R10: 88042902b470 R11: 8804293406a8 R12: 880424098840 R13: 880424099580 R14: 88042a61ec00 R15: 88042933ae00 ORIG_RAX: CS: 0010 SS: #8 [88042d683de0] vmxnet3_rq_rx_complete at c004dcfa [vmxnet3] #9 [88042d683e58] vmxnet3_poll_rx_only at c004e60a [vmxnet3] #10 [88042d683e90] net_rx_action at
[Kernel-packages] [Bug 1650635] Re: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled.
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1650635 Title: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled. Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: [Impact] It has been brought to my attention that a Trusty Vmware Virtual Machine running kernel v4.4.0-36 crashed with the following stacktrace : PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" ... #0 [88042d683aa0] machine_kexec at 8105987c #1 [88042d683af8] crash_kexec at 81105d23 #2 [88042d683bc0] oops_end at 81030a79 #3 [88042d683be8] die at 81030f7b #4 [88042d683c18] do_trap at 8102e04d #5 [88042d683c68] do_error_trap at 8102e5a7 #6 [88042d683d20] do_invalid_op at 8102e840 #7 [88042d683d30] invalid_op at 817f900e [exception RIP: vmxnet3_rq_rx_complete+3016] RIP: c004e448 RSP: 88042d683de8 RFLAGS: 00010246 RAX: 0001 RBX: 880424099668 RCX: RDX: 05f2 RSI: 05f2 RDI: 88042a61f400 RBP: 88042d683e50 R8: R9: R10: 88042902b470 R11: 8804293406a8 R12: 880424098840 R13: 880424099580 R14: 88042a61ec00 R15: 88042933ae00 ORIG_RAX: CS: 0010 SS: #8 [88042d683de0] vmxnet3_rq_rx_complete at c004dcfa [vmxnet3] #9 [88042d683e58] vmxnet3_poll_rx_only at c004e60a [vmxnet3] #10 [88042d683e90] net_rx_action at 816f3544 #11 [88042d683f00] __do_softirq at 81081e7d #12 [88042d683f68] irq_exit at 81082255 #13 [88042d683f78] do_IRQ at 817f9ee6 --- --- #14 [880426c73f30] ret_from_intr at 817f7fc2 [exception RIP: unknown or invalid address] RIP: fffb RSP: 7fe17e59bf48 RFLAGS: 0001 RAX: 7fe18564ed58 RBX: 7fe2064ce848 RCX: 7fe185612d60 RDX: 7fe20b47eb30 RSI: 7fe185640d38 RDI: 7fe18564ed50 RBP: 817f7fe5 R8: 7fe185100068 R9: 00037ce0 R10: 00134ad8 R11: 7fe17e4b7028 R12: 7fe185100068 R13: 7fe185632380 R14: R15: 81003a64 ORIG_RAX: 0001 CS: 7fe185640d38 SS: ff91 bt: WARNING: possibly bogus exception frame RIP: 004e92bb RSP: 7fe20b47ea40 RFLAGS: 0283 RAX: 0001 RBX: 7fe18564ed58 RCX: fffb RDX: 7fe185640d38 RSI: 0001 RDI: 7fe17e59bf48 RBP: 7fe185100068 R8: 7fe18564ed50 R9: 7fe185640d38 R10: 7fe20b47eb30 R11: 7fe185612d60 R12: 00037ce0 R13: 00134ad8 R14: 7fe17e4b7028 R15: 7fe2064ce848 ORIG_RAX: ff91 CS: 0033 SS: 002b [Test Case] * There is no real reproducer, the problem occurred randomly if SegCnt == 1 on a Trusty VMware Virtual Machine using Xenial kernel with LRO enabled in the VMware environment. [Regression Potential] * none expected * Commit can be found in upstream linux stable * Yakkety and Zesty kernel has the patch already [Other Info] * Upstream commit : 5021953 vmxnet3: segCnt can be 1 for LRO packets [Original Description] It has been brought to my attention that a Trusty Vmware Virtual Machine running kernel v4.4.0-36 crashed with the following stacktrace : PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" ... #0 [88042d683aa0] machine_kexec at 8105987c #1 [88042d683af8] crash_kexec at 81105d23 #2 [88042d683bc0] oops_end at 81030a79 #3 [88042d683be8] die at 81030f7b #4 [88042d683c18] do_trap at 8102e04d #5 [88042d683c68] do_error_trap at 8102e5a7 #6 [88042d683d20] do_invalid_op at 8102e840 #7 [88042d683d30] invalid_op at 817f900e [exception RIP: vmxnet3_rq_rx_complete+3016] RIP: c004e448 RSP: 88042d683de8 RFLAGS: 00010246 RAX: 0001 RBX:
[Kernel-packages] [Bug 1650635] Re: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled.
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1650635 Title: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled. Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: [Impact] It has been brought to my attention that a Trusty Vmware Virtual Machine running kernel v4.4.0-36 crashed with the following stacktrace : PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" ... #0 [88042d683aa0] machine_kexec at 8105987c #1 [88042d683af8] crash_kexec at 81105d23 #2 [88042d683bc0] oops_end at 81030a79 #3 [88042d683be8] die at 81030f7b #4 [88042d683c18] do_trap at 8102e04d #5 [88042d683c68] do_error_trap at 8102e5a7 #6 [88042d683d20] do_invalid_op at 8102e840 #7 [88042d683d30] invalid_op at 817f900e [exception RIP: vmxnet3_rq_rx_complete+3016] RIP: c004e448 RSP: 88042d683de8 RFLAGS: 00010246 RAX: 0001 RBX: 880424099668 RCX: RDX: 05f2 RSI: 05f2 RDI: 88042a61f400 RBP: 88042d683e50 R8: R9: R10: 88042902b470 R11: 8804293406a8 R12: 880424098840 R13: 880424099580 R14: 88042a61ec00 R15: 88042933ae00 ORIG_RAX: CS: 0010 SS: #8 [88042d683de0] vmxnet3_rq_rx_complete at c004dcfa [vmxnet3] #9 [88042d683e58] vmxnet3_poll_rx_only at c004e60a [vmxnet3] #10 [88042d683e90] net_rx_action at 816f3544 #11 [88042d683f00] __do_softirq at 81081e7d #12 [88042d683f68] irq_exit at 81082255 #13 [88042d683f78] do_IRQ at 817f9ee6 --- --- #14 [880426c73f30] ret_from_intr at 817f7fc2 [exception RIP: unknown or invalid address] RIP: fffb RSP: 7fe17e59bf48 RFLAGS: 0001 RAX: 7fe18564ed58 RBX: 7fe2064ce848 RCX: 7fe185612d60 RDX: 7fe20b47eb30 RSI: 7fe185640d38 RDI: 7fe18564ed50 RBP: 817f7fe5 R8: 7fe185100068 R9: 00037ce0 R10: 00134ad8 R11: 7fe17e4b7028 R12: 7fe185100068 R13: 7fe185632380 R14: R15: 81003a64 ORIG_RAX: 0001 CS: 7fe185640d38 SS: ff91 bt: WARNING: possibly bogus exception frame RIP: 004e92bb RSP: 7fe20b47ea40 RFLAGS: 0283 RAX: 0001 RBX: 7fe18564ed58 RCX: fffb RDX: 7fe185640d38 RSI: 0001 RDI: 7fe17e59bf48 RBP: 7fe185100068 R8: 7fe18564ed50 R9: 7fe185640d38 R10: 7fe20b47eb30 R11: 7fe185612d60 R12: 00037ce0 R13: 00134ad8 R14: 7fe17e4b7028 R15: 7fe2064ce848 ORIG_RAX: ff91 CS: 0033 SS: 002b [Test Case] * There is no real reproducer, the problem occurred randomly if SegCnt == 1 on a Trusty VMware Virtual Machine using Xenial kernel with LRO enabled in the VMware environment. [Regression Potential] * none expected * Commit can be found in upstream linux stable * Yakkety and Zesty kernel has the patch already [Other Info] * Upstream commit : 5021953 vmxnet3: segCnt can be 1 for LRO packets [Original Description] It has been brought to my attention that a Trusty Vmware Virtual Machine running kernel v4.4.0-36 crashed with the following stacktrace : PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" ... #0 [88042d683aa0] machine_kexec at 8105987c #1 [88042d683af8] crash_kexec at 81105d23 #2 [88042d683bc0] oops_end at 81030a79 #3 [88042d683be8] die at 81030f7b #4 [88042d683c18] do_trap at 8102e04d #5 [88042d683c68] do_error_trap at 8102e5a7 #6 [88042d683d20] do_invalid_op at 8102e840 #7 [88042d683d30] invalid_op at 817f900e [exception RIP: vmxnet3_rq_rx_complete+3016] RIP: c004e448 RSP: 88042d683de8 RFLAGS: 00010246 RAX: 0001 RBX: 880424099668 RCX: RDX: 05f2 RSI: 05f2 RDI: 88042a61f400 RBP: 88042d683e50 R8: R9: R10: 88042902b470 R11: 8804293406a8 R12: 880424098840 R13: 880424099580 R14: 88042a61ec00 R15: 88042933ae00 ORIG_RAX: CS: 0010 SS: #8 [88042d683de0] vmxnet3_rq_rx_complete at c004dcfa [vmxnet3] #9 [88042d683e58] vmxnet3_poll_rx_only at c004e60a [vmxnet3] #10 [88042d683e90] net_rx_action at
[Kernel-packages] [Bug 1650635] Re: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled.
** Description changed: + [Impact] + It has been brought to my attention that a Trusty Vmware Virtual Machine running kernel v4.4.0-36 crashed with the following stacktrace : - PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" + PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" ... #0 [88042d683aa0] machine_kexec at 8105987c #1 [88042d683af8] crash_kexec at 81105d23 #2 [88042d683bc0] oops_end at 81030a79 #3 [88042d683be8] die at 81030f7b #4 [88042d683c18] do_trap at 8102e04d #5 [88042d683c68] do_error_trap at 8102e5a7 #6 [88042d683d20] do_invalid_op at 8102e840 #7 [88042d683d30] invalid_op at 817f900e [exception RIP: vmxnet3_rq_rx_complete+3016] RIP: c004e448 RSP: 88042d683de8 RFLAGS: 00010246 RAX: 0001 RBX: 880424099668 RCX: RDX: 05f2 RSI: 05f2 RDI: 88042a61f400 RBP: 88042d683e50 R8: R9: R10: 88042902b470 R11: 8804293406a8 R12: 880424098840 R13: 880424099580 R14: 88042a61ec00 R15: 88042933ae00 ORIG_RAX: CS: 0010 SS: #8 [88042d683de0] vmxnet3_rq_rx_complete at c004dcfa [vmxnet3] #9 [88042d683e58] vmxnet3_poll_rx_only at c004e60a [vmxnet3] #10 [88042d683e90] net_rx_action at 816f3544 #11 [88042d683f00] __do_softirq at 81081e7d #12 [88042d683f68] irq_exit at 81082255 #13 [88042d683f78] do_IRQ at 817f9ee6 --- --- #14 [880426c73f30] ret_from_intr at 817f7fc2 [exception RIP: unknown or invalid address] RIP: fffb RSP: 7fe17e59bf48 RFLAGS: 0001 RAX: 7fe18564ed58 RBX: 7fe2064ce848 RCX: 7fe185612d60 RDX: 7fe20b47eb30 RSI: 7fe185640d38 RDI: 7fe18564ed50 RBP: 817f7fe5 R8: 7fe185100068 R9: 00037ce0 R10: 00134ad8 R11: 7fe17e4b7028 R12: 7fe185100068 R13: 7fe185632380 R14: R15: 81003a64 ORIG_RAX: 0001 CS: 7fe185640d38 SS: ff91 bt: WARNING: possibly bogus exception frame RIP: 004e92bb RSP: 7fe20b47ea40 RFLAGS: 0283 RAX: 0001 RBX: 7fe18564ed58 RCX: fffb RDX: 7fe185640d38 RSI: 0001 RDI: 7fe17e59bf48 RBP: 7fe185100068 R8: 7fe18564ed50 R9: 7fe185640d38 R10: 7fe20b47eb30 R11: 7fe185612d60 R12: 00037ce0 R13: 00134ad8 R14: 7fe17e4b7028 R15: 7fe2064ce848 ORIG_RAX: ff91 CS: 0033 SS: 002b + + [Test Case] + + * There is no real reproducer, the problem occured on a Ubuntu VMware + Virtual Machine with LRO enabled in the VMware environment. + + [Regression Potential] + + * none expected + * Commit can be found in upstream linux stable + * Yakkety and Zesty kernel has the patch already + + [Other Info] + + * Upstream commit : +5021953 vmxnet3: segCnt can be 1 for LRO packets + + [Original Description] + + It has been brought to my attention that a Trusty Vmware Virtual Machine + running kernel v4.4.0-36 crashed with the following stacktrace : + + PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" + ... + #0 [88042d683aa0] machine_kexec at 8105987c + #1 [88042d683af8] crash_kexec at 81105d23 + #2 [88042d683bc0] oops_end at 81030a79 + #3 [88042d683be8] die at 81030f7b + #4 [88042d683c18] do_trap at 8102e04d + #5 [88042d683c68] do_error_trap at 8102e5a7 + #6 [88042d683d20] do_invalid_op at 8102e840 + #7 [88042d683d30] invalid_op at 817f900e + [exception RIP: vmxnet3_rq_rx_complete+3016] + RIP: c004e448 RSP: 88042d683de8 RFLAGS: 00010246 + RAX: 0001 RBX: 880424099668 RCX: + RDX: 05f2 RSI: 05f2 RDI: 88042a61f400 + RBP: 88042d683e50 R8: R9: + R10: 88042902b470 R11: 8804293406a8 R12: 880424098840 + R13: 880424099580 R14: 88042a61ec00 R15: 88042933ae00 + ORIG_RAX: CS: 0010 SS: + #8 [88042d683de0] vmxnet3_rq_rx_complete at c004dcfa [vmxnet3] + #9 [88042d683e58] vmxnet3_poll_rx_only at c004e60a [vmxnet3] + #10 [88042d683e90] net_rx_action at 816f3544 + #11 [88042d683f00] __do_softirq at 81081e7d + #12 [88042d683f68] irq_exit at 81082255 + #13 [88042d683f78] do_IRQ at 817f9ee6 + --- --- + #14 [880426c73f30] ret_from_intr at 817f7fc2 + [exception RIP: unknown or invalid address] + RIP: fffb RSP: 7fe17e59bf48
[Kernel-packages] [Bug 1650635] Re: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled.
Patch has been submitted to Ubuntu kernel team earlier today. -- 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/1650635 Title: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled. Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: It has been brought to my attention that a Trusty Vmware Virtual Machine running kernel v4.4.0-36 crashed with the following stacktrace : PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" ... #0 [88042d683aa0] machine_kexec at 8105987c #1 [88042d683af8] crash_kexec at 81105d23 #2 [88042d683bc0] oops_end at 81030a79 #3 [88042d683be8] die at 81030f7b #4 [88042d683c18] do_trap at 8102e04d #5 [88042d683c68] do_error_trap at 8102e5a7 #6 [88042d683d20] do_invalid_op at 8102e840 #7 [88042d683d30] invalid_op at 817f900e [exception RIP: vmxnet3_rq_rx_complete+3016] RIP: c004e448 RSP: 88042d683de8 RFLAGS: 00010246 RAX: 0001 RBX: 880424099668 RCX: RDX: 05f2 RSI: 05f2 RDI: 88042a61f400 RBP: 88042d683e50 R8: R9: R10: 88042902b470 R11: 8804293406a8 R12: 880424098840 R13: 880424099580 R14: 88042a61ec00 R15: 88042933ae00 ORIG_RAX: CS: 0010 SS: #8 [88042d683de0] vmxnet3_rq_rx_complete at c004dcfa [vmxnet3] #9 [88042d683e58] vmxnet3_poll_rx_only at c004e60a [vmxnet3] #10 [88042d683e90] net_rx_action at 816f3544 #11 [88042d683f00] __do_softirq at 81081e7d #12 [88042d683f68] irq_exit at 81082255 #13 [88042d683f78] do_IRQ at 817f9ee6 --- --- #14 [880426c73f30] ret_from_intr at 817f7fc2 [exception RIP: unknown or invalid address] RIP: fffb RSP: 7fe17e59bf48 RFLAGS: 0001 RAX: 7fe18564ed58 RBX: 7fe2064ce848 RCX: 7fe185612d60 RDX: 7fe20b47eb30 RSI: 7fe185640d38 RDI: 7fe18564ed50 RBP: 817f7fe5 R8: 7fe185100068 R9: 00037ce0 R10: 00134ad8 R11: 7fe17e4b7028 R12: 7fe185100068 R13: 7fe185632380 R14: R15: 81003a64 ORIG_RAX: 0001 CS: 7fe185640d38 SS: ff91 bt: WARNING: possibly bogus exception frame RIP: 004e92bb RSP: 7fe20b47ea40 RFLAGS: 0283 RAX: 0001 RBX: 7fe18564ed58 RCX: fffb RDX: 7fe185640d38 RSI: 0001 RDI: 7fe17e59bf48 RBP: 7fe185100068 R8: 7fe18564ed50 R9: 7fe185640d38 R10: 7fe20b47eb30 R11: 7fe185612d60 R12: 00037ce0 R13: 00134ad8 R14: 7fe17e4b7028 R15: 7fe2064ce848 ORIG_RAX: ff91 CS: 0033 SS: 002b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635/+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 1650635] Re: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled.
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: linux (Ubuntu) Assignee: Eric Desrochers (slashd) => (unassigned) ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- 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/1650635 Title: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled. Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: It has been brought to my attention that a Trusty Vmware Virtual Machine running kernel v4.4.0-36 crashed with the following stacktrace : PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" ... #0 [88042d683aa0] machine_kexec at 8105987c #1 [88042d683af8] crash_kexec at 81105d23 #2 [88042d683bc0] oops_end at 81030a79 #3 [88042d683be8] die at 81030f7b #4 [88042d683c18] do_trap at 8102e04d #5 [88042d683c68] do_error_trap at 8102e5a7 #6 [88042d683d20] do_invalid_op at 8102e840 #7 [88042d683d30] invalid_op at 817f900e [exception RIP: vmxnet3_rq_rx_complete+3016] RIP: c004e448 RSP: 88042d683de8 RFLAGS: 00010246 RAX: 0001 RBX: 880424099668 RCX: RDX: 05f2 RSI: 05f2 RDI: 88042a61f400 RBP: 88042d683e50 R8: R9: R10: 88042902b470 R11: 8804293406a8 R12: 880424098840 R13: 880424099580 R14: 88042a61ec00 R15: 88042933ae00 ORIG_RAX: CS: 0010 SS: #8 [88042d683de0] vmxnet3_rq_rx_complete at c004dcfa [vmxnet3] #9 [88042d683e58] vmxnet3_poll_rx_only at c004e60a [vmxnet3] #10 [88042d683e90] net_rx_action at 816f3544 #11 [88042d683f00] __do_softirq at 81081e7d #12 [88042d683f68] irq_exit at 81082255 #13 [88042d683f78] do_IRQ at 817f9ee6 --- --- #14 [880426c73f30] ret_from_intr at 817f7fc2 [exception RIP: unknown or invalid address] RIP: fffb RSP: 7fe17e59bf48 RFLAGS: 0001 RAX: 7fe18564ed58 RBX: 7fe2064ce848 RCX: 7fe185612d60 RDX: 7fe20b47eb30 RSI: 7fe185640d38 RDI: 7fe18564ed50 RBP: 817f7fe5 R8: 7fe185100068 R9: 00037ce0 R10: 00134ad8 R11: 7fe17e4b7028 R12: 7fe185100068 R13: 7fe185632380 R14: R15: 81003a64 ORIG_RAX: 0001 CS: 7fe185640d38 SS: ff91 bt: WARNING: possibly bogus exception frame RIP: 004e92bb RSP: 7fe20b47ea40 RFLAGS: 0283 RAX: 0001 RBX: 7fe18564ed58 RCX: fffb RDX: 7fe185640d38 RSI: 0001 RDI: 7fe17e59bf48 RBP: 7fe185100068 R8: 7fe18564ed50 R9: 7fe185640d38 R10: 7fe20b47eb30 R11: 7fe185612d60 R12: 00037ce0 R13: 00134ad8 R14: 7fe17e4b7028 R15: 7fe2064ce848 ORIG_RAX: ff91 CS: 0033 SS: 002b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635/+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 1650635] Re: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled.
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- 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/1650635 Title: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled. Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: It has been brought to my attention that a Trusty Vmware Virtual Machine running kernel v4.4.0-36 crashed with the following stacktrace : PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" ... #0 [88042d683aa0] machine_kexec at 8105987c #1 [88042d683af8] crash_kexec at 81105d23 #2 [88042d683bc0] oops_end at 81030a79 #3 [88042d683be8] die at 81030f7b #4 [88042d683c18] do_trap at 8102e04d #5 [88042d683c68] do_error_trap at 8102e5a7 #6 [88042d683d20] do_invalid_op at 8102e840 #7 [88042d683d30] invalid_op at 817f900e [exception RIP: vmxnet3_rq_rx_complete+3016] RIP: c004e448 RSP: 88042d683de8 RFLAGS: 00010246 RAX: 0001 RBX: 880424099668 RCX: RDX: 05f2 RSI: 05f2 RDI: 88042a61f400 RBP: 88042d683e50 R8: R9: R10: 88042902b470 R11: 8804293406a8 R12: 880424098840 R13: 880424099580 R14: 88042a61ec00 R15: 88042933ae00 ORIG_RAX: CS: 0010 SS: #8 [88042d683de0] vmxnet3_rq_rx_complete at c004dcfa [vmxnet3] #9 [88042d683e58] vmxnet3_poll_rx_only at c004e60a [vmxnet3] #10 [88042d683e90] net_rx_action at 816f3544 #11 [88042d683f00] __do_softirq at 81081e7d #12 [88042d683f68] irq_exit at 81082255 #13 [88042d683f78] do_IRQ at 817f9ee6 --- --- #14 [880426c73f30] ret_from_intr at 817f7fc2 [exception RIP: unknown or invalid address] RIP: fffb RSP: 7fe17e59bf48 RFLAGS: 0001 RAX: 7fe18564ed58 RBX: 7fe2064ce848 RCX: 7fe185612d60 RDX: 7fe20b47eb30 RSI: 7fe185640d38 RDI: 7fe18564ed50 RBP: 817f7fe5 R8: 7fe185100068 R9: 00037ce0 R10: 00134ad8 R11: 7fe17e4b7028 R12: 7fe185100068 R13: 7fe185632380 R14: R15: 81003a64 ORIG_RAX: 0001 CS: 7fe185640d38 SS: ff91 bt: WARNING: possibly bogus exception frame RIP: 004e92bb RSP: 7fe20b47ea40 RFLAGS: 0283 RAX: 0001 RBX: 7fe18564ed58 RCX: fffb RDX: 7fe185640d38 RSI: 0001 RDI: 7fe17e59bf48 RBP: 7fe185100068 R8: 7fe18564ed50 R9: 7fe185640d38 R10: 7fe20b47eb30 R11: 7fe185612d60 R12: 00037ce0 R13: 00134ad8 R14: 7fe17e4b7028 R15: 7fe2064ce848 ORIG_RAX: ff91 CS: 0033 SS: 002b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635/+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 1650635] Re: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled.
** Summary changed: - vmxnet3 driver causes kernel panic w/ kernel v4.4 + vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled. -- 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/1650635 Title: vmxnet3 driver could causes kernel panic with v4.4 if LRO enabled. Status in linux package in Ubuntu: In Progress Bug description: It has been brought to my attention that a Trusty Vmware Virtual Machine running kernel v4.4.0-36 crashed with the following stacktrace : PANIC: "kernel BUG at /build/linux-lts-xenial-QiVniY/linux-lts-xenial-4.4.0/drivers/net/vmxnet3/vmxnet3_drv.c:1353!" ... #0 [88042d683aa0] machine_kexec at 8105987c #1 [88042d683af8] crash_kexec at 81105d23 #2 [88042d683bc0] oops_end at 81030a79 #3 [88042d683be8] die at 81030f7b #4 [88042d683c18] do_trap at 8102e04d #5 [88042d683c68] do_error_trap at 8102e5a7 #6 [88042d683d20] do_invalid_op at 8102e840 #7 [88042d683d30] invalid_op at 817f900e [exception RIP: vmxnet3_rq_rx_complete+3016] RIP: c004e448 RSP: 88042d683de8 RFLAGS: 00010246 RAX: 0001 RBX: 880424099668 RCX: RDX: 05f2 RSI: 05f2 RDI: 88042a61f400 RBP: 88042d683e50 R8: R9: R10: 88042902b470 R11: 8804293406a8 R12: 880424098840 R13: 880424099580 R14: 88042a61ec00 R15: 88042933ae00 ORIG_RAX: CS: 0010 SS: #8 [88042d683de0] vmxnet3_rq_rx_complete at c004dcfa [vmxnet3] #9 [88042d683e58] vmxnet3_poll_rx_only at c004e60a [vmxnet3] #10 [88042d683e90] net_rx_action at 816f3544 #11 [88042d683f00] __do_softirq at 81081e7d #12 [88042d683f68] irq_exit at 81082255 #13 [88042d683f78] do_IRQ at 817f9ee6 --- --- #14 [880426c73f30] ret_from_intr at 817f7fc2 [exception RIP: unknown or invalid address] RIP: fffb RSP: 7fe17e59bf48 RFLAGS: 0001 RAX: 7fe18564ed58 RBX: 7fe2064ce848 RCX: 7fe185612d60 RDX: 7fe20b47eb30 RSI: 7fe185640d38 RDI: 7fe18564ed50 RBP: 817f7fe5 R8: 7fe185100068 R9: 00037ce0 R10: 00134ad8 R11: 7fe17e4b7028 R12: 7fe185100068 R13: 7fe185632380 R14: R15: 81003a64 ORIG_RAX: 0001 CS: 7fe185640d38 SS: ff91 bt: WARNING: possibly bogus exception frame RIP: 004e92bb RSP: 7fe20b47ea40 RFLAGS: 0283 RAX: 0001 RBX: 7fe18564ed58 RCX: fffb RDX: 7fe185640d38 RSI: 0001 RDI: 7fe17e59bf48 RBP: 7fe185100068 R8: 7fe18564ed50 R9: 7fe185640d38 R10: 7fe20b47eb30 R11: 7fe185612d60 R12: 00037ce0 R13: 00134ad8 R14: 7fe17e4b7028 R15: 7fe2064ce848 ORIG_RAX: ff91 CS: 0033 SS: 002b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635/+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
