BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Eric Desrochers |
Bug Description
[Impact]
It has been brought to my attention that VMware Guest[1] randomly crashes after moving the VMs from a VMware "5.5" env to VMware 6.5 env.
Notes:
* The crashes wasn't present in VMware 5.5 (with the same VMs). Only started to happens with Vmware 6.5
* The Trusty HWE kernel (Ubuntu-4.4.0-X) doesn't exhibit the situation on VMware 6.5.
Here's the stack trace took from the .vmss converted to be readable by Linux debugger:
[17007961.187411] BUG: scheduling while atomic: swapper/
[17007961.189794] Modules linked in: arc4 md4 nls_utf8 cifs nfsv3 nfs_acl nfsv4 nfs lockd sunrpc fscache veth ipt_MASQUERADE nf_conntrack_
[17007961.189856] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.13.0-135-generic #184-Ubuntu
[17007961.189862] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 10/22/2013
[17007961.189867] 0000000000000000 ffff88042f263b90 ffffffff8172d959 ffff88042f263d30
[17007961.189874] ffff88042f273180 ffff88042f263ba0 ffffffff81726d8c ffff88042f263c00
[17007961.189879] ffffffff81731c8f ffff880428c29800 0000000000013180 ffff880428c25fd8
[17007961.189885] Call Trace:
[17007961.189889] <IRQ> [<ffffffff8172d
[17007961.189913] [<ffffffff81726
[17007961.189922] [<ffffffff81731
[17007961.189929] [<ffffffff81731
[17007961.189935] [<ffffffff81731
[17007961.189947] [<ffffffff810a3
[17007961.189955] [<ffffffff810a9
[17007961.189962] [<ffffffff810a0
[17007961.189971] [<ffffffff81732
[17007961.189977] [<ffffffff8109e
[17007961.189987] [<ffffffff810cc
[17007961.189993] [<ffffffff810ca
[17007961.189999] [<ffffffff810ca
[17007961.190006] [<ffffffff810cc
[17007961.190047] [<ffffffffa01a8
[17007961.190063] [<ffffffffa0189
[17007961.190078] [<ffffffffa017f
[17007961.190087] [<ffffffff8161a
[17007961.190092] [<ffffffff8161a
[17007961.190102] [<ffffffffa018a
[17007961.190114] [<ffffffffa01a7
[17007961.190126] [<ffffffffa01a8
[17007961.190138] [<ffffffff8106f
[17007961.190145] [<ffffffff8106f
[17007961.190153] [<ffffffff81070
[17007961.190161] [<ffffffff81740
[17007961.190170] [<ffffffff81735
[17007961.190173] <EOI> [<ffffffff81051
[17007961.190190] [<ffffffff8101d
[17007961.190197] [<ffffffff8101e
[17007961.190205] [<ffffffff810c2
[17007961.190214] [<ffffffff81042
[17007961.190221] bad: scheduling from the idle thread!
[Test Case]
- Run a Trusty kernel (3.13 kernel series) VMware guests hosted on VMware 6.0 and later (with VMCI (Virtual Machine Communication Interface) turn on)
- Wait for the crash to happen. It is happening randomly with no clear reproducible steps on how to trigger the crash for now.
[Regression Potential]
* A test kernel has been tested on VMware 5.5 (where the situation doesn't happen but we are testing anyway in order to look for potential regression in earlier VMware environment version) and Vmware 6.5 (where the situation happens). I basically wanted to make sure the test package will work good on both VMware env before thinking of proposing the patch series to the Ubuntu kernel ML.
And it does so far, see Comment #5 from an affected user.
* Limited risk due to changes being made only to a
very specific driver.
[Other infos]
I have identified a patch series[2] which seems to fix the exact same situation.
A full discussion can be found on patchworks[3], suggesting a certain patch series[2] authored by Vmware.
[1] - VM details :
Release: Trusty
Kernel: Ubuntu-3.13.0-135
[2] Upstream patch series
8ab18d7 VSOCK: Detach QP check should filter out non matching QPs.
8566b86 VSOCK: Fix lockdep issue.
4ef7ea9 VSOCK: sock_put wasn't safe to call in interrupt context
----------------
commit 4ef7ea9
Author: Jorgen Hansen <email address hidden>
Date: Wed Oct 21 04:53:56 2015 -0700
VSOCK: sock_put wasn't safe to call in interrupt context
...
Multiple customers have been hitting this issue when using
VMware tools on vSphere 2015.
...
----------------
VSphere 2015 == VMware 6.0 (release in 2015) and late.
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
Changed in linux (Ubuntu Trusty): | |
importance: | Undecided → Medium |
assignee: | nobody → Eric Desrochers (slashd) |
status: | New → In Progress |
summary: |
- BUG: scheduling while atomic (v3.13 + VMware 6.0 and late) + BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and + late) |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in linux (Ubuntu Trusty): | |
status: | In Progress → Fix Committed |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1780470
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.