All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Roy Tam <roytam@gmail.com>
Cc: Bug 824650 <824650@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 824650] [NEW] Latest GIT assert error in arp_table.c
Date: Wed, 26 Oct 2011 11:04:27 +0200	[thread overview]
Message-ID: <4EA7CD1B.2070106@siemens.com> (raw)
In-Reply-To: <CAA=zYJaUDxd_LVYVrqe8e9bRrO9oLrTG_usZUJs87sSTOrGt1Q@mail.gmail.com>

On 2011-10-26 10:03, Roy Tam wrote:
> Hi,
> 
> 2011/9/15 Jan Kiszka <jan.kiszka@web.de>:
>> On 2011-09-15 15:20, Roy Tam wrote:
>>> 2011/9/15 Jan Kiszka <jan.kiszka@web.de>:
>>>> On 2011-09-15 14:05, Roy Tam wrote:
>>>>> Here you go.
>>>>>
>>>>> sb16: warning: command 0xf,1 is not truly understood yet
>>>>> sb16: warning: command 0xe,2 is not truly understood yet
>>>>> [Switching to Thread 13840.0x3140]
>>>>>
>>>>> Breakpoint 1, arp_table_search (slirp=0x19f7380, ip_addr=4294967295,
>>>>>     out_ethaddr=0x20af64a "") at slirp/arp_table.c:75
>>>>> 75      //    assert((ip_addr & htonl(~(0xf << 28))) != 0);
>>>>> (gdb) c
>>>>> Continuing.
>>>>> [New Thread 13840.0x31b8]
>>>>> [Switching to Thread 13840.0x3628]
>>>>>
>>>>> Breakpoint 1, arp_table_search (slirp=0x19f7380, ip_addr=0,
>>>>>     out_ethaddr=0x22f642 "\"") at slirp/arp_table.c:75
>>>>> 75      //    assert((ip_addr & htonl(~(0xf << 28))) != 0);
>>>>> (gdb) bt
>>>>> #0  arp_table_search (slirp=0x19f7380, ip_addr=0, out_ethaddr=0x22f642 "\"")
>>>>>     at slirp/arp_table.c:75
>>>>> #1  0x004bafbd in if_encap (slirp=0x19f7488, ifm=0x2255978)
>>>>>     at slirp/slirp.c:709
>>>>> #2  0x004b8a73 in if_start (slirp=0x19f7380) at slirp/if.c:210
>>>>> #3  0x004b9c9e in ip_output (so=0x2255978, m0=0x0) at slirp/ip_output.c:84
>>>>> #4  0x004bf737 in tcp_output (tp=0x1cac848) at slirp/tcp_output.c:456
>>>>> #5  0x004c09ad in tcp_drop (tp=0x1cac848, err=0) at slirp/tcp_subr.c:225
>>>>> #6  0x004c1182 in tcp_timers (timer=<optimized out>, tp=<optimized out>)
>>>>>     at slirp/tcp_timer.c:287
>>>>> #7  tcp_slowtimo (slirp=0x0) at slirp/tcp_timer.c:88
>>>>> #8  0x004bb6f1 in slirp_select_poll (readfds=0x22fae0, writefds=0x22f9dc,
>>>>>     xfds=0x22f8d8, select_error=2291816) at slirp/slirp.c:433
>>>>> #9  0x0048fb87 in main_loop_wait (nonblocking=0)
>>>>>     at C:/msys/home/User/qemu/vl.c:1436
>>>>> #10 0x00490d10 in main_loop () at C:/msys/home/User/qemu/vl.c:1466
>>>>> #11 qemu_main (argc=0, argv=0x19f5100, envp=0x0)
>>>>>     at C:/msys/home/User/qemu/vl.c:3453
>>>>> #12 0x0049322d in SDL_main (argc=17, argv=0x19f5100)
>>>>>     at C:/msys/home/User/qemu/vl.c:102
>>>>> #13 0x005eb784 in console_main ()
>>>>> #14 0x005eb844 in WinMain@16 ()
>>>>> #15 0x005eb068 in main ()
>>>>> (gdb) frame 4
>>>>> #4  0x004bf737 in tcp_output (tp=0x1cac848) at slirp/tcp_output.c:456
>>>>> 456             error = ip_output(so, m);
>>>>> (gdb) print *tp
>>>>> $1 = {seg_next = 0x1cac848, seg_prev = 0x1cac848, t_state = 0, t_timer = {0,
>>>>>     0, 0, 0}, t_rxtshift = 0, t_rxtcur = 12, t_dupacks = 0, t_maxseg = 1460,
>>>>>   t_force = 0 '\000', t_flags = 0, t_template = {ti_i = {ih_mbuf = {
>>>>>         mptr = 0x0, dummy = 0}, ih_x1 = 0 '\000', ih_pr = 0 '\000',
>>>>>       ih_len = 0, ih_src = {S_un = {S_un_b = {s_b1 = 0 '\000',
>>>>>             s_b2 = 0 '\000', s_b3 = 0 '\000', s_b4 = 0 '\000'}, S_un_w = {
>>>>>             s_w1 = 0, s_w2 = 0}, S_addr = 0}}, ih_dst = {S_un = {S_un_b = {
>>>>>             s_b1 = 0 '\000', s_b2 = 0 '\000', s_b3 = 0 '\000',
>>>>>             s_b4 = 0 '\000'}, S_un_w = {s_w1 = 0, s_w2 = 0}, S_addr = 0}}},
>>>>
>>>> That confirms my theory: the template is not yet initialized.
>>>>
>>>> A shot from the hips: does this patch help?
>>>>
>>>
>>> Yeah the assertion doesn't fail anymore. Thanks.
>>
>> Now I just need to invent some good "why this is correct"... ;)
>>
>> Thanks for testing,
> 
> I just have time now to make some tests about -net user.
> And I found that the User mode networking doesn't work anymore after
> your slirp patch series.

Can you be more verbose? What precisely does not work? Same setup as
before (host, guest, command line, steps to reproduce)? I'm not facing
problems here ATM.

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-10-26  9:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 16:46 [Qemu-devel] [Bug 824650] [NEW] Latest GIT assert error in arp_table.c Nigel Horne
2011-08-31 21:03 ` [Qemu-devel] [Bug 824650] " 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 [this message]
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=4EA7CD1B.2070106@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=824650@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    --cc=roytam@gmail.com \
    /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.