Bug 720909 - system crash with kernel BUG at arch/x86/kvm/mmu.c:693
Summary: system crash with kernel BUG at arch/x86/kvm/mmu.c:693
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-13 08:22 UTC by Olivier Fourdan
Modified: 2013-03-04 02:50 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-27 23:51:56 UTC
Type: ---

Attachments (Terms of Use)
crash log (7.40 KB, text/plain)
2011-07-13 08:22 UTC, Olivier Fourdan 		no flags Details
Another (different) crash log (5.95 KB, text/plain)
2011-07-13 09:14 UTC, Olivier Fourdan 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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?
Note You need to log in before you can comment on or make changes to this bug.