From: Blue Swirl <blauwirbel@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Peter Lieven <pl@dlh.net>, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] possible regression in qemu-kvm 0.13.0 (memtest)
Date: Tue, 28 Dec 2010 20:41:46 +0000 [thread overview]
Message-ID: <AANLkTimzwZFunzamgBDLVvFDYY1v_mwb+oWLGusptjpt@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim9viMhuDETnqFOE1o5qH5=RLvAWUo-hJ0JqeBx@mail.gmail.com>
On Mon, Dec 27, 2010 at 3:47 AM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Sat, Dec 25, 2010 at 7:02 PM, Peter Lieven <pl@dlh.net> wrote:
>> this was the outcome of my bisect session:
>>
>> 956a3e6bb7386de48b642d4fee11f7f86a2fcf9a is first bad commit
>> commit 956a3e6bb7386de48b642d4fee11f7f86a2fcf9a
>> Author: Blue Swirl <blauwirbel@gmail.com>
>> Date: Sat May 22 07:59:01 2010 +0000
>>
>> Compile pckbd only once
>>
>> Use a qemu_irq to indicate A20 line changes. Move I/O port 92
>> to pckbd.c.
>>
>> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
>>
>> :100644 100644 acbaf227455f931f3ef6dbe0bb4494c6b41f2cd9 1a33d4eb4a5624c55896871b5f4ecde78a49ff28 M Makefile.objs
>> :100644 100644 a22484e1e98355a35deeb5038a45fb8fe8685a91 ba5147fbc48e4faef072a5be6b0d69d3201c1e18 M Makefile.target
>> :040000 040000 dd03f81a42b5162c93c40c517f45eb9f7bece93c 309f472328632319a15128a59715aa63daf4d92c M default-configs
>> :040000 040000 83201c4fcde2f592a771479246e0a33a8906515b b1192bce85f2a7129fb19cf2fe7462ef168165cb M hw
>> bisect run success
>
> Nice job bisecting this! I can reproduce the Memtest86+ V4.10 system
> reset with qemu-kvm.git and qemu.git.
>
> The following code path is hit when val=0x2:
> if (!(val & 1)) {
> qemu_system_reset_request();
> }
>
> I think unifying ioport 0x92 and KBD_CCMD_WRITE_OUTPORT was incorrect.
> ioport 0x92 is the System Control Port A and resets the system if bit
> 0 is 1. The keyboard outport seems to reset if bit 0 is 0.
>
> Here are the links I've found describing the i8042 keyboard controller
> and System Control Port A:
> http://www.computer-engineering.org/ps2keyboard/
> http://www.win.tue.nl/~aeb/linux/kbd/A20.html
>
> Blue Swirl: Any thoughts on this?
SMSC LPC47S45x data sheet (p. 112) also confirms this. The proper fix
is to split the ports.
But then A20 logic becomes more complex, disabling either of keyboard
or port 92 A20 lines should disable system A20 gate.
I think we should move port 92 back to pc.c and add the missing A20
logic there as well.
prev parent reply other threads:[~2010-12-28 20:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 10:02 [Qemu-devel] possible regression in qemu-kvm 0.13.0 (memtest) Peter Lieven
2010-12-23 2:42 ` Stefan Hajnoczi
2010-12-25 19:02 ` Peter Lieven
2010-12-26 21:21 ` FIXED: " Peter Lieven
2010-12-27 3:51 ` Stefan Hajnoczi
2010-12-27 7:59 ` Peter Lieven
2011-01-05 17:01 ` Serge E. Hallyn
2011-01-06 11:24 ` Stefan Hajnoczi
2011-01-06 16:41 ` Serge E. Hallyn
2011-01-06 18:24 ` Blue Swirl
2010-12-28 12:38 ` Peter Lieven
2010-12-27 3:47 ` Stefan Hajnoczi
2010-12-28 20:41 ` Blue Swirl [this message]
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=AANLkTimzwZFunzamgBDLVvFDYY1v_mwb+oWLGusptjpt@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pl@dlh.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).