All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: "Ingo Jürgensmann" <ij@2013.bluespice.org>,
	"Andreas Ziegler" <ml@andreas-ziegler.de>
Cc: janprunk@gmail.com, Wei.Liu2@citrix.com,
	george.dunlap@citrix.com, xen-devel@lists.xen.org
Subject: Re: Kernel panic on Xen virtualisation in Debian
Date: Mon, 25 Jul 2016 11:49:36 +0100	[thread overview]
Message-ID: <5795EEC0.6010700@citrix.com> (raw)
In-Reply-To: <9ff88c3a34c81efb0a28188a68aa6c0a@localhost>

On 25/07/16 10:38, Ingo Jürgensmann wrote:
> On 22.07.2016 12:21, Ingo Jürgensmann wrote:
>> On 22.07.2016 11:03, Ingo Jürgensmann wrote:
>>
>>> In the meanwhile, I activated IPv6 again on Tuesday evening and today
>>> the server crashed again some minutes ago. Here's the output from
>>> netconsole:
>> ... and the second subsequent crash:
> 
> ... and another crash below...
> 
> But in the meanwhile, I wonder if anyone except Andreas and I has some
> interest in fixing this issue, as there were absolutely no comments or
> feedback on my previous mails. Quite disappointing. :-/

The level of technical support is somewhat proportional to what you pay.

> Jul 25 10:50:00 31.172.31.251 [257646.574819] CPU: 0 PID: 0 Comm:
> swapper/0 Not tainted 3.16.0-4-amd64 #1 Debian 3.16.7-ckt25-2+deb8u3
> Jul 25 10:50:00 31.172.31.251 [257646.574874] Hardware name: Supermicro
> X9SRE/X9SRE-3F/X9SRi/X9SRi-3F/X9SRE/X9SRE-3F/X9SRi/X9SRi-3F, BIOS 3.0a
> 01/03/2014
> Jul 25 10:50:00 31.172.31.251 [257646.574934] task: ffffffff8181a460 ti:
> ffffffff81800000 task.ti: ffffffff81800000
> Jul 25 10:50:00 31.172.31.251 [257646.575080] RIP:
> e030:[<ffffffff812b7a16>]
> Jul 25 10:50:00 31.172.31.251  [<ffffffff812b7a16>] memcpy+0x6/0x110


I think that there's a path in the network stack that is cloning frags
without orphaning them.  The original frags are freed (and unmapped) and
the cloned frags now have unmapped pages.

I think newer kernels address at least one of these paths.

David


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-07-25 10:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09 22:29 Kernel panic on Xen virtualisation in Debian Andreas Ziegler
2016-07-10 13:18 ` Ingo Jürgensmann
2016-07-18 16:44   ` Andreas Ziegler
2016-07-22  9:03     ` Ingo Jürgensmann
2016-07-22 10:21       ` Ingo Jürgensmann
2016-07-25  9:38         ` Ingo Jürgensmann
2016-07-25 10:23           ` Wei Liu
2016-07-25 10:42             ` Andreas Ziegler
2016-07-25 10:50               ` Andreas Ziegler
2016-07-25 10:51               ` Wei Liu
2016-07-25 11:27                 ` Ingo Jürgensmann
2016-07-25 12:35                   ` Sander Eikelenboom
2016-07-25 11:41             ` Ingo Jürgensmann
2016-07-25 13:13               ` Wei Liu
2016-07-29 11:45                 ` Andreas Ziegler
2016-07-29 13:01                   ` Wei Liu
2016-07-29 20:17                   ` Ingo Jürgensmann
2016-08-02  9:20                     ` Wei Liu
2016-08-02 10:30                       ` Ingo Jürgensmann
2016-08-02 12:37                         ` Wei Liu
2016-11-14 15:55                           ` Andreas Ziegler
2016-11-29  9:08                             ` Wei Liu
2016-11-29 20:20                               ` Ingo Jürgensmann
2016-12-01 13:26                                 ` Wei Liu
2016-12-01 13:59                                   ` Ingo Jürgensmann
2016-12-01 14:07                                     ` Wei Liu
2016-12-01 14:50                                     ` Sander Eikelenboom
2016-07-25 10:49           ` David Vrabel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-07-04 18:06 Jan Prunk
2016-07-06 14:14 ` George Dunlap
2016-07-08 11:14   ` Wei Liu
2016-07-08 12:22     ` Jan Prunk

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=5795EEC0.6010700@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Wei.Liu2@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=ij@2013.bluespice.org \
    --cc=janprunk@gmail.com \
    --cc=ml@andreas-ziegler.de \
    --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.