From: Jason Wessel <jason.wessel@windriver.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Qemu PPC ethernet checksum bug
Date: Wed, 21 Mar 2007 00:33:10 -0500 [thread overview]
Message-ID: <4600C396.1050403@windriver.com> (raw)
In-Reply-To: <1174206229.7316.195.camel@rapid>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
J. Mayer wrote:
> Hi,
>
> My concern is I cannot reproduce your problem for the following reasons:
> - the PREP machine (and the heathrow too...) is broken and cannot even
> boot. PCI and/or IRQ are broken, so the Linux kernel hangs.
> - when using the "known to work" Linux distributions on the mac99
> machine (please take a look at the STATUS file), I am able to download a
> kernel from www.kernel.org, which makes me think TCP packets are sent
> and received correctly, with valid checksums.
>
> Then, it would be a great thing if you could isolate the failing routine
> and, for example, make a test case usable with linux-user emulation.
> This would be a great help to solve this issue.
>
> Thanks by advance.
>
>
Attached is a test program which demonstrates the issue. You can run
% ./ppc-linux-user/qemu-ppc /tmp/csum_test/main
Testing
Result 0x956a3263
Above is the correct result prior to 3/8/2007. If you run from CVS
today, you get
% ./ppc-linux-user/qemu-ppc /tmp/csum_test/main
Testing
Result 0x956a3264
It appears to be a result of the corruption of the xer_ca by the time
you do the first adde instruction.
Thanks,
Jason.
[-- Attachment #2: csum_test.tar.gz --]
[-- Type: application/x-gzip, Size: 262810 bytes --]
next prev parent reply other threads:[~2007-03-21 5:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-17 14:02 [Qemu-devel] qemu/target-ppc cpu.h exec.h helper.c op.c op_h Jocelyn Mayer
2007-03-17 14:53 ` Wessel, Jason
2007-03-18 8:23 ` [Qemu-devel] Re: Qemu PPC ethernet checksum bug J. Mayer
2007-03-21 5:33 ` Jason Wessel [this message]
2007-03-22 17:39 ` [Qemu-devel] Re: Qemu PPC ethernet checksum bug [PATCH] Jason Wessel
2007-03-22 19:19 ` J. Mayer
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=4600C396.1050403@windriver.com \
--to=jason.wessel@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.