From: Andrew Randrianasulu <randrianasulu@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1769189] Re: Issue with qemu 2.12.0 + SATA
Date: Sun, 20 May 2018 20:54:50 +0300 [thread overview]
Message-ID: <201805202054.50525.randrianasulu@gmail.com> (raw)
I think I was hit with very same bug.
I did bisect with 2.11.0 as good point and 2.12.0 as bad point.
configure was
setarch
i486 ./configure --prefix=/usr --disable-gtk --enable-virglrenderer --enable-sdl --with-sdlabi=2.0 --audio-drv-list=alsa,oss --host-cc=/opt/gcc49/bin/gcc --enable-opengl --extra-cflags="-I/usr/X11R7/include -O3 -march=i686 -mtune=native -m32 -Wno-maybe-uninitialized -Wno-nested-externs -Wno-implicit-function-declaration" --disable-werror --target-list="x86_64-softmmu"
and launch command
x86_64-softmmu/qemu-system-x86_64 -cdrom
~/Downloads/ISO/slax-English-US-7.0.8-x86_64.iso -enable-kvm -m 1G -M q35
------------
git bisect bad
66eb7825d0bd84a870a054fb208fe765317109fa is the first bad commit
commit 66eb7825d0bd84a870a054fb208fe765317109fa
Author: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
Date: Tue Feb 27 12:53:05 2018 +0300
replay: avoid recursive call of checkpoints
This patch adds a flag which denies recursive call of replay_checkpoint
function. Checkpoints may be accompanied by the hardware events. When event
is processed, virtual device may invoke timer modification functions that
also invoke the checkpoint function. This leads to infinite loop.
Signed-off-by: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>
Message-Id: <20180227095305.1060.56463.stgit@pasha-VirtualBox>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
:040000 040000 f8d1eb18d3a8fcd0df0329e6b899a515e4b0e16e
a286be2d590b42b15f9facf033348ee37c460d25 M replay
-------------
git bisect log
git bisect start
# good: [0a0dc59d27527b78a195c2d838d28b7b49e5a639] Update version for v2.11.0
release
git bisect good 0a0dc59d27527b78a195c2d838d28b7b49e5a639
# bad: [4743c23509a51bd4ee85cc272287a41917d1be35] Update version for v2.12.0
release
git bisect bad 4743c23509a51bd4ee85cc272287a41917d1be35
# skip: [db57d7a3c284db2315d92f55962597cc7276579a] wdt_ib700-test: Drop
dependence on global_qtest
git bisect skip db57d7a3c284db2315d92f55962597cc7276579a
# good: [539022dd6089cdef36589d608ed63cbdaacfd71f] chardev: Clean up previous
patch indentation
git bisect good 539022dd6089cdef36589d608ed63cbdaacfd71f
# good: [9db0855e8501365334e859370800c240d25322a2] Merge remote-tracking
branch 'remotes/pmaydell/tags/pull-target-arm-20180301' into staging
git bisect good 9db0855e8501365334e859370800c240d25322a2
# good: [a57946ff2acb9c0d95c9f127914540586b0b8c21] Merge remote-tracking
branch 'remotes/awilliam/tags/vfio-update-20180313.0' into staging
git bisect good a57946ff2acb9c0d95c9f127914540586b0b8c21
# bad: [211d6260208d079429fd0d447b86ff480d0524ca] Merge remote-tracking
branch 'remotes/kevin/tags/for-upstream' into staging
git bisect bad 211d6260208d079429fd0d447b86ff480d0524ca
# bad: [09b68dab5a11e8657119bc1d2ab18e98a70530ed] vhdx: Support .bdrv_co_create
git bisect bad 09b68dab5a11e8657119bc1d2ab18e98a70530ed
# bad: [3788c7b6e56fa34ee2a73e41706eb2a2447ba75a] Merge remote-tracking
branch 'remotes/bonzini/tags/for-upstream' into staging
git bisect bad 3788c7b6e56fa34ee2a73e41706eb2a2447ba75a
# good: [63f01a74aeeb9c4fb39e2b4100beb084f5c10c95] hw/isa/pc87312: Inherit from
the abstract TYPE_ISA_SUPERIO
git bisect good 63f01a74aeeb9c4fb39e2b4100beb084f5c10c95
# good: [1a96e3c1e7dbb466a8c93743b8f5ae37cc023766] replay: fix processing async
events
git bisect good 1a96e3c1e7dbb466a8c93743b8f5ae37cc023766
# good: [1a423896fa4fc2ea49c64e7a493d88a8b251950d] replay: don't destroy mutex
at exit
git bisect good 1a423896fa4fc2ea49c64e7a493d88a8b251950d
# bad: [821c113033075d4f1b50966d92022a1064085422] scripts/replay-dump.py: replay
log dumper
git bisect bad 821c113033075d4f1b50966d92022a1064085422
# good: [6dc0f5296359ff59c248215a965c8658dea9544b] replay: check return values
of fwrite
git bisect good 6dc0f5296359ff59c248215a965c8658dea9544b
# bad: [66eb7825d0bd84a870a054fb208fe765317109fa] replay: avoid recursive call
of checkpoints
git bisect bad 66eb7825d0bd84a870a054fb208fe765317109fa
# first bad commit: [66eb7825d0bd84a870a054fb208fe765317109fa] replay: avoid
recursive call of checkpoints
------------------------
next reply other threads:[~2018-05-20 18:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-20 17:54 Andrew Randrianasulu [this message]
2018-06-01 11:32 ` [Qemu-devel] [Bug 1769189] Re: Issue with qemu 2.12.0 + SATA Stefan Hajnoczi
-- strict thread matches above, loose matches on Subject: below --
2018-06-01 16:58 Andrew Randrianasulu
2018-05-04 15:31 [Qemu-devel] [Bug 1769189] [NEW] Issue with qemu 2.12.0 + UEFI François Guerraz
2018-05-15 8:42 ` [Qemu-devel] [Bug 1769189] Re: Issue with qemu 2.12.0 + SATA François Guerraz
2018-05-15 16:30 ` Dr. David Alan Gilbert
2018-05-16 21:01 ` blackdevil
2018-05-23 17:30 ` Bruce Rogers
2018-05-25 1:08 ` John Snow
2018-05-25 12:59 ` Bruce Rogers
2018-05-31 0:25 ` John Snow
2018-05-31 19:02 ` John Snow
2018-06-13 20:43 ` John Snow
2018-06-14 7:01 ` Robert Hu
2018-06-14 16:36 ` John Snow
2018-07-22 21:06 ` Peter Maloney
2018-07-23 18:39 ` John Snow
2018-08-15 7:22 ` Thomas Huth
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=201805202054.50525.randrianasulu@gmail.com \
--to=randrianasulu@gmail.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).