From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [BUG] Linux 2.6.28.4 freezing on a 32-bits x86 Thinkpad T43p Date: Wed, 11 Feb 2009 20:50:38 +0100 Message-ID: <20090211195038.GC25968@elte.hu> References: <20090204211106.GA30824@Krystal> <20090204211759.GK22608@elte.hu> <20090211193125.GA30975@Krystal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , Andrew Morton , Thomas Gleixner , Greg KH , ltt-dev@lists.casi.polymtl.ca, linux-kernel@vger.kernel.org, kvm@vger.kernel.org To: Mathieu Desnoyers Return-path: Received: from mx3.mail.elte.hu ([157.181.1.138]:39893 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755329AbZBKTvV (ORCPT ); Wed, 11 Feb 2009 14:51:21 -0500 Content-Disposition: inline In-Reply-To: <20090211193125.GA30975@Krystal> Sender: kvm-owner@vger.kernel.org List-ID: * Mathieu Desnoyers 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