** 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 [ffff88042d683aa0] machine_kexec at ffffffff8105987c
  #1 [ffff88042d683af8] crash_kexec at ffffffff81105d23
  #2 [ffff88042d683bc0] oops_end at ffffffff81030a79
  #3 [ffff88042d683be8] die at ffffffff81030f7b
  #4 [ffff88042d683c18] do_trap at ffffffff8102e04d
  #5 [ffff88042d683c68] do_error_trap at ffffffff8102e5a7
  #6 [ffff88042d683d20] do_invalid_op at ffffffff8102e840
  #7 [ffff88042d683d30] invalid_op at ffffffff817f900e
  [exception RIP: vmxnet3_rq_rx_complete+3016]
  RIP: ffffffffc004e448 RSP: ffff88042d683de8 RFLAGS: 00010246
  RAX: 0000000000000001 RBX: ffff880424099668 RCX: 0000000000000000
  RDX: 00000000000005f2 RSI: 00000000000005f2 RDI: ffff88042a61f400
  RBP: ffff88042d683e50 R8: 0000000000000000 R9: 0000000000000000
  R10: ffff88042902b470 R11: ffff8804293406a8 R12: ffff880424098840
  R13: ffff880424099580 R14: ffff88042a61ec00 R15: ffff88042933ae00
  ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000
  #8 [ffff88042d683de0] vmxnet3_rq_rx_complete at ffffffffc004dcfa [vmxnet3]
  #9 [ffff88042d683e58] vmxnet3_poll_rx_only at ffffffffc004e60a [vmxnet3]
  #10 [ffff88042d683e90] net_rx_action at ffffffff816f3544
  #11 [ffff88042d683f00] __do_softirq at ffffffff81081e7d
  #12 [ffff88042d683f68] irq_exit at ffffffff81082255
  #13 [ffff88042d683f78] do_IRQ at ffffffff817f9ee6
  --- <IRQ stack> ---
  #14 [ffff880426c73f30] ret_from_intr at ffffffff817f7fc2
  [exception RIP: unknown or invalid address]
  RIP: fffffffffffffffb RSP: 00007fe17e59bf48 RFLAGS: 00000001
  RAX: 00007fe18564ed58 RBX: 00007fe2064ce848 RCX: 00007fe185612d60
  RDX: 00007fe20b47eb30 RSI: 00007fe185640d38 RDI: 00007fe18564ed50
  RBP: ffffffff817f7fe5 R8: 00007fe185100068 R9: 0000000000037ce0
  R10: 0000000000134ad8 R11: 00007fe17e4b7028 R12: 00007fe185100068
  R13: 00007fe185632380 R14: 0000000000000000 R15: ffffffff81003a64
  ORIG_RAX: 0000000000000001 CS: 7fe185640d38 SS: ffffffffffffff91
  bt: WARNING: possibly bogus exception frame
  RIP: 00000000004e92bb RSP: 00007fe20b47ea40 RFLAGS: 00000283
  RAX: 0000000000000001 RBX: 00007fe18564ed58 RCX: fffffffffffffffb
  RDX: 00007fe185640d38 RSI: 0000000000000001 RDI: 00007fe17e59bf48
  RBP: 00007fe185100068 R8: 00007fe18564ed50 R9: 00007fe185640d38
  R10: 00007fe20b47eb30 R11: 00007fe185612d60 R12: 0000000000037ce0
  R13: 0000000000134ad8 R14: 00007fe17e4b7028 R15: 00007fe2064ce848
  ORIG_RAX: ffffffffffffff91 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 [ffff88042d683aa0] machine_kexec at ffffffff8105987c
