Bug 718741

Summary: [KVM] BUG: sleeping function called from invalid context at arch/x86/mm/fault.c:1087
Product: [Fedora] Fedora Reporter: Marcin <exeqtor1>
Component: kernelAssignee: Justin M. Forbes <jforbes>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: aquini, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:d34cb33c46896c62485d4004ec151685244c795c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-17 17:12:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Marcin 2011-07-04 13:21:18 UTC
abrt version: 2.0.3
architecture:   i686
cmdline:        ro root=UUID=35bc9810-7ca8-4785-a05d-1495efd41350 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=pl2 rhgb quiet
comment:        Start virt-manager, connect to qemu server and start random virtual machine
component:      kernel
kernel:         2.6.38.8-32.fc15.i686
os_release:     Fedora release 15 (Lovelock)
package:        kernel
reason:         BUG: sleeping function called from invalid context at arch/x86/mm/fault.c:1087
time:           Mon Jul  4 15:13:09 2011

backtrace:
:BUG: sleeping function called from invalid context at arch/x86/mm/fault.c:1087
:in_atomic(): 0, irqs_disabled(): 1, pid: 12353, name: qemu-kvm
:Pid: 12353, comm: qemu-kvm Not tainted 2.6.38.8-32.fc15.i686 #1
:Call Trace:
: [<c07ced36>] ? printk+0x2d/0x2f
: [<c042e5fa>] __might_sleep+0xdd/0xe4
: [<c07d933c>] do_page_fault+0x179/0x30c
: [<c0454999>] ? hrtimer_interrupt+0x110/0x1aa
: [<c0404eb7>] ? do_softirq+0x8c/0x92
: [<c07d91c3>] ? do_page_fault+0x0/0x30c
: [<c07d6fb7>] error_code+0x67/0x6c
: [<c07d6909>] ? restore_nocheck+0xb/0x10
: [<c0462203>] ? do_raw_spin_lock+0x1/0x1e
: [<c07d6474>] ? _raw_spin_lock+0xd/0xf
: [<fab1638e>] coalesced_mmio_write+0xcb/0x100 [kvm]
: [<fab15a79>] kvm_io_bus_write+0x4f/0x6c [kvm]
: [<fab162c3>] ? coalesced_mmio_write+0x0/0x100 [kvm]
: [<fab22d91>] emulator_write_emulated_onepage+0xe0/0x146 [kvm]
: [<fab3532d>] ? apic_mmio_write+0x0/0x67 [kvm]
: [<fab22e60>] emulator_write_emulated+0x69/0x71 [kvm]
: [<fab2e86e>] ? linear+0x26/0x2d [kvm]
: [<fab2ea10>] writeback+0x8e/0x9a [kvm]
: [<fab22df7>] ? emulator_write_emulated+0x0/0x71 [kvm]
: [<fab32975>] x86_emulate_insn+0x1d49/0x2fd4 [kvm]
: [<fab2f13e>] ? decode_register_operand+0x81/0x8c [kvm]
: [<fab2264f>] ? kvm_get_cs_db_l_bits+0x1e/0x31 [kvm]
: [<fab22af4>] x86_emulate_instruction+0x176/0x2d6 [kvm]
: [<fab1fdad>] ? emulator_pio_out_emulated+0x7b/0xd6 [kvm]
: [<fab2a662>] kvm_mmu_page_fault+0x4d/0x70 [kvm]
: [<fa564e18>] pf_interception+0xb6/0xf8 [kvm_amd]
: [<fa569600>] handle_exit+0x2b2/0x363 [kvm_amd]
: [<c0458a7b>] ? monotonic_to_bootbased+0x33/0x44
: [<fab1fedc>] ? kvm_get_cr8+0x19/0x23 [kvm]
: [<fa565865>] ? svm_get_msr+0xda/0x1d9 [kvm_amd]
: [<fab2538b>] kvm_arch_vcpu_ioctl_run+0xa9f/0xd20 [kvm]
: [<c07d5991>] ? mutex_lock+0x22/0x3c
: [<fab20bf0>] ? kvm_arch_vcpu_load+0x109/0x11e [kvm]
: [<fab1485e>] kvm_vcpu_ioctl+0x105/0x4b1 [kvm]
: [<c045fb74>] ? futex_wake+0xc2/0xcc
: [<c0460a5d>] ? do_futex+0x98/0x6c1
: [<fab14759>] ? kvm_vcpu_ioctl+0x0/0x4b1 [kvm]
: [<c04f0a5d>] do_vfs_ioctl+0x451/0x482
: [<c07d6d51>] ? apic_timer_interrupt+0x31/0x38
: [<c0458b94>] ? current_kernel_time+0x8/0x2c
: [<c047bbb5>] ? audit_syscall_entry+0x128/0x14a
: [<c04f0ad6>] sys_ioctl+0x48/0x6a
: [<c07d68cc>] syscall_call+0x7/0xb

Comment 1 Dave Jones 2011-08-15 21:54:24 UTC
Can you confirm whether or not this still occurs in the 2.6.40 update ?

Comment 2 Marcin 2011-08-16 21:15:54 UTC
Everything is ok in this version.
Thanks for Your concern.