* Mathieu Desnoyers comp...@krystal.dyndns.org wrote:
* Mathieu Desnoyers (mathieu.desnoy...@polymtl.ca) wrote:
* Ingo Molnar (mi...@elte.hu) wrote:
* Mathieu Desnoyers mathieu.desnoy...@polymtl.ca wrote:
Here is a new backtrace, taken with a huge amount of debugging active,
* Mathieu Desnoyers mathieu.desnoy...@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,
Mathieu Desnoyers wrote:
* Ingo Molnar (mi...@elte.hu) wrote:
* Mathieu Desnoyers mathieu.desnoy...@polymtl.ca wrote:
Hi,
I've started experiencing freezes on my uniprocessor laptop with a
2.6.28.2/2.6.28.3 kernel with the LTTng patchset applied
* Ingo Molnar (mi...@elte.hu) wrote:
* Mathieu Desnoyers mathieu.desnoy...@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
On Wed, Feb 11, 2009 at 08:50:38PM +0100, Ingo Molnar wrote:
* Mathieu Desnoyers mathieu.desnoy...@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
* Mathieu Desnoyers (mathieu.desnoy...@polymtl.ca) wrote:
* Ingo Molnar (mi...@elte.hu) wrote:
* Mathieu Desnoyers mathieu.desnoy...@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
