From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:54140)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andi@firstfloor.org>) id 1QZWzb-0000ix-8X
	for qemu-devel@nongnu.org; Wed, 22 Jun 2011 19:37:56 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <andi@firstfloor.org>) id 1QZWza-0005Bq-4e
	for qemu-devel@nongnu.org; Wed, 22 Jun 2011 19:37:55 -0400
Received: from mga01.intel.com ([192.55.52.88]:8953)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andi@firstfloor.org>) id 1QZWzZ-0005BN-UL
	for qemu-devel@nongnu.org; Wed, 22 Jun 2011 19:37:54 -0400
From: Andi Kleen <andi@firstfloor.org>
Date: Wed, 22 Jun 2011 16:36:17 -0700
Message-ID: <m27h8dh21a.fsf@firstfloor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Qemu-devel] IO errors in guest caused by LTP dio test
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org


Running LTP testcases/kernel/io/direct_io/test_dma_thread_diotest7
causes IO errors in the guest.  There are no IO errors on the host.

Kernel Linux 3.0.0-rc*
Using a standard emulated IDE -hda image.

I tried a few qemu versions, it happens at least with the one
in FC14 and with 0.14. qemu master doesn't boot and ends
with a spinlock lockup.

Writing file _dma_thread_test_0010.tmp.
Writing file _dma_thread_test_0011.tmp.
Writing file _dma_thread_test_0012.tmp.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x5
ata1.00: failed command: WRITE DMA EXT
ata1.00: cmd 35/00:00:e9:6c:ba/00:04:00:00:00/e0 tag 0 dma 524288 out
         res 41/04:00:e9:6c:ba/04:00:e9:6c:ba/e0 Emask 0x1 (device
         error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ABRT }
ata1.00: configured for MWDMA2
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x5
ata1.00: failed command: WRITE DMA EXT
ata1.00: cmd 35/00:00:e9:6c:ba/00:04:00:00:00/e0 tag 0 dma 524288 out
         res 41/04:00:e9:6c:ba/04:00:e9:6c:ba/e0 Emask 0x1 (device
         error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ABRT }
ata1.00: configured for MWDMA2
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x5
ata1.00: failed command: WRITE DMA EXT
ata1.00: cmd 35/00:00:e9:6c:ba/00:04:00:00:00/e0 tag 0 dma 524288 out
         res 41/04:00:e9:6c:ba/04:00:e9:6c:ba/e0 Emask 0x1 (device
         error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ABRT }
ata1.00: configured for MWDMA2
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x5
ata1.00: failed command: WRITE DMA EXT
ata1.00: cmd 35/00:00:e9:6c:ba/00:04:00:00:00/e0 tag 0 dma 524288 out
         res 41/04:00:e9:6c:ba/04:00:e9:6c:ba/e0 Emask 0x1 (device
         error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ABRT }
ata1.00: configured for MWDMA2
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x5

-- 
ak@linux.intel.com -- Speaking for myself only