qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL for-2.1 00/22] Block patches for 2.1.0-rc2


From: Peter Maydell
Subject: Re: [Qemu-devel] [PULL for-2.1 00/22] Block patches for 2.1.0-rc2
Date: Fri, 11 Jul 2014 13:46:54 +0100

On 10 July 2014 13:35, Kevin Wolf <address@hidden> wrote:
> The following changes since commit 675879f6f3c9463e103735a4e41e9deb0bee9b39:
>
>   Update version for v2.1.0-rc1 release (2014-07-08 16:53:59 +0100)
>
> are available in the git repository at:
>
>   git://repo.or.cz/qemu/kevin.git tags/for-upstream
>
> for you to fetch changes up to ccd3583aed26144b752ff48d11e2a0e551ddbe19:
>
>   ide: Treat read/write beyond end as invalid (2014-07-10 12:55:39 +0200)
>
> ----------------------------------------------------------------
> Block patches for 2.1.0-rc2

I'm afraid this fails 'make check' on my 32 bit ARM box:

TEST: tests/hd-geo-test... (pid=5395)
  /i386/hd-geo/ide/none:                                               OK
  /i386/hd-geo/ide/drive/mbr/blank:
qemu-system-i386: /root/qemu/block/raw-posix.c:1030: paio_submit:
Assertion `qiov->size == acb->aio_nbytes' failed.
Broken pipe
FAIL
GTester: last random seed: R02S10fb9de706ffe8751465b3da08786cf3
(pid=5400)
  /i386/hd-geo/ide/drive/mbr/lba:
qemu-system-i386: /root/qemu/block/raw-posix.c:1030: paio_submit:
Assertion `qiov->size == acb->aio_nbytes' failed.
Broken pipe
FAIL
GTester: last random seed: R02S88fb3c4a374bf0ffbe13ecc2b89cd471
(pid=5403)
  /i386/hd-geo/ide/drive/mbr/chs:
qemu-system-i386: /root/qemu/block/raw-posix.c:1030: paio_submit:
Assertion `qiov->size == acb->aio_nbytes' failed.
Broken pipe
FAIL

(and similarly with all the other hd-geo tests.)

I tried to get a backtrace but unfortunately it seems to be
pretty much impossible given the way the test case
starts QEMU as a separate process. I tried arranging
to attach gdb to that process but it dies with a SIGTERM
before actually doing anything interesting if I do that.

thanks
-- PMM



reply via email to

[Prev in Thread] Current Thread [Next in Thread]