Bug 1402877 - [abrt] BUG: spinlock bad magic on CPU#3, qemu-system-i38/1297: TAINTED
Summary: [abrt] BUG: spinlock bad magic on CPU#3, qemu-system-i38/1297: TAINTED
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:25a685788ab93cd1531dadc1432...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-08 14:15 UTC by Bill Gianopoulos
Modified: 2019-01-09 12:54 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-06 18:19:48 UTC
Type: ---

Attachments (Terms of Use)
File: dmesg (77.55 KB, text/plain)
2016-12-08 14:15 UTC, Bill Gianopoulos 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Bill Gianopoulos 2016-12-08 14:15:06 UTC 
Additional info:
reporter:       libreport-2.8.0
BUG: spinlock bad magic on CPU#3, qemu-system-i38/1297
 lock: svm_vm_data_hash_lock+0x0/0xffffffffffff9de0 [kvm_amd], .magic: 00000000, .owner: qemu-system-i38/1297, .owner_cpu: 3
CPU: 3 PID: 1297 Comm: qemu-system-i38 Not tainted 4.9.0-0.rc8.git1.1.fc26.x86_64 #1
Hardware name: SAMSUNG ELECTRONICS CO., LTD. 305E4A/305E5A/305E7A/305E4A/305E4A, BIOS 01TL.MI30.20121023.SKK 10/23/2012
 ffff9deac21b3b00 ffffffffa5477443 ffff8af502ea0000 ffffffffc0c7c220
 ffff9deac21b3b20 ffffffffa5117068 ffffffffc0c7c220 ffffffffc0c7c220
 ffff9deac21b3b38 ffffffffa5117303 0000000000000292 ffff9deac21b3b58
Call Trace:
 [<ffffffffa5477443>] dump_stack+0x86/0xc3
 [<ffffffffa5117068>] spin_dump+0x78/0xd0
 [<ffffffffa5117303>] do_raw_spin_unlock+0x63/0xc0
 [<ffffffffa5915e7c>] _raw_spin_unlock_irqrestore+0x2c/0x60
 [<ffffffffc0c6cf88>] avic_vm_destroy+0xb8/0xc0 [kvm_amd]
 [<ffffffffc0976965>] kvm_arch_destroy_vm+0x45/0x1d0 [kvm]
 [<ffffffffc0956e7f>] kvm_put_kvm+0x12f/0x200 [kvm]
 [<ffffffffc0956fc1>] kvm_vm_release+0x21/0x30 [kvm]
 [<ffffffffa52afb48>] __fput+0xf8/0x210
 [<ffffffffa52afc9e>] ____fput+0xe/0x10
 [<ffffffffa50d6505>] task_work_run+0x85/0xc0
 [<ffffffffa50b56a8>] do_exit+0x338/0xcf0
 [<ffffffffa50b60f0>] do_group_exit+0x50/0xd0
 [<ffffffffa50c4159>] get_signal+0x2d9/0x950
 [<ffffffffa502d3a7>] do_signal+0x37/0x690
 [<ffffffffa52d1974>] ? __fget+0x114/0x200
 [<ffffffffa52d1865>] ? __fget+0x5/0x200
 [<ffffffffa52d1ac5>] ? __fget_light+0x25/0x60
 [<ffffffffa50032f0>] exit_to_usermode_loop+0x80/0xc0
 [<ffffffffa5003e09>] syscall_return_slowpath+0xc9/0x140
 [<ffffffffa59167e2>] entry_SYSCALL_64_fastpath+0xc0/0xc2
Comment 1 Bill Gianopoulos 2016-12-08 14:15:17 UTC 
Created attachment 1229496 [details]
File: dmesg
Comment 2 Laura Abbott 2018-04-06 18:19:48 UTC 
Doing some pruning, this bug looks to be years old. Please test on a newer kernel and reopen if the problem still exists.
Note You need to log in before you can comment on or make changes to this bug.