From: "Kazu" <kazoo@r3.dion.ne.jp>
To: Christian MICHON <christian.michon@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] pcnet/mingw32 debug info (help needed)
Date: Fri, 22 Jul 2005 19:30:16 +0900 [thread overview]
Message-ID: <002501c58ea8$5a35eaa0$0464a8c0@athlon> (raw)
In-Reply-To: 46d6db660507220031588860a5@mail.gmail.com
Hi,
Sent: Friday, July 22, 2005 4:31 PM Christian MICHON wrote:
>here's the output of gdb. If anyone can make something from it,
>thanks in advance.
This is a part of backtrace output of gdb after I set IP address and ping
10.0.2.2.
I seems that arp packet loops endlessly between pcnet and slirp.
I think something is wrong in pcnet_receive?
#27399 0x004552ac in pcnet_transmit (s=0xcdbf8e8)
at C:/msys/1.0/home/kazu/qemu-0.7.0/hw/pcnet.c:582
#27400 0x00455571 in pcnet_poll (s=0xcdbf8e8)
at C:/msys/1.0/home/kazu/qemu-0.7.0/hw/pcnet.c:625
#27401 0x00454fc3 in pcnet_receive (opaque=0xcdbf8e8, buf=0x22f7b0 "RT",
size=0) at C:/msys/1.0/home/kazu/qemu-0.7.0/hw/pcnet.c:538
#27402 0x004025f7 in slirp_output (pkt=0x22f7b0 "RT", pkt_len=42)
at C:/msys/1.0/home/kazu/qemu-0.7.0/vl.c:1402
#27403 0x0045b980 in arp_input (pkt=0xcdbfc30 "??????RT", pkt_len=42)
at C:/msys/1.0/home/kazu/qemu-0.7.0/slirp/slirp.c:583
#27404 0x0045b9dc in slirp_input (pkt=0xcdbfc30 "??????RT", pkt_len=42)
at C:/msys/1.0/home/kazu/qemu-0.7.0/slirp/slirp.c:602
#27405 0x00402611 in slirp_send_packet (nd=0x4e6a90, buf=0xcdbfc30
"??????RT",
size=42) at C:/msys/1.0/home/kazu/qemu-0.7.0/vl.c:1411
#27406 0x00402541 in qemu_send_packet (nd=0x4e6a90, buf=0xcdbfc30
"??????RT",
size=42) at C:/msys/1.0/home/kazu/qemu-0.7.0/vl.c:1353
#27407 0x004552ac in pcnet_transmit (s=0xcdbf8e8)
at C:/msys/1.0/home/kazu/qemu-0.7.0/hw/pcnet.c:582
#27408 0x00455571 in pcnet_poll (s=0xcdbf8e8)
at C:/msys/1.0/home/kazu/qemu-0.7.0/hw/pcnet.c:625
#27409 0x004556aa in pcnet_poll_timer (opaque=0xcdbf8e8)
at C:/msys/1.0/home/kazu/qemu-0.7.0/hw/pcnet.c:647
#27410 0x00455fa1 in pcnet_ioport_writew (opaque=0xcdbf8e8, addr=49202,
val=0)
at C:/msys/1.0/home/kazu/qemu-0.7.0/hw/pcnet.c:915
#27411 0x004018f0 in cpu_outw (env=0x3d7358, addr=49202, val=0)
at C:/msys/1.0/home/kazu/qemu-0.7.0/vl.c:372
#27412 0x0078456b in code_gen_buffer ()
#27413 0x00404315 in main_loop () at
C:/msys/1.0/home/kazu/qemu-0.7.0/vl.c:2700
#27414 0x00406c94 in main (argc=6, argv=0x3d27e8)
at C:/msys/1.0/home/kazu/qemu-0.7.0/vl.c:3719
(gdb) q
This backtrace said that as follows.
cpu_outputw
pcnet_ioport_wirtew <- arp packet is send from pcnet to slirp
pcnet_poll_timer
pcnet_poll
pcnet_transmit
<snip>
slirp_input
arp_input <- arp packet returns form slirp to pcnet
slirp_output
pcnet_receive <- arp packet received by pcnet
pcnet_poll <- I don't know why pcnet_poll is called again
pcnet_transmit <- endless loop
Regards,
Kazu
next prev parent reply other threads:[~2005-07-22 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 7:31 [Qemu-devel] pcnet/mingw32 debug info (help needed) Christian MICHON
2005-07-22 10:30 ` Kazu [this message]
2005-07-22 12:52 ` Christian MICHON
2005-07-23 2:05 ` Kazu
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='002501c58ea8$5a35eaa0$0464a8c0@athlon' \
--to=kazoo@r3.dion.ne.jp \
--cc=christian.michon@gmail.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;
as well as URLs for NNTP newsgroup(s).