+ #1 [ffff88042d683af8] crash_kexec at ffffffff81105d23
+ #2 [ffff88042d683bc0] oops_end at ffffffff81030a79
+ #3 [ffff88042d683be8] die at ffffffff81030f7b
+ #4 [ffff88042d683c18] do_trap at ffffffff8102e04d
+ #5 [ffff88042d683c68] do_error_trap at ffffffff8102e5a7
+ #6 [ffff88042d683d20] do_invalid_op at ffffffff8102e840
+ #7 [ffff88042d683d30] invalid_op at ffffffff817f900e
+ [exception RIP: vmxnet3_rq_rx_complete+3016]
+ RIP: ffffffffc004e448 RSP: ffff88042d683de8 RFLAGS: 00010246
+ RAX: 0000000000000001 RBX: ffff880424099668 RCX: 0000000000000000
+ RDX: 00000000000005f2 RSI: 00000000000005f2 RDI: ffff88042a61f400
+ RBP: ffff88042d683e50 R8: 0000000000000000 R9: 0000000000000000
+ R10: ffff88042902b470 R11: ffff8804293406a8 R12: ffff880424098840
+ R13: ffff880424099580 R14: ffff88042a61ec00 R15: ffff88042933ae00
+ ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000
+ #8 [ffff88042d683de0] vmxnet3_rq_rx_complete at ffffffffc004dcfa [vmxnet3]
+ #9 [ffff88042d683e58] vmxnet3_poll_rx_only at ffffffffc004e60a [vmxnet3]
+ #10 [ffff88042d683e90] net_rx_action at ffffffff816f3544
+ #11 [ffff88042d683f00] __do_softirq at ffffffff81081e7d
+ #12 [ffff88042d683f68] irq_exit at ffffffff81082255
+ #13 [ffff88042d683f78] do_IRQ at ffffffff817f9ee6
+ --- <IRQ stack> ---
+ #14 [ffff880426c73f30] ret_from_intr at ffffffff817f7fc2
+ [exception RIP: unknown or invalid address]
+ RIP: fffffffffffffffb RSP: 00007fe17e59bf48 RFLAGS: 00000001
+ RAX: 00007fe18564ed58 RBX: 00007fe2064ce848 RCX: 00007fe185612d60
+ RDX: 00007fe20b47eb30 RSI: 00007fe185640d38 RDI: 00007fe18564ed50
+ RBP: ffffffff817f7fe5 R8: 00007fe185100068 R9: 0000000000037ce0
+ R10: 0000000000134ad8 R11: 00007fe17e4b7028 R12: 00007fe185100068
+ R13: 00007fe185632380 R14: 0000000000000000 R15: ffffffff81003a64
+ ORIG_RAX: 0000000000000001 CS: 7fe185640d38 SS: ffffffffffffff91
+ bt: WARNING: possibly bogus exception frame
+ RIP: 00000000004e92bb RSP: 00007fe20b47ea40 RFLAGS: 00000283
+ RAX: 0000000000000001 RBX: 00007fe18564ed58 RCX: fffffffffffffffb
+ RDX: 00007fe185640d38 RSI: 0000000000000001 RDI: 00007fe17e59bf48
+ RBP: 00007fe185100068 R8: 00007fe18564ed50 R9: 00007fe185640d38
+ R10: 00007fe20b47eb30 R11: 00007fe185612d60 R12: 0000000000037ce0
+ R13: 0000000000134ad8 R14: 00007fe17e4b7028 R15: 00007fe2064ce848
+ ORIG_RAX: ffffffffffffff91 CS: 0033 SS: 002b

