From: Vasily Evseenko <svpcom@gmail.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: domU crash with kernel BUG at drivers/net/xen-netfront.c:305
Date: Fri, 27 Dec 2013 16:21:10 +0400 [thread overview]
Message-ID: <52BD70B6.7040300@gmail.com> (raw)
In-Reply-To: <20131227115345.GR25969@zion.uk.xensource.com>
[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]
Hi,
There are no clear steps to reproduce.
Bug triggered only by high tcp network load (webserver pattern - many
small connections) every one - two days.
See xen, dom0 and domU's info in attachment. I can provide any
additional info.
I've tried dom0/domU kernels 3.10.23 (vanilla, from centos-xen) and
3.10.25, xen 4.2.3 and 4.3.1.
On 12/27/2013 03:53 PM, Wei Liu wrote:
> On Fri, Dec 27, 2013 at 03:09:17PM +0400, Vasily Evseenko wrote:
>> Hi,
>>
>> I've got domU crash (~ every 1-2 days under high network (tcp) load)
>> with message:
>>
> Do you have clear steps on how to reproduce this issue?
>
>> domU's are under high TCP load (a lot of small tcp connections (web server))
>> sometimes i've got on dom0:
>> ---
>> [2013-12-26 00:16:30] (XEN) grant_table.c:289:d0 Increased maptrack size
>> to 2 frames
>> [2013-12-26 03:53:18] (XEN) grant_table.c:1858:d0 Bad grant reference
>> 99221507
>> [2013-12-26 03:53:18] (XEN) grant_table.c:1858:d0 Bad grant reference
>> 43646979
>> [2013-12-26 03:53:18] (XEN) grant_table.c:1858:d0 Bad grant reference
>> 43646979
>> [2013-12-26 03:53:18] (XEN) grant_table.c:1858:d0 Bad grant reference
>> 99221507
>> [2013-12-26 06:15:14] (XEN) grant_table.c:1858:d0 Bad grant reference
>> 43646979
>> [2013-12-26 06:15:14] (XEN) grant_table.c:1858:d0 Bad grant reference
>> 99221507
>> [2013-12-26 06:15:14] (XEN) grant_table.c:1858:d0 Bad grant reference
>> 99221507
>> [2013-12-26 06:15:14] (XEN) grant_table.c:1858:d0 Bad grant reference
>> 99221507
>>
> Grant reference this big doesn't look right. Frontend is passing garbage
> to backend. Given that the numbers showed above have certain pattern
> there might be a bug in frontend somewhere.
>
>> ---
>>
>> It seems the root of problem in dom0 messages above. Is it HW failure or
>> some internal kernel structures overflow?
>>
> It's not hardware failure, more likely to be overflow. In order to fix
> this you need to provide more info on your workload, software setup etc.
>
> Wei.
>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
[-- Attachment #2: host.tgz --]
[-- Type: application/x-gzip, Size: 19688 bytes --]
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-12-27 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 11:09 domU crash with kernel BUG at drivers/net/xen-netfront.c:305 Vasily Evseenko
2013-12-27 11:53 ` Wei Liu
2013-12-27 12:21 ` Vasily Evseenko [this message]
2013-12-27 14:20 ` Wei Liu
2013-12-31 12:56 ` William Dauchy
2013-12-31 14:23 ` Vasily Evseenko
2014-01-02 5:09 ` annie li
2014-01-02 11:40 ` Pasi Kärkkäinen
2014-01-02 12:01 ` Wei Liu
2014-01-03 6:15 ` annie li
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=52BD70B6.7040300@gmail.com \
--to=svpcom@gmail.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.