From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [BUG] Regression in networking code (SIGSEGV)
Date: Wed, 21 Jan 2009 22:17:20 +0100 [thread overview]
Message-ID: <497790E0.7050905@mail.berlios.de> (raw)
Hi,
the SIGSEGV crash below can be reproduced with Qemu r6391 and "high" net
load.
I bootet a mips malta kernel from a debian nfs root. While this worked fine,
aptitude update hangs during downloads, nfs root is lost and after some time
Qemu gets a SIGSEGV.
A similar crash occurs with a different mips machine (ar7) and different
network hardware (ar7 emac / cpmac), so it is not restricted to pcnet.
This second system does not survive the network boot.
Up to now, I could not run tests with non-mips systems.
I'm fairly sure that 2 weeks ago networking worked without problems in both
cases.
Regards
Stefan Weil
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f3be89386e0 (LWP 14845)]
0x00000000004d1a6f in ip_reass (ip=0xfe96e0, fp=0x1109050) at
~/src/qemu/trunk/slirp/ip_input.c:408
408 ip->ip_len = next;
(gdb) i s
#0 0x00000000004d1a6f in ip_reass (ip=0xfe96e0, fp=0x1109050) at
~/src/qemu/trunk/slirp/ip_input.c:408
#1 0x00000000004d15ad in ip_input (m=0x110e010) at
~/src/qemu/trunk/slirp/ip_input.c:228
#2 0x00000000004b3d25 in slirp_input (pkt=0x12fcbd0 "RT", pkt_len=1294)
at ~/src/qemu/trunk/slirp/slirp.c:679
#3 0x000000000049a07d in qemu_send_packet (vc1=0x10ff440, buf=0x12fcbd0
"RT", size=1294) at ~/src/qemu/trunk/net.c:399
#4 0x000000000042ea6a in pcnet_transmit (s=0x12fc810) at
~/src/qemu/trunk/hw/pcnet.c:1300
#5 0x000000000042ebd8 in pcnet_poll_timer (opaque=<value optimized
out>) at ~/src/qemu/trunk/hw/pcnet.c:1363
#6 0x000000000042f270 in pcnet_ioport_writew (opaque=0x7f3be72a79e0,
addr=17884784, val=16684768)
at ~/src/qemu/trunk/hw/pcnet.c:1645
#7 0x0000000000405eb8 in ioport_write (index=1, address=4146, data=0)
at ~/src/qemu/trunk/vl.c:302
#8 0x00000000004062b5 in cpu_outw (env=0x0, addr=4146, val=0) at
~/src/qemu/trunk/vl.c:432
#9 0x00000000420ae755 in ?? ()
#10 0x0000000000000000 in ?? ()
(gdb) up
#1 0x00000000004d15ad in ip_input (m=0x110e010) at
~/src/qemu/trunk/slirp/ip_input.c:228
228 ip = ip_reass(ip, fp);
(gdb) p ip
$1 = (struct ip *) 0x110e060
(gdb) do
#0 0x00000000004d1a6f in ip_reass (ip=0xfe96e0, fp=0x1109050) at
~/src/qemu/trunk/slirp/ip_input.c:408
408 ip->ip_len = next;
(gdb) p *ip
Cannot access memory at address 0xfe96e0
next reply other threads:[~2009-01-21 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 21:17 Stefan Weil [this message]
2009-01-22 7:38 ` [Qemu-devel] [BUG] Regression in networking code (SIGSEGV) Gleb Natapov
2009-01-24 21:00 ` Stefan Weil
2009-01-24 21:53 ` Aurelien Jarno
2009-01-25 21:29 ` Stefan Weil
2009-01-26 6:29 ` Gleb Natapov
2009-02-01 20:11 ` Stefan Weil
[not found] ` <20090202163806.GA29674@redhat.com>
2009-02-04 12:01 ` Stefan Weil
2009-02-05 15:34 ` Gleb Natapov
2009-02-05 19:24 ` Stefan Weil
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=497790E0.7050905@mail.berlios.de \
--to=weil@mail.berlios.de \
--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).