From: Jiri Slaby <jslaby@suse.cz>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: David Airlie <airlied@linux.ie>,
virtualization@lists.linux-foundation.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: BUG: 'list_empty(&vgdev->free_vbufs)' is true!
Date: Thu, 15 Dec 2016 14:01:12 +0100 [thread overview]
Message-ID: <a03bbf47-f08a-e54c-a5f4-e639c40f7cee@suse.cz> (raw)
In-Reply-To: <1479301975.25611.23.camel@redhat.com>
On 11/16/2016, 02:12 PM, 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.
>> Run pps [1] without exit(0); on e.g. serial console.
>> Wait a bit. The lot of output causes the BUG.
>>
>> [1] https://github.com/jirislaby/collected_sources/blob/master/pps.c
>
> Doesn't reproduce here.
>
> Running "while true; do dmesg; done" on the virtio-gpu fbcon.
> Running the pps fork bomb on the serial console.
>
> Can watch dmesg printing the kernel messages over and over, until the
> shell can't spawn dmesg any more due to the fork bomb hitting the
> process limit. No BUG() triggered.
>
> Tried spice, gtk and sdl.
>
> Hmm.
>
> Any ideas what else might be needed to reproduce it?
I can reproduce even with count = 32 :(. And without the fork bomb (i.e.
with the code from the repository).
This is how I start qemu:
/usr/bin/qemu-system-x86_64 -machine accel=kvm -k en-us -smp 4 -m 2371
-usb -device virtio-rng-pci -drive
file=/home/new/suse-fact.img,format=raw,discard=unmap,if=none,id=hd
-device virtio-scsi-pci,id=scsi -device scsi-hd,drive=hd -soundhw hda
-net
user,tftp=/home/xslaby/tftp,bootfile=/pxelinux.0,hostfwd=tcp::2222-:22,hostfwd=tcp::3632-:3632
-net nic,model=virtio -serial pty -balloon virtio -device
virtio-tablet-pci -vga virtio -kernel
/home/latest/my/arch/x86/boot/bzImage -append root=/dev/sda1
console=ttyS0,115200 loglevel=debug -snapshot
I do
dmesg -w # on the console
and on serial console:
while :; do for aa in `seq 1 10`; do ./pps & done; wait; done
Note the latter can cause interrupt "storm" (~ 700 irqs per second) as
much output is generated. This can lead to some race condition. serial
is on IRQ4 and virtio gpu on IRQ10 which has lower priority AFAIK.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2016-12-15 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bfe29853-694b-6cb5-02e7-6986a9927438@suse.cz>
2016-11-08 20:37 ` BUG: 'list_empty(&vgdev->free_vbufs)' is true! 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
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 ` Jiri Slaby [this message]
2016-11-11 14:35 ` BUG: 'list_empty(&vgdev->free_vbufs)' is true! 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=a03bbf47-f08a-e54c-a5f4-e639c40f7cee@suse.cz \
--to=jslaby@suse.cz \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--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).