On 07/30/2012 07:39 PM, Avi Kivity wrote:
On 07/30/2012 05:07 PM, Chris Clayton wrote:
With kernel 3.5.0 with b2da15ac26a0c00 reverted, I have just had 15
clean invocations of vanilla qemu-kvm-1.1.1. So that commit would seem
to be the problem.
Just to be sure, I've run some more tests
On 07/31/2012 02:36 AM, Marcelo Tosatti wrote:
On Mon, Jul 30, 2012 at 07:39:31PM +0300, Avi Kivity wrote:
On 07/30/2012 05:07 PM, Chris Clayton wrote:
With kernel 3.5.0 with b2da15ac26a0c00 reverted, I have just had 15
clean invocations of vanilla qemu-kvm-1.1.1. So that commit would seem
On 07/31/2012 07:29 PM, Marcelo Tosatti wrote:
So the same problem should happen with %fs and %gs, no?
AFAICS:
depends on CONFIG_X86_32_LAZY_GS for GS, unconditional for FS.
This fs/gs were already in there, I wonder how it wasn't broken before.
Something's fishy here.
x86_64 is
On Tue, Jul 31, 2012 at 12:11:13PM +0300, Avi Kivity wrote:
On 07/31/2012 02:36 AM, Marcelo Tosatti wrote:
On Mon, Jul 30, 2012 at 07:39:31PM +0300, Avi Kivity wrote:
On 07/30/2012 05:07 PM, Chris Clayton wrote:
With kernel 3.5.0 with b2da15ac26a0c00 reverted, I have just had 15
On 07/29/12 20:10, Chris Clayton wrote:
Possible culprit: b2da15ac26a0c00.
That commit isn't in qermu-kvm-1.1.1.
It is in kernel.
Sorry, so it is.
With kernel 3.5.0 with b2da15ac26a0c00 reverted, I have just had 15
clean invocations of vanilla qemu-kvm-1.1.1. So that commit would seem
On 07/30/2012 05:00 PM, Chris Clayton wrote:
On 07/29/12 20:10, Chris Clayton wrote:
Possible culprit: b2da15ac26a0c00.
That commit isn't in qermu-kvm-1.1.1.
It is in kernel.
Sorry, so it is.
With kernel 3.5.0 with b2da15ac26a0c00 reverted, I have just had 15
clean invocations of
On 07/30/12 15:03, Avi Kivity wrote:
On 07/30/2012 05:00 PM, Chris Clayton wrote:
On 07/29/12 20:10, Chris Clayton wrote:
Possible culprit: b2da15ac26a0c00.
That commit isn't in qermu-kvm-1.1.1.
It is in kernel.
Sorry, so it is.
With kernel 3.5.0 with b2da15ac26a0c00 reverted, I have
On 07/30/2012 05:07 PM, Chris Clayton wrote:
With kernel 3.5.0 with b2da15ac26a0c00 reverted, I have just had 15
clean invocations of vanilla qemu-kvm-1.1.1. So that commit would seem
to be the problem.
Just to be sure, I've run some more tests today. No crashes occurred in
20 runs of
On Mon, Jul 30, 2012 at 07:39:31PM +0300, Avi Kivity wrote:
On 07/30/2012 05:07 PM, Chris Clayton wrote:
With kernel 3.5.0 with b2da15ac26a0c00 reverted, I have just had 15
clean invocations of vanilla qemu-kvm-1.1.1. So that commit would seem
to be the problem.
Just to be sure, I've
On 07/27/2012 10:04 PM, Chris Clayton wrote:
On 07/27/12 19:08, Eric Northup wrote:
Could you include the output of info registers at the point where it
crashed?
Here you go:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6a78b40 (LWP 13249)]
On 07/29/12 13:42, Avi Kivity wrote:
On 07/27/2012 10:04 PM, Chris Clayton wrote:
On 07/27/12 19:08, Eric Northup wrote:
Could you include the output of info registers at the point where it
crashed?
Here you go:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread
On 07/29/2012 05:03 PM, Chris Clayton wrote:
On 07/29/12 13:42, Avi Kivity wrote:
On 07/27/2012 10:04 PM, Chris Clayton wrote:
On 07/27/12 19:08, Eric Northup wrote:
Could you include the output of info registers at the point where it
crashed?
Here you go:
Program received signal
On 07/29/2012 05:18 PM, Avi Kivity wrote:
I think you are saying that the problem isn't in kvm, so where would you
recommend I continue investigations. I'm not seeing a crash with any
other applications.
What might have happened is that the movdqu instruction faulted (as it's
an fpu
On 07/29/12 15:48, Avi Kivity wrote:
On 07/29/2012 05:18 PM, Avi Kivity wrote:
I think you are saying that the problem isn't in kvm, so where would you
recommend I continue investigations. I'm not seeing a crash with any
other applications.
What might have happened is that the movdqu
On 07/29/2012 05:18 PM, Avi Kivity wrote:
On 07/29/2012 05:03 PM, Chris Clayton wrote:
On 07/29/12 13:42, Avi Kivity wrote:
On 07/27/2012 10:04 PM, Chris Clayton wrote:
On 07/27/12 19:08, Eric Northup wrote:
Could you include the output of info registers at the point where it
crashed?
On 07/29/2012 06:47 PM, Avi Kivity wrote:
What might have happened is that the movdqu instruction faulted (as it's
an fpu instruction), and on the way back from the fault, ds and es
didn't get restored correctly.
You can test this by writing a trivial version of g_str_equal()
somewhere in
On 07/29/12 17:34, Avi Kivity wrote:
On 07/29/2012 06:47 PM, Avi Kivity wrote:
What might have happened is that the movdqu instruction faulted (as it's
an fpu instruction), and on the way back from the fault, ds and es
didn't get restored correctly.
You can test this by writing a trivial
On Sun, Jul 29, 2012 at 06:50:09PM +0100, Chris Clayton wrote:
On 07/29/12 17:34, Avi Kivity wrote:
On 07/29/2012 06:47 PM, Avi Kivity wrote:
What might have happened is that the movdqu instruction faulted (as it's
an fpu instruction), and on the way back from the fault, ds and es
didn't get
On 07/29/12 18:54, Gleb Natapov wrote:
On Sun, Jul 29, 2012 at 06:50:09PM +0100, Chris Clayton wrote:
On 07/29/12 17:34, Avi Kivity wrote:
On 07/29/2012 06:47 PM, Avi Kivity wrote:
What might have happened is that the movdqu instruction faulted (as it's
an fpu instruction), and on the way
On 07/27/12 00:22, Chris Clayton wrote:
On 07/26/12 13:07, Avi Kivity wrote:
On 07/26/2012 02:58 PM, Chris Clayton wrote:
It looks like general memory corruption. Is this repeatable? What's
the guest uptime when it happens (i.e. is it immediate?)
I've just done 10 runs of WinXP SP3 and 5
On 07/27/12 19:08, Eric Northup wrote:
Could you include the output of info registers at the point where it
crashed?
Here you go:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6a78b40 (LWP 13249)]
__strcmp_sse4_2 () at
On 07/19/12 19:23, Chris Clayton wrote:
On 07/19/12 13:17, Avi Kivity wrote:
On 07/19/2012 03:14 PM, Chris Clayton wrote:
Change of diagnostics, unfortunately. qemu-kvm-1.0.1 can, in fact,
crash
on 3.5.0-rc6 (and rc7). I didn't get it earlier because it takes many
times more invocations
On 07/26/2012 12:52 PM, Chris Clayton wrote:
On 07/19/12 19:23, Chris Clayton wrote:
On 07/19/12 13:17, Avi Kivity wrote:
On 07/19/2012 03:14 PM, Chris Clayton wrote:
Change of diagnostics, unfortunately. qemu-kvm-1.0.1 can, in fact,
crash
on 3.5.0-rc6 (and rc7). I didn't get it earlier
On 07/26/2012 01:29 PM, Jan Kiszka wrote:
It looks like general memory corruption. Is this repeatable? What's
the guest uptime when it happens (i.e. is it immediate?)
Jan, why are we calling cpu_set_apic_tpr() with kvm_irqchip_in_kernel?
To sync the userspace state with what the kernel
On 2012-07-26 12:45, Avi Kivity wrote:
On 07/26/2012 01:29 PM, Jan Kiszka wrote:
It looks like general memory corruption. Is this repeatable? What's
the guest uptime when it happens (i.e. is it immediate?)
Jan, why are we calling cpu_set_apic_tpr() with kvm_irqchip_in_kernel?
To sync
On 2012-07-26 12:49, Jan Kiszka wrote:
On 2012-07-26 12:45, Avi Kivity wrote:
On 07/26/2012 01:29 PM, Jan Kiszka wrote:
It looks like general memory corruption. Is this repeatable? What's
the guest uptime when it happens (i.e. is it immediate?)
Jan, why are we calling cpu_set_apic_tpr()
Hi Chris,
Could you please try this patch?
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=ccebf448daf7964ee2aff7947c0bbe4c7962d059
On 07/26/2012 05:52 PM, Chris Clayton wrote:
On 07/19/12 19:23, Chris Clayton wrote:
On 07/19/12 13:17, Avi Kivity wrote:
On 07/19/2012
On 07/26/12 11:01, Avi Kivity wrote:
On 07/26/2012 12:52 PM, Chris Clayton wrote:
On 07/19/12 19:23, Chris Clayton wrote:
On 07/19/12 13:17, Avi Kivity wrote:
On 07/19/2012 03:14 PM, Chris Clayton wrote:
Change of diagnostics, unfortunately. qemu-kvm-1.0.1 can, in fact,
crash
on 3.5.0-rc6
On 07/26/2012 02:58 PM, Chris Clayton wrote:
It looks like general memory corruption. Is this repeatable? What's
the guest uptime when it happens (i.e. is it immediate?)
I've just done 10 runs of WinXP SP3 and 5 of them crashed. Three crashed
early as XP was starting up - well before the
On 2012-07-26 13:58, Chris Clayton wrote:
On 07/26/12 11:01, Avi Kivity wrote:
On 07/26/2012 12:52 PM, Chris Clayton wrote:
On 07/19/12 19:23, Chris Clayton wrote:
On 07/19/12 13:17, Avi Kivity wrote:
On 07/19/2012 03:14 PM, Chris Clayton wrote:
Change of diagnostics, unfortunately.
On 07/26/12 12:10, Xiao Guangrong wrote:
Hi Chris,
Could you please try this patch?
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=ccebf448daf7964ee2aff7947c0bbe4c7962d059
Sorry, that patch does not fix the crashes.
On 07/26/2012 05:52 PM, Chris Clayton wrote:
On
On 07/26/12 13:07, Avi Kivity wrote:
On 07/26/2012 02:58 PM, Chris Clayton wrote:
It looks like general memory corruption. Is this repeatable? What's
the guest uptime when it happens (i.e. is it immediate?)
I've just done 10 runs of WinXP SP3 and 5 of them crashed. Three crashed
early as
On 07/15/12 20:52, Chris Clayton wrote:
On 07/11/12 08:22, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 08:18:17AM +0100, Chris Clayton wrote:
On 07/11/12 08:12, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 08:09:42AM +0100, Chris Clayton wrote:
Ping.
Have I committed a bug-reporting sin in
On 07/19/2012 03:14 PM, Chris Clayton wrote:
Change of diagnostics, unfortunately. qemu-kvm-1.0.1 can, in fact, crash
on 3.5.0-rc6 (and rc7). I didn't get it earlier because it takes many
times more invocations before the crash occurs with 1.0.1 and I haven't
used qemu-kvm much in the past
On 07/19/12 13:17, Avi Kivity wrote:
On 07/19/2012 03:14 PM, Chris Clayton wrote:
Change of diagnostics, unfortunately. qemu-kvm-1.0.1 can, in fact, crash
on 3.5.0-rc6 (and rc7). I didn't get it earlier because it takes many
times more invocations before the crash occurs with 1.0.1 and I
On 07/11/12 08:22, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 08:18:17AM +0100, Chris Clayton wrote:
On 07/11/12 08:12, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 08:09:42AM +0100, Chris Clayton wrote:
Ping.
Have I committed a bug-reporting sin in the mail below or is
everyone simply too
Ping.
Have I committed a bug-reporting sin in the mail below or is everyone
simply too busy to look at this kvm-related crash?
On 07/09/12 11:57, Chris Clayton wrote:
Hi,
When I run WinXP SP3 through qemu-kvm-1.1.0 on linux kernel 3.5.0-rc6, I
get a segmentation fault within 3 or 4 minutes
On Wed, Jul 11, 2012 at 08:09:42AM +0100, Chris Clayton wrote:
Ping.
Have I committed a bug-reporting sin in the mail below or is
everyone simply too busy to look at this kvm-related crash?
Since you have good and bad points can you bisect the problem?
On 07/09/12 11:57, Chris Clayton
On 07/11/12 08:12, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 08:09:42AM +0100, Chris Clayton wrote:
Ping.
Have I committed a bug-reporting sin in the mail below or is
everyone simply too busy to look at this kvm-related crash?
Since you have good and bad points can you bisect the problem?
On Wed, Jul 11, 2012 at 08:18:17AM +0100, Chris Clayton wrote:
On 07/11/12 08:12, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 08:09:42AM +0100, Chris Clayton wrote:
Ping.
Have I committed a bug-reporting sin in the mail below or is
everyone simply too busy to look at this kvm-related crash?
40 matches
Mail list logo
