From: Gerd Hoffmann <kraxel@redhat.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
virtualization@lists.linux-foundation.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org
Subject: Re: BUG: 'list_empty(&vgdev->free_vbufs)' is true!
Date: Tue, 15 Nov 2016 10:05:03 +0100 [thread overview]
Message-ID: <1479200703.32639.19.camel@redhat.com> (raw)
In-Reply-To: <18ae4a55-7c36-b55c-0ce3-03aef0bab1ec@suse.cz>
On Di, 2016-11-15 at 09:55 +0100, Jiri Slaby wrote:
> On 11/15/2016, 09:46 AM, Gerd Hoffmann wrote:
> > On Fr, 2016-11-11 at 17:28 +0100, Jiri Slaby wrote:
> >> On 11/09/2016, 09:01 AM, Gerd Hoffmann wrote:
> >>> On Di, 2016-11-08 at 22:37 +0200, Michael S. Tsirkin wrote:
> >>>> On Mon, Nov 07, 2016 at 09:43:24AM +0100, Jiri Slaby wrote:
> >>>>> Hi,
> >>>>>
> >>>>> I can relatively easily reproduce this bug:
> >>>
> >>> How?
> >>
> >> Run dmesg -w in the qemu window (virtio_gpu) to see a lot of output.
> >
> > fbcon? Or xorg/wayland with terminal app?
>
> Ah, just console, so fbcon. No X server running.
Hmm, /me looks puzzled. fbcon doesn't do cursor updates, so the cursor
queue can hardly be full and there should be enough buffers even without
allocating 16 extra bufs. I'll go try reproduce and analyze that one.
The +16 patch submitted nevertheless as temporary stopgap.
cheers,
Gerd
next prev parent reply other threads:[~2016-11-15 9:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 8:43 BUG: 'list_empty(&vgdev->free_vbufs)' is true! Jiri Slaby
2016-11-08 20:37 ` Michael S. Tsirkin
2016-11-09 8:01 ` Gerd Hoffmann
2016-11-11 16:28 ` Jiri Slaby
2016-11-15 8:46 ` Gerd Hoffmann
2016-11-15 8:55 ` Jiri Slaby
2016-11-15 9:05 ` Gerd Hoffmann [this message]
2016-11-16 13:12 ` Gerd Hoffmann
2016-11-24 2:57 ` virtio gpu sparse warning Michael S. Tsirkin
2016-11-28 7:50 ` Gerd Hoffmann
2016-12-15 13:01 ` BUG: 'list_empty(&vgdev->free_vbufs)' is true! Jiri Slaby
2016-11-11 14:35 ` Jiri Slaby
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=1479200703.32639.19.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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).