Bug 720909

Summary: system crash with kernel BUG at arch/x86/kvm/mmu.c:693
Product: [Fedora] Fedora Reporter: Olivier Fourdan <ofourdan>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: aquini, berrange, clalance, ehabkost, extras-orphan, gansalmon, itamar, jonathan, kem, kernel-maint, madhu.chinakonda, quintela, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-27 23:51:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
crash log
none
Another (different) crash log none

Description Olivier Fourdan 2011-07-13 08:22:43 UTC
Created attachment 512585 [details]
crash log

Description of problem:

Kernel crashes randomly with attached backtrace.

Version-Release number of selected component (if applicable):

kernel-2.6.38.8-35.fc15.x86_64

How reproducible:

Randomly

Steps to Reproduce:
1. Run more than one VM
  
Actual results:

Host system crash with attached backtrace

Expected results:

No crash

Additional info:

This seems to happen when I run more than one VM at the time.

ksm is not running (but ksmd is present in ps)

  $ cat /sys/kernel/mm/ksm/run 
  0

  $ sudo service ksm status
  ksm is not running

  $ sudo service ksmtuned status
  ksmtuned.service - LSB: tune the speed of ksm
  	  Loaded: loaded (/etc/rc.d/init.d/ksmtuned)
  	  Active: inactive (dead)
  	  CGroup: name=systemd:/system/ksmtuned.service

Comment 1 Olivier Fourdan 2011-07-13 09:14:05 UTC
Created attachment 512610 [details]
Another (different) crash log

Just had another crash but the backtrace is different.

This time ksm was enabled (enabled to check if that would have any influence on the issue).

Same reproducing steps:

1. Start two VMs
2. Copy some large amount of data from one to the other

Comment 2 Josh Boyer 2011-09-26 20:06:16 UTC
Does this still happen with the latest 2.6.40 kernel update?