Re: inconsistent lock state. (kvm)
- From: Avi Kivity <avi@xxxxxxxxxx>
- Date: Sat, 27 Sep 2008 12:56:06 +0300
Dave Jones wrote:
I just triggered this with just modprobe kvm_intel ; rmmod kvm kvm_intel
Dave
=================================
[ INFO: inconsistent lock state ]
2.6.26.3-29.fc9.x86_64.debug #1
---------------------------------
inconsistent {hardirq-on-W} -> {in-hardirq-W} usage.
Xorg/2680 [HC1[1]:SC0[0]:HE0:SE1] takes:
(kvm_lock){+-..}, at: [<ffffffffa0463ad6>] decache_vcpus_on_cpu+0x20/0xbd [kvm]
This is sort of known, which is why decache_vcpus_on_cpu no longer exists.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- inconsistent lock state. (kvm)
- From: Dave Jones
- inconsistent lock state. (kvm)
- Prev by Date: Re: [Bug #11516] severe performance degradation on x86_64 going from 2.6.26-rc9 -> 2.6.27-rc5
- Next by Date: Re: NFS regression? Odd delays and lockups accessing an NFS export.
- Previous by thread: inconsistent lock state. (kvm)
- Next by thread: [PATCH] x86: mtrr_cleanup optimization
- Index(es):
Relevant Pages
|
Loading