[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090211195038.GC25968@elte.hu>
Date: Wed, 11 Feb 2009 20:50:38 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc: Avi Kivity <avi@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>, Greg KH <greg@...ah.com>,
ltt-dev@...ts.casi.polymtl.ca, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org
Subject: Re: [BUG] Linux 2.6.28.4 freezing on a 32-bits x86 Thinkpad T43p
* Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote:
> Here is a new backtrace, taken with a huge amount of debugging active, which still
> points to an interrupt handler nested over kvm_mmu_pte_write as the culprit. It's
> weird that the kvm code gets called on my modest Pentium M laptop, which I think
> has no VT-x support at all. I am not running any KVM VMs on this machine. The
> problem still happens on 2.6.28.4, and Slub redzones did not identify any memory
> corruption. This could be due to kvm_mmu_pte_write which either should not be
> called at all, or due to improper interrupt disabling in this function.
Does latest tip:master fix it? In particular this one:
9cf161a: x86/cpa: make sure cpa is safe to call in lazy mmu mode
fixes a crasher related to KVM and mmu notifiers ...
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists