From: Rob Gardner <rob.gardner@hp.com>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: help with horrible network failures
Date: Tue, 01 Mar 2005 14:06:47 -0700 [thread overview]
Message-ID: <4224D967.3050904@hp.com> (raw)
I've got two machines running identical versions of xen & linux. One of
them constantly has problems under high network loads (70-100% httperf
loads). This is using xen-unstable checked out on or about Feb 13. Any
clues? See below for details.
Rob
KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1284)
(this messager sometimes repeated dozens of times...)
Followed by:
Unable to handle kernel paging request at virtual address a02e19e0
printing eip:
c0115fad
*pde = ma 00000000 pa 55555000
[<c0116b21>] __wake_up_common+0x41/0x60
[<c0116b8c>] __wake_up+0x4c/0xb0
[<c023d2d9>] sock_def_wakeup+0x49/0x50
[<c026a9d9>] tcp_rcv_state_process+0x749/0x970
[<c02723d6>] tcp_v4_do_rcv+0xa6/0x130
[<c0272a18>] tcp_v4_rcv+0x5b8/0x850
[<c02158b7>] add_timer_randomness+0x107/0x130
[<c025740b>] ip_local_deliver+0xab/0x160
[<c02577ea>] ip_rcv+0x32a/0x460
[<c0210bf0>] memmove+0x50/0x60
[<c0244553>] netif_receive_skb+0x133/0x1c0
[<c0238601>] netif_poll+0x301/0x660
[<c023de84>] kfree_skbmem+0x24/0x30
[<c0244815>] net_rx_action+0xb5/0x1a0
[<c011f545>] __do_softirq+0xc5/0xf0
[<c011f5fa>] do_softirq+0x8a/0x90
[<c0136355>] irq_exit+0x35/0x40
[<c010e262>] do_IRQ+0x22/0x30
[<c0106048>] evtchn_do_upcall+0xa8/0x110
[<c0109dc7>] hypervisor_callback+0x37/0x40
Oops: 0000 [#1]
PREEMPT
Modules linked in:
CPU: 0
EIP: 0061:[<c0115fad>] Not tainted VLI
EFLAGS: 00010202 (2.6.10-xenU)
EIP is at try_to_wake_up+0x1d/0xf0
eax: c033d860 ebx: a02e19e0 ecx: 00000001 edx: c2403d88
esi: c527dc98 edi: 00000000 ebp: c2403d98 esp: c2403d7c
ds: 007b es: 007b ss: 0069
Process httpd (pid: 7900, threadinfo=c2402000 task=c41c7a60)
Stack: a02e19e0 c2403d88 00000004 00000001 00000000 c527dc98 00000000
c2403dbc
c0116b21 a02e19e0 00000001 00000000 00000000 00000000 00000000
c2402000
c2403de8 c0116b8c c527dc98 00000001 00000000 00000000 00000000
00000000
Call Trace:
[<c0116b21>] __wake_up_common+0x41/0x60
[<c0116b8c>] __wake_up+0x4c/0xb0
[<c023d2d9>] sock_def_wakeup+0x49/0x50
[<c026a9d9>] tcp_rcv_state_process+0x749/0x970
[<c02723d6>] tcp_v4_do_rcv+0xa6/0x130
[<c0272a18>] tcp_v4_rcv+0x5b8/0x850
[<c02158b7>] add_timer_randomness+0x107/0x130
[<c025740b>] ip_local_deliver+0xab/0x160
[<c02577ea>] ip_rcv+0x32a/0x460
[<c0210bf0>] memmove+0x50/0x60
[<c0244553>] netif_receive_skb+0x133/0x1c0
[<c0238601>] netif_poll+0x301/0x660
[<c023de84>] kfree_skbmem+0x24/0x30
[<c0244815>] net_rx_action+0xb5/0x1a0
[<c011f545>] __do_softirq+0xc5/0xf0
[<c011f5fa>] do_softirq+0x8a/0x90
[<c0136355>] irq_exit+0x35/0x40
[<c010e262>] do_IRQ+0x22/0x30
[<c0106048>] evtchn_do_upcall+0xa8/0x110
[<c0109dc7>] hypervisor_callback+0x37/0x40
Code: 28 00 00 00 00 8b 5d fc 89 ec 5d c3 89 f6 55 89 e5 57 8d 45 f0 31
ff 56 53
83 ec 1 0 8b 5d 08 89 44 24 04 89 1c 24 e8 33 fc ff ff <8b> 13 89 c6
8b 45 0c
85 d0 74 4d 8b 43 28 85 c0 75 40 83 fa 02
<0>Kernel panic - not syncing: Fatal exception in interrupt
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-03-01 21:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 21:06 Rob Gardner [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-02 13:37 help with horrible network failures Ian Pratt
2005-03-02 18:01 ` Nivedita Singhvi
2005-03-02 18:10 ` Rob Gardner
2005-03-02 18:37 ` Nivedita Singhvi
2005-03-02 20:07 ` Jon Mason
2005-03-02 20:20 ` Nivedita Singhvi
2005-03-02 20:55 ` Nivedita Singhvi
2005-03-02 22:52 ` Rob Gardner
2005-03-02 23:13 ` Jon Mason
2005-03-02 23:34 ` Rob Gardner
2005-03-02 23:43 ` Nivedita Singhvi
2005-03-02 23:58 ` Rob Gardner
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=4224D967.3050904@hp.com \
--to=rob.gardner@hp.com \
--cc=xen-devel@lists.sourceforge.net \
/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.