[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49BC4196.3070204@goop.org>
Date: Sat, 14 Mar 2009 16:45:26 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: akataria@...are.com
CC: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
the arch/x86 maintainers <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: VMI broken on tip/master...
Alok Kataria wrote:
> Hi Peter,
>
> I was seeing a early fault when running tip/master with VMI enabled on
> VMware platform.
> This early fault was in the vmi_patch code where we are applying
> paravirt_alternatives. After some trials i noticed that this is
> reproducible only with CONFIG_TRACING. With that disabled my VM boots
> again.
>
> I started a git bisect after that, and git pointed to this as the bad
> commit
>
> commit 6cc3c6e12bb039047974ad2e7e2d46d15a1b762f
> trace_clock: fix preemption bug
>
> I then reverted that commit from tip/master and the system did boot.
> But I fail to understand how this simple patch would be causing things
> to fail in VMI. Any ideas ?
>
Nope. My first guess is that this is a misbisection, but the fact that
reverting helps tends to undermine that diagnosis.
What crash are you seeing? What kind of fault? At what instruction?
Doing what? It's a bit hard to tell what you're actually seeing.
Does reverting the text_poke() changes make a difference?
J
--
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