** 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!"
  ...
  #0 [ffff88042d683aa0] machine_kexec at ffffffff8105987c
  #1 [ffff88042d683af8] crash_kexec at ffffffff81105d23
  #2 [ffff88042d683bc0] oops_end at ffffffff81030a79
  #3 [ffff88042d683be8] die at ffffffff81030f7b
  #4 [ffff88042d683c18] do_trap at ffffffff8102e04d
  #5 [ffff88042d683c68] do_error_trap at ffffffff8102e5a7
  #6 [ffff88042d683d20] do_invalid_op at ffffffff8102e840
  #7 [ffff88042d683d30] invalid_op at ffffffff817f900e
  [exception RIP: vmxnet3_rq_rx_complete+3016]
  RIP: ffffffffc004e448 RSP: ffff88042d683de8 RFLAGS: 00010246
  RAX: 0000000000000001 RBX: ffff880424099668 RCX: 0000000000000000
  RDX: 00000000000005f2 RSI: 00000000000005f2 RDI: ffff88042a61f400
  RBP: ffff88042d683e50 R8: 0000000000000000 R9: 0000000000000000
  R10: ffff88042902b470 R11: ffff8804293406a8 R12: ffff880424098840
  R13: ffff880424099580 R14: ffff88042a61ec00 R15: ffff88042933ae00
  ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000
  #8 [ffff88042d683de0] vmxnet3_rq_rx_complete at ffffffffc004dcfa [vmxnet3]
  #9 [ffff88042d683e58] vmxnet3_poll_rx_only at ffffffffc004e60a [vmxnet3]
  #10 [ffff88042d683e90] net_rx_action at ffffffff816f3544
  #11 [ffff88042d683f00] __do_softirq at ffffffff81081e7d
  #12 [ffff88042d683f68] irq_exit at ffffffff81082255
  #13 [ffff88042d683f78] do_IRQ at ffffffff817f9ee6
  --- <IRQ stack> ---
  #14 [ffff880426c73f30] ret_from_intr at ffffffff817f7fc2
  [exception RIP: unknown or invalid address]
  RIP: fffffffffffffffb RSP: 00007fe17e59bf48 RFLAGS: 00000001
  RAX: 00007fe18564ed58 RBX: 00007fe2064ce848 RCX: 00007fe185612d60
  RDX: 00007fe20b47eb30 RSI: 00007fe185640d38 RDI: 00007fe18564ed50
  RBP: ffffffff817f7fe5 R8: 00007fe185100068 R9: 0000000000037ce0
  R10: 0000000000134ad8 R11: 00007fe17e4b7028 R12: 00007fe185100068
  R13: 00007fe185632380 R14: 0000000000000000 R15: ffffffff81003a64
  ORIG_RAX: 0000000000000001 CS: 7fe185640d38 SS: ffffffffffffff91
  bt: WARNING: possibly bogus exception frame
  RIP: 00000000004e92bb RSP: 00007fe20b47ea40 RFLAGS: 00000283
  RAX: 0000000000000001 RBX: 00007fe18564ed58 RCX: fffffffffffffffb
  RDX: 00007fe185640d38 RSI: 0000000000000001 RDI: 00007fe17e59bf48
  RBP: 00007fe185100068 R8: 00007fe18564ed50 R9: 00007fe185640d38
  R10: 00007fe20b47eb30 R11: 00007fe185612d60 R12: 0000000000037ce0
  R13: 0000000000134ad8 R14: 00007fe17e4b7028 R15: 00007fe2064ce848
  ORIG_RAX: ffffffffffffff91 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.
+  * 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
+  * 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
+ 
+  * 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 [ffff88042d683aa0] machine_kexec at ffffffff8105987c
  #1 [ffff88042d683af8] crash_kexec at ffffffff81105d23
  #2 [ffff88042d683bc0] oops_end at ffffffff81030a79
  #3 [ffff88042d683be8] die at ffffffff81030f7b
  #4 [ffff88042d683c18] do_trap at ffffffff8102e04d
  #5 [ffff88042d683c68] do_error_trap at ffffffff8102e5a7
  #6 [ffff88042d683d20] do_invalid_op at ffffffff8102e840
  #7 [ffff88042d683d30] invalid_op at ffffffff817f900e
  [exception RIP: vmxnet3_rq_rx_complete+3016]
  RIP: ffffffffc004e448 RSP: ffff88042d683de8 RFLAGS: 00010246
  RAX: 0000000000000001 RBX: ffff880424099668 RCX: 0000000000000000
  RDX: 00000000000005f2 RSI: 00000000000005f2 RDI: ffff88042a61f400
  RBP: ffff88042d683e50 R8: 0000000000000000 R9: 0000000000000000
  R10: ffff88042902b470 R11: ffff8804293406a8 R12: ffff880424098840
  R13: ffff880424099580 R14: ffff88042a61ec00 R15: ffff88042933ae00
  ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000
  #8 [ffff88042d683de0] vmxnet3_rq_rx_complete at ffffffffc004dcfa [vmxnet3]
  #9 [ffff88042d683e58] vmxnet3_poll_rx_only at ffffffffc004e60a [vmxnet3]
  #10 [ffff88042d683e90] net_rx_action at ffffffff816f3544
  #11 [ffff88042d683f00] __do_softirq at ffffffff81081e7d
  #12 [ffff88042d683f68] irq_exit at ffffffff81082255
  #13 [ffff88042d683f78] do_IRQ at ffffffff817f9ee6
  --- <IRQ stack> ---
  #14 [ffff880426c73f30] ret_from_intr at ffffffff817f7fc2
  [exception RIP: unknown or invalid address]
  RIP: fffffffffffffffb RSP: 00007fe17e59bf48 RFLAGS: 00000001
  RAX: 00007fe18564ed58 RBX: 00007fe2064ce848 RCX: 00007fe185612d60
  RDX: 00007fe20b47eb30 RSI: 00007fe185640d38 RDI: 00007fe18564ed50
  RBP: ffffffff817f7fe5 R8: 00007fe185100068 R9: 0000000000037ce0
  R10: 0000000000134ad8 R11: 00007fe17e4b7028 R12: 00007fe185100068
  R13: 00007fe185632380 R14: 0000000000000000 R15: ffffffff81003a64
  ORIG_RAX: 0000000000000001 CS: 7fe185640d38 SS: ffffffffffffff91
  bt: WARNING: possibly bogus exception frame
  RIP: 00000000004e92bb RSP: 00007fe20b47ea40 RFLAGS: 00000283
  RAX: 0000000000000001 RBX: 00007fe18564ed58 RCX: fffffffffffffffb
  RDX: 00007fe185640d38 RSI: 0000000000000001 RDI: 00007fe17e59bf48
  RBP: 00007fe185100068 R8: 00007fe18564ed50 R9: 00007fe185640d38
  R10: 00007fe20b47eb30 R11: 00007fe185612d60 R12: 0000000000037ce0
  R13: 0000000000134ad8 R14: 00007fe17e4b7028 R15: 00007fe2064ce848
  ORIG_RAX: ffffffffffffff91 CS: 0033 SS: 002b

