From: Philipp Hahn <pmhahn@pmhahn.de>
To: Philipp Hahn <hahn@univention.de>, Laszlo Ersek <lersek@redhat.com>
Cc: qemu-devel@nongnu.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Peter Jones <pjones@redhat.com>,
linux-fbdev@vger.kernel.org
Subject: Re: [Qemu-devel] [RFH] qemu-2.6 memory corruption with OVMF and linux-4.9
Date: Tue, 20 Jun 2017 12:08:56 +0200 [thread overview]
Message-ID: <d323a0b6-164f-7378-c565-e42128cf56b6@pmhahn.de> (raw)
In-Reply-To: <58d3a273-e857-fe9e-0b1e-a4aca4aa54ef@univention.de>
Hello,
Am 18.06.2017 um 20:22 schrieb Philipp Hahn:
> Am 17.06.2017 um 18:51 schrieb Laszlo Ersek:
>> (I also recommend using the "vbindiff" tool for such problems, it is
>> great for picking out patterns.)
>>
>> ** ** ** ** ** ** ** ** 8 9 ** ** ** 13 14 15
>> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 00000000 01 e8 00 00 00 00 00 00 8c 5e 00 00 00 10 ff f1
>> 00000010 5b 78 8a 3e 00 00 00 00 00 00 00 00 00 00 00 00
>> 00000020 8c 77 00 00 00 12 00 02 18 f0 00 00 00 00 00 00
>> 00000030 00 1e 00 00 00 00 00 00 8c 8c 00 00 00 12 00 02
>> 00000040 07 70 00 00 00 00 00 00 00 14 00 00 00 00 00 00
>> 00000050 8c 9c 00 00 00 12 00 02 22 00 00 00 00 00 00 00
>> 00000060 00 40 00 00 00 00 00 00 8c ac 00 00 00 10 ff f1
>>
>> 00000000 01 e8 00 00 00 00 00 00 00 3c 00 00 00 17 00 00
>> 00000010 5b 78 8a 3e 00 00 00 00 00 3c 00 00 00 07 00 00
>> 00000020 8c 77 00 00 00 12 00 02 00 3c 00 00 00 07 00 00
>> 00000030 00 1e 00 00 00 00 00 00 00 3c 00 00 00 17 00 00
>> 00000040 07 70 00 00 00 00 00 00 00 3c 00 00 00 07 00 00
>> 00000050 8c 9c 00 00 00 12 00 02 00 3c 00 00 00 07 00 00
>> 00000060 00 40 00 00 00 00 00 00 00 3c 00 00 00 17 00 00
>> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> ** ** ** ** ** ** ** ** 8 9 ** ** ** 13 14 15
>>
>> The columns that I marked with "**" are identical between "good" and
>> "bad". (These are columns 0-7, 10-12.)
>>
>> Column 8 is overwritten by zeros (every 16th byte).
>>
>> Column 9 is overwritten by 0x3c (every 16th byte).
>>
>> Column 13 is super interesting. The most significant nibble in that
>> column is not disturbed. And, in the least significant nibble, the least
>> significant three bits are turned on. Basically, the corruption could be
>> described, for this column (i.e., every 16th byte), as
>>
>> bad = good | 0x7
>>
>> Column 14 is overwritten by zeros (every 16th byte).
>>
>> Column 15 is overwritten by zeros (every 16th byte).
>>
>> My take is that your host machine has faulty RAM. Please run memtest86+
>> or something similar.
>
> I will do so, but for me very unlikely:
> - it never happens with BIOS, only with OVMF
> - for each test I start q new QEMU process, which should use a different
> memory region
> - it repeatedly hits e1000 or libata.ko
Okay: memtest+-5.01 run for 8h and did not find any errors in those 3
passes.
> After updating from OVMF to 0~20161202.7bbe0b3e-1 from
> (0~20160813.de74668f-2 it has not yet happened again.
Anyway, thank you for your help.
Philipp
prev parent reply other threads:[~2017-06-20 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 17:03 Philipp Hahn
2017-06-17 16:51 ` [Qemu-devel] " Laszlo Ersek
2017-06-18 18:22 ` Philipp Hahn
2017-06-18 18:27 ` Dr. David Alan Gilbert
2017-06-18 19:54 ` Philipp Hahn
2017-06-20 10:08 ` Philipp Hahn [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=d323a0b6-164f-7378-c565-e42128cf56b6@pmhahn.de \
--to=pmhahn@pmhahn.de \
--cc=hahn@univention.de \
--cc=lersek@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pjones@redhat.com \
--cc=qemu-devel@nongnu.org \
/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
all inboxes | Powered by JetHome®