* [Qemu-devel] Segfault starting vcpu thread
@ 2012-07-11 11:46 Avi Kivity
2012-07-11 11:55 ` Jan Kiszka
0 siblings, 1 reply; 7+ messages in thread
From: Avi Kivity @ 2012-07-11 11:46 UTC (permalink / raw)
To: Jan Kiszka; +Cc: qemu-devel, KVM list
Current qemu-kvm master merged with latest upstream fails on startup:
(gdb) bt
#0 0x00007fdcd4a047a0 in kvm_vcpu_ioctl (env=0x0, type=-1071075694) at
/home/tlv/akivity/qemu/kvm-all.c:1602
#1 0x00007fdcd49c9fda in kvm_apic_enable_tpr_reporting
(s=0x7fdcd75af6c0, enable=false) at
/home/tlv/akivity/qemu/hw/i386/../kvm/apic.c:107
#2 0x00007fdcd4993d71 in flush_queued_work (env=0x7fdcd75a0c70) at
/home/tlv/akivity/qemu/cpus.c:680
#3 0x00007fdcd4993e23 in qemu_wait_io_event_common (env=0x7fdcd75a0c70)
at /home/tlv/akivity/qemu/cpus.c:694
#4 0x00007fdcd4993f61 in qemu_kvm_wait_io_event (env=0x7fdcd75a0c70) at
/home/tlv/akivity/qemu/cpus.c:725
#5 0x00007fdcd499408c in qemu_kvm_cpu_thread_fn (arg=0x7fdcd75a0c70) at
/home/tlv/akivity/qemu/cpus.c:757
#6 0x00007fdcd2e72d14 in start_thread () from /lib64/libpthread.so.0
APICCommonState::cpu_env in frame 1 is NULL. I'm looking at it, but if
you have a quick fix, all the better.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Segfault starting vcpu thread
2012-07-11 11:46 [Qemu-devel] Segfault starting vcpu thread Avi Kivity
@ 2012-07-11 11:55 ` Jan Kiszka
2012-07-11 11:58 ` Avi Kivity
0 siblings, 1 reply; 7+ messages in thread
From: Jan Kiszka @ 2012-07-11 11:55 UTC (permalink / raw)
To: Avi Kivity; +Cc: qemu-devel, KVM list
On 2012-07-11 13:46, Avi Kivity wrote:
> Current qemu-kvm master merged with latest upstream fails on startup:
>
> (gdb) bt
> #0 0x00007fdcd4a047a0 in kvm_vcpu_ioctl (env=0x0, type=-1071075694) at
> /home/tlv/akivity/qemu/kvm-all.c:1602
> #1 0x00007fdcd49c9fda in kvm_apic_enable_tpr_reporting
> (s=0x7fdcd75af6c0, enable=false) at
> /home/tlv/akivity/qemu/hw/i386/../kvm/apic.c:107
> #2 0x00007fdcd4993d71 in flush_queued_work (env=0x7fdcd75a0c70) at
> /home/tlv/akivity/qemu/cpus.c:680
> #3 0x00007fdcd4993e23 in qemu_wait_io_event_common (env=0x7fdcd75a0c70)
> at /home/tlv/akivity/qemu/cpus.c:694
> #4 0x00007fdcd4993f61 in qemu_kvm_wait_io_event (env=0x7fdcd75a0c70) at
> /home/tlv/akivity/qemu/cpus.c:725
> #5 0x00007fdcd499408c in qemu_kvm_cpu_thread_fn (arg=0x7fdcd75a0c70) at
> /home/tlv/akivity/qemu/cpus.c:757
> #6 0x00007fdcd2e72d14 in start_thread () from /lib64/libpthread.so.0
>
> APICCommonState::cpu_env in frame 1 is NULL. I'm looking at it, but if
> you have a quick fix, all the better.
>
I will try to reproduce. Is there a tree of the merge available? Any
specific command line or guest?
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Segfault starting vcpu thread
2012-07-11 11:55 ` Jan Kiszka
@ 2012-07-11 11:58 ` Avi Kivity
2012-07-11 11:59 ` Jan Kiszka
0 siblings, 1 reply; 7+ messages in thread
From: Avi Kivity @ 2012-07-11 11:58 UTC (permalink / raw)
To: Jan Kiszka; +Cc: qemu-devel, KVM list
On 07/11/2012 02:55 PM, Jan Kiszka wrote:
> On 2012-07-11 13:46, Avi Kivity wrote:
>> Current qemu-kvm master merged with latest upstream fails on startup:
>>
>> (gdb) bt
>> #0 0x00007fdcd4a047a0 in kvm_vcpu_ioctl (env=0x0, type=-1071075694) at
>> /home/tlv/akivity/qemu/kvm-all.c:1602
>> #1 0x00007fdcd49c9fda in kvm_apic_enable_tpr_reporting
>> (s=0x7fdcd75af6c0, enable=false) at
>> /home/tlv/akivity/qemu/hw/i386/../kvm/apic.c:107
>> #2 0x00007fdcd4993d71 in flush_queued_work (env=0x7fdcd75a0c70) at
>> /home/tlv/akivity/qemu/cpus.c:680
>> #3 0x00007fdcd4993e23 in qemu_wait_io_event_common (env=0x7fdcd75a0c70)
>> at /home/tlv/akivity/qemu/cpus.c:694
>> #4 0x00007fdcd4993f61 in qemu_kvm_wait_io_event (env=0x7fdcd75a0c70) at
>> /home/tlv/akivity/qemu/cpus.c:725
>> #5 0x00007fdcd499408c in qemu_kvm_cpu_thread_fn (arg=0x7fdcd75a0c70) at
>> /home/tlv/akivity/qemu/cpus.c:757
>> #6 0x00007fdcd2e72d14 in start_thread () from /lib64/libpthread.so.0
>>
>> APICCommonState::cpu_env in frame 1 is NULL. I'm looking at it, but if
>> you have a quick fix, all the better.
>>
>
> I will try to reproduce. Is there a tree of the merge available?
I just merged upstream into qemu-kvm master. For some reason there were
no conflicts.
> Any
> specific command line or guest?
qemu-system-x86_64
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Segfault starting vcpu thread
2012-07-11 11:58 ` Avi Kivity
@ 2012-07-11 11:59 ` Jan Kiszka
2012-07-11 12:04 ` Avi Kivity
0 siblings, 1 reply; 7+ messages in thread
From: Jan Kiszka @ 2012-07-11 11:59 UTC (permalink / raw)
To: Avi Kivity; +Cc: qemu-devel, KVM list
On 2012-07-11 13:58, Avi Kivity wrote:
> On 07/11/2012 02:55 PM, Jan Kiszka wrote:
>> On 2012-07-11 13:46, Avi Kivity wrote:
>>> Current qemu-kvm master merged with latest upstream fails on startup:
>>>
>>> (gdb) bt
>>> #0 0x00007fdcd4a047a0 in kvm_vcpu_ioctl (env=0x0, type=-1071075694) at
>>> /home/tlv/akivity/qemu/kvm-all.c:1602
>>> #1 0x00007fdcd49c9fda in kvm_apic_enable_tpr_reporting
>>> (s=0x7fdcd75af6c0, enable=false) at
>>> /home/tlv/akivity/qemu/hw/i386/../kvm/apic.c:107
>>> #2 0x00007fdcd4993d71 in flush_queued_work (env=0x7fdcd75a0c70) at
>>> /home/tlv/akivity/qemu/cpus.c:680
>>> #3 0x00007fdcd4993e23 in qemu_wait_io_event_common (env=0x7fdcd75a0c70)
>>> at /home/tlv/akivity/qemu/cpus.c:694
>>> #4 0x00007fdcd4993f61 in qemu_kvm_wait_io_event (env=0x7fdcd75a0c70) at
>>> /home/tlv/akivity/qemu/cpus.c:725
>>> #5 0x00007fdcd499408c in qemu_kvm_cpu_thread_fn (arg=0x7fdcd75a0c70) at
>>> /home/tlv/akivity/qemu/cpus.c:757
>>> #6 0x00007fdcd2e72d14 in start_thread () from /lib64/libpthread.so.0
>>>
>>> APICCommonState::cpu_env in frame 1 is NULL. I'm looking at it, but if
>>> you have a quick fix, all the better.
>>>
>>
>> I will try to reproduce. Is there a tree of the merge available?
>
> I just merged upstream into qemu-kvm master. For some reason there were
> no conflicts.
A rare moment, I guess. ;)
>
>> Any
>> specific command line or guest?
>
> qemu-system-x86_64
Just did the same, but it's all fine here.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Segfault starting vcpu thread
2012-07-11 11:59 ` Jan Kiszka
@ 2012-07-11 12:04 ` Avi Kivity
2012-07-11 12:08 ` Avi Kivity
0 siblings, 1 reply; 7+ messages in thread
From: Avi Kivity @ 2012-07-11 12:04 UTC (permalink / raw)
To: Jan Kiszka; +Cc: qemu-devel, KVM list
On 07/11/2012 02:59 PM, Jan Kiszka wrote:
>>>
>>> I will try to reproduce. Is there a tree of the merge available?
>>
>> I just merged upstream into qemu-kvm master. For some reason there were
>> no conflicts.
>
> A rare moment, I guess. ;)
I'll put it down to random chance until we can figure out who's responsible.
>
>>
>>> Any
>>> specific command line or guest?
>>
>> qemu-system-x86_64
>
> Just did the same, but it's all fine here.
Ok, I'll debug it. Probably something stupid like a miscompile.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Segfault starting vcpu thread
2012-07-11 12:04 ` Avi Kivity
@ 2012-07-11 12:08 ` Avi Kivity
2012-07-11 12:40 ` Paolo Bonzini
0 siblings, 1 reply; 7+ messages in thread
From: Avi Kivity @ 2012-07-11 12:08 UTC (permalink / raw)
To: Jan Kiszka; +Cc: Paolo Bonzini, qemu-devel, KVM list
On 07/11/2012 03:04 PM, Avi Kivity wrote:
>>>> specific command line or guest?
>>>
>>> qemu-system-x86_64
>>
>> Just did the same, but it's all fine here.
>
> Ok, I'll debug it. Probably something stupid like a miscompile.
Indeed, a simple clean build fixed it up. Paolo, it looks like
autodependencies are still broken.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Segfault starting vcpu thread
2012-07-11 12:08 ` Avi Kivity
@ 2012-07-11 12:40 ` Paolo Bonzini
0 siblings, 0 replies; 7+ messages in thread
From: Paolo Bonzini @ 2012-07-11 12:40 UTC (permalink / raw)
To: Avi Kivity; +Cc: Jan Kiszka, qemu-devel, KVM list
Il 11/07/2012 14:08, Avi Kivity ha scritto:
>>>>> specific command line or guest?
>>>> >>>
>>>> >>> qemu-system-x86_64
>>> >>
>>> >> Just did the same, but it's all fine here.
>> >
>> > Ok, I'll debug it. Probably something stupid like a miscompile.
> Indeed, a simple clean build fixed it up. Paolo, it looks like
> autodependencies are still broken.
Hmm, I think everything happened while I was away. I'll take a look.
Paolo
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2012-07-11 12:40 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-07-11 11:46 [Qemu-devel] Segfault starting vcpu thread Avi Kivity
2012-07-11 11:55 ` Jan Kiszka
2012-07-11 11:58 ` Avi Kivity
2012-07-11 11:59 ` Jan Kiszka
2012-07-11 12:04 ` Avi Kivity
2012-07-11 12:08 ` Avi Kivity
2012-07-11 12:40 ` Paolo Bonzini
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).