-- 
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:
  [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 [ffff88042d683aa0] machine_kexec at ffffffff8105987c
  #1 [ffff88042d683af8] crash_kexec at ffffffff81105d23
  #2 [ffff88042d683bc0] oops_end at ffffffff81030a79
  #3 [ffff88042d683be8] die at ffffffff81030f7b
  #4 [ffff88042d683c18] do_trap at ffffffff8102e04d
  #5 [ffff88042d683c68] do_error_trap at ffffffff8102e5a7
  #6 [ffff88042d683d20] do_invalid_op at ffffffff8102e840
  #7 [ffff88042d683d30] invalid_op at ffffffff817f900e
  [exception RIP: vmxnet3_rq_rx_complete+3016]
  RIP: ffffffffc004e448 RSP: ffff88042d683de8 RFLAGS: 00010246
  RAX: 0000000000000001 RBX: ffff880424099668 RCX: 0000000000000000
  RDX: 00000000000005f2 RSI: 00000000000005f2 RDI: ffff88042a61f400
  RBP: ffff88042d683e50 R8: 0000000000000000 R9: 0000000000000000
  R10: ffff88042902b470 R11: ffff8804293406a8 R12: ffff880424098840
  R13: ffff880424099580 R14: ffff88042a61ec00 R15: ffff88042933ae00
  ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000
  #8 [ffff88042d683de0] vmxnet3_rq_rx_complete at ffffffffc004dcfa [vmxnet3]
  #9 [ffff88042d683e58] vmxnet3_poll_rx_only at ffffffffc004e60a [vmxnet3]
  #10 [ffff88042d683e90] net_rx_action at ffffffff816f3544
  #11 [ffff88042d683f00] __do_softirq at ffffffff81081e7d
  #12 [ffff88042d683f68] irq_exit at ffffffff81082255
  #13 [ffff88042d683f78] do_IRQ at ffffffff817f9ee6
  --- <IRQ stack> ---
  #14 [ffff880426c73f30] ret_from_intr at ffffffff817f7fc2
  [exception RIP: unknown or invalid address]
  RIP: fffffffffffffffb RSP: 00007fe17e59bf48 RFLAGS: 00000001
  RAX: 00007fe18564ed58 RBX: 00007fe2064ce848 RCX: 00007fe185612d60
  RDX: 00007fe20b47eb30 RSI: 00007fe185640d38 RDI: 00007fe18564ed50
  RBP: ffffffff817f7fe5 R8: 00007fe185100068 R9: 0000000000037ce0
  R10: 0000000000134ad8 R11: 00007fe17e4b7028 R12: 00007fe185100068
  R13: 00007fe185632380 R14: 0000000000000000 R15: ffffffff81003a64
  ORIG_RAX: 0000000000000001 CS: 7fe185640d38 SS: ffffffffffffff91
  bt: WARNING: possibly bogus exception frame
  RIP: 00000000004e92bb RSP: 00007fe20b47ea40 RFLAGS: 00000283
  RAX: 0000000000000001 RBX: 00007fe18564ed58 RCX: fffffffffffffffb
  RDX: 00007fe185640d38 RSI: 0000000000000001 RDI: 00007fe17e59bf48
  RBP: 00007fe185100068 R8: 00007fe18564ed50 R9: 00007fe185640d38
  R10: 00007fe20b47eb30 R11: 00007fe185612d60 R12: 0000000000037ce0
  R13: 0000000000134ad8 R14: 00007fe17e4b7028 R15: 00007fe2064ce848
  ORIG_RAX: ffffffffffffff91 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 [ffff88042d683aa0] machine_kexec at ffffffff8105987c
  #1 [ffff88042d683af8] crash_kexec at ffffffff81105d23
  #2 [ffff88042d683bc0] oops_end at ffffffff81030a79
  #3 [ffff88042d683be8] die at ffffffff81030f7b
  #4 [ffff88042d683c18] do_trap at ffffffff8102e04d
  #5 [ffff88042d683c68] do_error_trap at ffffffff8102e5a7
  #6 [ffff88042d683d20] do_invalid_op at ffffffff8102e840
  #7 [ffff88042d683d30] invalid_op at ffffffff817f900e
  [exception RIP: vmxnet3_rq_rx_complete+3016]
  RIP: ffffffffc004e448 RSP: ffff88042d683de8 RFLAGS: 00010246
  RAX: 0000000000000001 RBX: ffff880424099668 RCX: 0000000000000000
  RDX: 00000000000005f2 RSI: 00000000000005f2 RDI: ffff88042a61f400
  RBP: ffff88042d683e50 R8: 0000000000000000 R9: 0000000000000000
  R10: ffff88042902b470 R11: ffff8804293406a8 R12: ffff880424098840
  R13: ffff880424099580 R14: ffff88042a61ec00 R15: ffff88042933ae00
  ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000
  #8 [ffff88042d683de0] vmxnet3_rq_rx_complete at ffffffffc004dcfa [vmxnet3]
  #9 [ffff88042d683e58] vmxnet3_poll_rx_only at ffffffffc004e60a [vmxnet3]
  #10 [ffff88042d683e90] net_rx_action at ffffffff816f3544
  #11 [ffff88042d683f00] __do_softirq at ffffffff81081e7d
  #12 [ffff88042d683f68] irq_exit at ffffffff81082255
  #13 [ffff88042d683f78] do_IRQ at ffffffff817f9ee6
  --- <IRQ stack> ---
  #14 [ffff880426c73f30] ret_from_intr at ffffffff817f7fc2
  [exception RIP: unknown or invalid address]
  RIP: fffffffffffffffb RSP: 00007fe17e59bf48 RFLAGS: 00000001
  RAX: 00007fe18564ed58 RBX: 00007fe2064ce848 RCX: 00007fe185612d60
  RDX: 00007fe20b47eb30 RSI: 00007fe185640d38 RDI: 00007fe18564ed50
  RBP: ffffffff817f7fe5 R8: 00007fe185100068 R9: 0000000000037ce0
  R10: 0000000000134ad8 R11: 00007fe17e4b7028 R12: 00007fe185100068
  R13: 00007fe185632380 R14: 0000000000000000 R15: ffffffff81003a64
  ORIG_RAX: 0000000000000001 CS: 7fe185640d38 SS: ffffffffffffff91
  bt: WARNING: possibly bogus exception frame
  RIP: 00000000004e92bb RSP: 00007fe20b47ea40 RFLAGS: 00000283
  RAX: 0000000000000001 RBX: 00007fe18564ed58 RCX: fffffffffffffffb
  RDX: 00007fe185640d38 RSI: 0000000000000001 RDI: 00007fe17e59bf48
  RBP: 00007fe185100068 R8: 00007fe18564ed50 R9: 00007fe185640d38
  R10: 00007fe20b47eb30 R11: 00007fe185612d60 R12: 0000000000037ce0
  R13: 0000000000134ad8 R14: 00007fe17e4b7028 R15: 00007fe2064ce848
  ORIG_RAX: ffffffffffffff91 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

Reply via email to