From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49611) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZJReo-0008TS-Fa for qemu-devel@nongnu.org; Sun, 26 Jul 2015 15:32:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZJRel-00056E-BA for qemu-devel@nongnu.org; Sun, 26 Jul 2015 15:32:22 -0400 Received: from v220110690675601.yourvserver.net ([37.221.199.173]:52332) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZJRel-000566-5g for qemu-devel@nongnu.org; Sun, 26 Jul 2015 15:32:19 -0400 Message-ID: <55B535BE.60806@weilnetz.de> Date: Sun, 26 Jul 2015 21:32:14 +0200 From: Stefan Weil MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] BIOS regression since v2.3.0 (misaligned longword i/o to address 0xffff) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: QEMU Developer , Gerd Hoffmann Hi, since commit 21f5826a04d38e19488f917e1eef22751490c769 "seabios: update to 1.8.0 release" there is a misaligned i/o access caused by the PC BIOS. QEMU's PC emulation (qemu-system-i386, qemu-system-x86_64) with enabled trace backend reports the misaligned i/o access when running the BIOS code: Misaligned i/o to address 0x0000ffff with size 4 for memory region io ("to address 0x0000ffff" was added by my debug code) This issue was reported by users of QEMU for Windows, but it is not Windows specific. Regards Stefan