All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	virtualization@lists.linux-foundation.org,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: BUG: 'list_empty(&vgdev->free_vbufs)' is true!
Date: Mon, 7 Nov 2016 09:43:24 +0100	[thread overview]
Message-ID: <bfe29853-694b-6cb5-02e7-6986a9927438@suse.cz> (raw)

Hi,

I can relatively easily reproduce this bug:
BUG: 'list_empty(&vgdev->free_vbufs)' is true!
------------[ cut here ]------------
kernel BUG at /home/latest/linux/drivers/gpu/drm/virtio/virtgpu_vq.c:130!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 355 Comm: kworker/1:2 Not tainted 4.9.0-rc2-next-20161028+ #32
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org 04/01/2014
Workqueue: events drm_fb_helper_dirty_work
task: ffff88007b124980 task.stack: ffff88007b8a0000
RIP: 0010:virtio_gpu_get_vbuf+0x32e/0x630
RSP: 0018:ffff88007b8a78c0 EFLAGS: 00010286
RAX: 000000000000002e RBX: 1ffff1000f714f1d RCX: 0000000000000000
RDX: 000000000000002e RSI: 0000000000000001 RDI: ffffed000f714f0e
RBP: ffff88007b8a7970 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000002 R11: 0000000000000001 R12: 0000000000000030
R13: ffff88007caeaba8 R14: 0000000000000018 R15: ffff88007cae0000
FS:  0000000000000000(0000) GS:ffff88007dc80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000601028 CR3: 000000007740d000 CR4: 00000000000006e0
Call Trace:
Code: df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 bb 01 00 00 4c 89 69 e8
eb 9e 48 c7 c6 e0 d2 d1 83 48 c7 c7 20 d3 d1 83 e8 6c fb 04 ff <0f> 0b
48 c7 c7 a0 fb b0 85 e8 09 95 86 ff 48 c7 c6 c0 d3 d1 83
RIP: virtio_gpu_get_vbuf+0x32e/0x630 RSP: ffff88007b8a78c0


There is no stacktrace, as the kernel starts panicing all over the place
during its generation. Any ideas?

thanks,
-- 
js
suse labs

             reply	other threads:[~2016-11-07 15:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07  8:43 Jiri Slaby [this message]
2016-11-08 20:37 ` BUG: 'list_empty(&vgdev->free_vbufs)' is true! Michael S. Tsirkin
2016-11-08 20:37   ` Michael S. Tsirkin
2016-11-09  8:01   ` Gerd Hoffmann
2016-11-09  8:01     ` Gerd Hoffmann
2016-11-11 16:28     ` Jiri Slaby
2016-11-11 16:28     ` Jiri Slaby
2016-11-15  8:46       ` Gerd Hoffmann
2016-11-15  8:46       ` Gerd Hoffmann
2016-11-15  8:46         ` Gerd Hoffmann
2016-11-15  8:55         ` Jiri Slaby
2016-11-15  8:55         ` Jiri Slaby
2016-11-15  8:55           ` Jiri Slaby
2016-11-15  9:05           ` Gerd Hoffmann
2016-11-15  9:05           ` Gerd Hoffmann
2016-11-16 13:12       ` Gerd Hoffmann
2016-11-16 13:12         ` Gerd Hoffmann
2016-11-24  2:57         ` virtio gpu sparse warning Michael S. Tsirkin
2016-11-24  2:57           ` Michael S. Tsirkin
2016-11-28  7:50           ` Gerd Hoffmann
2016-11-28  7:50           ` Gerd Hoffmann
2016-11-28  7:50             ` Gerd Hoffmann
2016-12-15 13:01         ` BUG: 'list_empty(&vgdev->free_vbufs)' is true! Jiri Slaby
2016-12-15 13:01           ` Jiri Slaby
2016-11-11 14:35   ` Jiri Slaby
2016-11-11 14:35   ` Jiri Slaby
2016-11-08 20:37 ` Michael S. Tsirkin

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=bfe29853-694b-6cb5-02e7-6986a9927438@suse.cz \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.