From: Nigel Horne <824650@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 824650] [NEW] Latest GIT assert error in arp_table.c
Date: Thu, 11 Aug 2011 16:46:21 -0000 [thread overview]
Message-ID: <20110811164621.32220.49907.malonedeb@chaenomeles.canonical.com> (raw)
In-Reply-To: 20110811164621.32220.49907.malonedeb@chaenomeles.canonical.com
Public bug reported:
The latest git version of qemu (commit
8cc7c3952d4d0a681d8d4c3ac89a206a5bfd7f00) crashes after a few minutes.
All was fine up to a few days ago. This is wth both x86 and sparc
emulation, on an x86_64 host.
e.g. qemu-system-sparc -drive
file=netbsd5.0.2-sparc,index=0,media=disk,cache=unsafe -m 256 -boot c
-nographic -redir tcp:2232::22:
qemu-system-sparc: slirp/arp_table.c:75: arp_table_search: Assertion
`(ip_addr & (__extension__ ({ register unsigned int __v, __x = (~(0xf <<
28)); if (__builtin_constant_p (__x)) __v = ((((__x) & 0xff000000) >>
24) | (((__x) & 0x00ff0000) >> 8) | (((__x) & 0x0000ff00) << 8) |
(((__x) & 0x000000ff) << 24)); else __asm__ ("bswap %0" : "=r" (__v) :
"0" (__x)); __v; }))) != 0' failed.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/824650
Title:
Latest GIT assert error in arp_table.c
Status in QEMU:
New
Bug description:
The latest git version of qemu (commit
8cc7c3952d4d0a681d8d4c3ac89a206a5bfd7f00) crashes after a few minutes.
All was fine up to a few days ago. This is wth both x86 and sparc
emulation, on an x86_64 host.
e.g. qemu-system-sparc -drive
file=netbsd5.0.2-sparc,index=0,media=disk,cache=unsafe -m 256 -boot c
-nographic -redir tcp:2232::22:
qemu-system-sparc: slirp/arp_table.c:75: arp_table_search: Assertion
`(ip_addr & (__extension__ ({ register unsigned int __v, __x = (~(0xf
<< 28)); if (__builtin_constant_p (__x)) __v = ((((__x) & 0xff000000)
>> 24) | (((__x) & 0x00ff0000) >> 8) | (((__x) & 0x0000ff00) << 8) |
(((__x) & 0x000000ff) << 24)); else __asm__ ("bswap %0" : "=r" (__v) :
"0" (__x)); __v; }))) != 0' failed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/824650/+subscriptions
next parent reply other threads:[~2011-08-11 16:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 16:46 Nigel Horne [this message]
2011-08-31 21:03 ` [Qemu-devel] [Bug 824650] Re: Latest GIT assert error in arp_table.c Nigel Horne
2011-09-01 7:18 ` Jan Kiszka
2011-09-09 2:26 ` Nigel Horne
2011-09-15 4:11 ` [Qemu-devel] [Bug 824650] [NEW] " Roy Tam
2011-09-15 6:33 ` Jan Kiszka
2011-09-15 7:38 ` Roy Tam
2011-09-15 10:45 ` Jan Kiszka
2011-09-15 10:53 ` Roy Tam
2011-09-15 11:54 ` Jan Kiszka
2011-09-15 12:05 ` Roy Tam
2011-09-15 13:06 ` Jan Kiszka
2011-09-15 13:20 ` Roy Tam
2011-09-15 13:45 ` Jan Kiszka
2011-10-26 8:03 ` Roy Tam
2011-10-26 9:04 ` Jan Kiszka
2011-10-27 2:03 ` Roy Tam
2011-10-27 3:21 ` Roy Tam
2011-10-27 8:08 ` Jan Kiszka
2011-10-27 8:19 ` Roy Tam
2012-01-16 17:14 ` [Qemu-devel] [Bug 824650] " AleksTJ@gmail.com
2012-02-07 18:12 ` Bjoern Bornemann
2012-02-08 8:39 ` Bjoern Bornemann
2012-02-10 8:42 ` Bjoern Bornemann
2012-02-18 15:44 ` Solitaire
2012-02-18 16:36 ` Bjoern Bornemann
2012-02-18 17:59 ` Solitaire
2012-02-24 2:23 ` Roy Tam
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=20110811164621.32220.49907.malonedeb@chaenomeles.canonical.com \
--to=824650@bugs.launchpad.net \
--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.