From: Ingo Molnar <mingo@elte.hu>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Avi Kivity <avi@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>, Greg KH <greg@kroah.com>,
ltt-dev@lists.casi.polymtl.ca, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
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 [thread overview]
Message-ID: <20090211195038.GC25968@elte.hu> (raw)
In-Reply-To: <20090211193125.GA30975@Krystal>
* Mathieu Desnoyers <mathieu.desnoyers@polymtl.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
next prev parent reply other threads:[~2009-02-11 19:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 21:11 [BUG] Linux 2.6.28.3 freezing on a 32-bits x86 Thinkpad T43p Mathieu Desnoyers
2009-02-04 21:17 ` Ingo Molnar
2009-02-11 19:31 ` [BUG] Linux 2.6.28.4 " Mathieu Desnoyers
2009-02-11 19:50 ` Ingo Molnar [this message]
2009-02-11 20:13 ` Mathieu Desnoyers
2009-02-12 4:50 ` [ltt-dev] " Mathieu Desnoyers
2009-02-12 14:43 ` Ingo Molnar
2009-02-12 15:07 ` Mathieu Desnoyers
2009-02-11 20:14 ` Marcelo Tosatti
2009-02-11 20:11 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090211195038.GC25968@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=greg@kroah.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox