From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Leonardo Soares Müller" <leozinho29_eu@hotmail.com>
Cc: "kraxel@redhat.com" <kraxel@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Crash when booting KDE Neon using qxl-vga
Date: Mon, 28 Jan 2019 17:35:36 +0000 [thread overview]
Message-ID: <20190128173536.GE2585@work-vm> (raw)
In-Reply-To: <RO1P152MB1483C38DCFD740BD8982F39597960@RO1P152MB1483.LAMP152.PROD.OUTLOOK.COM>
* Leonardo Soares Müller (leozinho29_eu@hotmail.com) wrote:
> Here is the backtrace with the debug symbols added:
OK, great; can can you confirm the version of the spice packages
on both the guest and host, and the kernel on the guest.
Dave
> (gdb) bt
> #0 0x00007ffff0373e97 in __GI_raise (sig=sig@entry=6) at
> ../sysdeps/unix/sysv/linux/raise.c:51
> #1 0x00007ffff0375801 in __GI_abort () at abort.c:79
> #2 0x00007ffff1171cc9 in spice_logv (log_domain=0x7ffff11dc9f5 "Spice",
> args=0x7fff36028cb0, format=0x7ffff11e3c5b "slot_id %d too big,
> addr=%lx", function=0x7ffff11e3d90 <__FUNCTION__.15594>
> "memslot_get_virt", strloc=0x7ffff11e3c78 "memslot.c:111",
> log_level=G_LOG_LEVEL_CRITICAL) at log.c:183
> #3 0x00007ffff1171cc9 in spice_log
> (log_level=log_level@entry=G_LOG_LEVEL_CRITICAL,
> strloc=strloc@entry=0x7ffff11e3c78 "memslot.c:111",
> function=function@entry=0x7ffff11e3d90 <__FUNCTION__.15594>
> "memslot_get_virt", format=format@entry=0x7ffff11e3c5b "slot_id %d too
> big, addr=%lx") at log.c:196
> #4 0x00007ffff11373b8 in memslot_get_virt
> (info=info@entry=0x5555579b8630, addr=addr@entry=18374686483949813760,
> add_size=add_size@entry=10, group_id=group_id@entry=1,
> error=error@entry=0x7fff36028e08)
> at memslot.c:111
> #5 0x00007ffff11407d0 in red_get_image
> (slots=slots@entry=0x5555579b8630, group_id=group_id@entry=1,
> addr=<optimized out>, flags=flags@entry=0, is_mask=is_mask@entry=false)
> at red-parse-qxl.c:512
> #6 0x00007ffff1140a76 in red_get_copy_ptr
> (slots=slots@entry=0x5555579b8630, group_id=group_id@entry=1,
> red=red@entry=0x7fff1409f5f0, qxl=0x7fff1fe0107b, flags=flags@entry=0)
> at red-parse-qxl.c:680
> #7 0x00007ffff11419a1 in red_get_native_drawable (flags=<optimized
> out>, addr=<optimized out>, red=<optimized out>, group_id=<optimized
> out>, slots=<optimized out>) at red-parse-qxl.c:1072
> #8 0x00007ffff11419a1 in red_get_drawable
> (slots=slots@entry=0x5555579b8630, group_id=1,
> red=red@entry=0x7fff1409f550, addr=<optimized out>, flags=0) at
> red-parse-qxl.c:1206
> #9 0x00007ffff11543cd in red_process_display (worker=0x5555579b85a0,
> ring_is_empty=0x7fff36028f9c) at red-worker.c:224
> #10 0x00007ffff1152d21 in flush_commands
> (worker=worker@entry=0x5555579b85a0, red_channel=0x5555579b4a10,
> process=process@entry=0x7ffff1154220 <red_process_display>) at
> red-worker.c:315
> #11 0x00007ffff1152e58 in flush_display_commands
> (worker=worker@entry=0x5555579b85a0) at red-worker.c:352
> #12 0x00007ffff11534bf in flush_all_qxl_commands (worker=0x5555579b85a0)
> at red-worker.c:367
> #13 0x00007ffff11534bf in destroy_primary_surface
> (worker=0x5555579b85a0, surface_id=0) at red-worker.c:558
> #14 0x00007ffff11214f1 in dispatcher_handle_single_read
> (dispatcher=0x555556a0c1c0) at dispatcher.c:284
> #15 0x00007ffff11214f1 in dispatcher_handle_recv_read
> (dispatcher=0x555556a0c1c0) at dispatcher.c:304
> #16 0x00007ffff1127d7b in watch_func (source=<optimized out>,
> condition=<optimized out>, data=0x5555579b8780) at event-loop.c:128
> #17 0x00007ffff47931f5 in g_main_context_dispatch () at
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #18 0x00007ffff47935c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #19 0x00007ffff47938d2 in g_main_loop_run () at
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #20 0x00007ffff1153b3a in red_worker_main (arg=0x5555579b85a0) at
> red-worker.c:1372
> #21 0x00007ffff072d6db in start_thread (arg=0x7fff3602c700) at
> pthread_create.c:463
> #22 0x00007ffff045688f in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
>
>
> Às 10:13 de 28/01/2019, Dr. David Alan Gilbert escreveu:
> >
> > Thanks for the report,
> >
> > Could you install the debug packages of libspice-server on your system
> > so that the backtrace you get has symbols?
> >
> > Dave
> >
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-01-28 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 23:44 [Qemu-devel] Crash when booting KDE Neon using qxl-vga Leonardo Soares Müller
2019-01-28 12:13 ` Dr. David Alan Gilbert
2019-01-28 17:14 ` Leonardo Soares Müller
2019-01-28 17:35 ` Dr. David Alan Gilbert [this message]
2019-01-28 19:48 ` Leonardo Soares Müller
2019-02-01 13:36 ` Dr. David Alan Gilbert
2019-02-01 15:39 ` Leonardo Soares Müller
2019-02-01 20:28 ` Dr. David Alan Gilbert
2019-02-01 22:39 ` Leonardo Soares Müller
2019-02-14 10:42 ` Dr. David Alan Gilbert
2019-02-01 17:57 ` Leonardo Soares Müller
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=20190128173536.GE2585@work-vm \
--to=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=leozinho29_eu@hotmail.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).