From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LOEbc-00080p-PQ for qemu-devel@nongnu.org; Sat, 17 Jan 2009 12:05:08 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LOEbb-0007yb-6g for qemu-devel@nongnu.org; Sat, 17 Jan 2009 12:05:08 -0500 Received: from [199.232.76.173] (port=45295 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LOEbb-0007yS-2R for qemu-devel@nongnu.org; Sat, 17 Jan 2009 12:05:07 -0500 Received: from fmmailgate02.web.de ([217.72.192.227]:52415) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LOEbZ-0007iF-Kq for qemu-devel@nongnu.org; Sat, 17 Jan 2009 12:05:06 -0500 Message-ID: <49720FB6.1030208@web.de> Date: Sat, 17 Jan 2009 18:04:54 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <4971C8E5.3050501@web.de> In-Reply-To: <4971C8E5.3050501@web.de> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig058C9E627BF72E79B701A46F" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: cirrus-vga is not properly reset Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "qemu-devel@nongnu.org" Cc: Avi Kivity , kvm-devel This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig058C9E627BF72E79B701A46F Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Jan Kiszka wrote: > Hi, >=20 > when rebooting from non-text mode, the text output of BIOS and > bootloader is unreadable. This only happens with cirrus and the KVM > tree, std-vga is fine, cirrus with upstream QEMU is fine, too. Moreover= , > -no-kvm makes no difference. Looked at it again, and I was able to reproduce this problem with latest QEMU, too. It just doesn't trigger that reliably as with kvm-userspace. So I bet it has something to do with recent QEMU reset changes for vga and cirrus (the display changes are not yet merged into kvm, so they can't contribute to the reason). Moreover, the error pattern suggests that correct text is written to the VGA RAM and attempted to dump to the screen, but the font that should have been written to VGA RAM by the BIOS is corrupted. >=20 > What's very strange about this: CirrusVGAState does not differ after > issuing a reset from text mode compared to a reset from graphic mode > (except for a needless re-init of some io_memory slots - will post a > cleanup patch upstream). Currently I have no clue where to look next. >=20 > Jan >=20 Jan --------------enig058C9E627BF72E79B701A46F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAklyD74ACgkQniDOoMHTA+nZ5wCfQapcMQX0q/ckAMUTjwI0AX/o 2isAn1zGQd63iua6jTDacXuI+NcnnT1E =eCrB -----END PGP SIGNATURE----- --------------enig058C9E627BF72E79B701A46F--